Flash Media Server |
|||
| Managing Flash Media Server > Managing the Server > Logging client connections and other system events > 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). Users can also add user-defined messages to the application log by using trace() in server-side scripting.
The default application log is application.xx.log, located in the subdirectory within the Flash Media Server 2 logs directory. Flash Media Server 2 is configured, by default, to create one application log per application instance. The application folder is located in the matching vhost directory. The "xx" in the filename is a 2-digit number representing the history of the application log. The most recent logs can be found in "application.00.log."
The following table lists the fields in the application logs.
|
Field |
Event(s) |
Description |
|---|---|---|
|
date |
all |
Date on which the event occurred. |
|
time |
all |
Time at which the event occurred. |
|
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 3 characters represent severity. This is always in a letter format. The letters are as follows:
(w) = warning (e) = error (i) = information (d) = debug (s) = trace from server-side script (_) = unknown
The next 3 characters represent category. All categories are listed in the "Status" table below for the diagnostic logs.
The last 4 characters represent message ID. All messages IDs are listed in the "Status Message IDs" table below for the Diagnostics logs. |
|
x-ctx |
all |
Event-dependent context information |
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/fms/2/docs/00000182.html