103
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Monitoring and Managing Log Files
Last updated 11/28/2012
Application logs
Application log file
The application log records information about activities in application instances. This log is used primarily for
debugging (logging uncommon events that occur in an application instance).
The default application log is application.xx.log, located in the subdirectory within the Flash Media Server logs
directory. Flash Media Server is configured, by default, to create one application log per application instance. The
application folder is located in the matching virtual host directory. The “xx” in the filename is a two-digit number
representing the history of the application log. The most recent logs can be found in application.00.log.
Fields in application logs
disconnect
js_exception
602
An unknown exception is thrown from the JS
engine.
disconnect
js_chunkstream_error
603
Bad application data.
disconnect
js_debug_forbidden
604
Application does not allow debug connections.
play
js_gc_object
605
~fcstreamjshook() clean up.
Field
Event(s)
Description
date
All
Date of the event.
time
All
Time of the event.
x-pid
All
Server process ID.
x-status
All
Status code: The code is a 10-character string that represents the severity, category, and
message ID.
The first three characters represent severity, as follows:
(w) = warning
(e) = error
(i) = information
(d) = debug
(s) = trace from server-side script
(_) = unknown
The next three characters represent the category. All categories are listed in “
Status
categories in diagnostic logs
” on page
104.
The last four characters represent message ID. All message IDs are listed in “
Diagnostic
logs
” on page
104.
x-ctx
All
Event-dependent context information.
Field
Symbol
Status Code
Description