Administration
A31003-S2000-M102-3-76A9, 08/07/2009
3-146
Asterisk - OpenStage Family, Administration Manual
administration.fm
Diagnostics
3.19.6
Fault Trace Configuration
Error tracing and logging can be configured separately for all components, i. e. the services and
applications running on the OpenStage phone. The resulting files can be viewed in the WBM
web pages over the
Download
links.
The
File size (bytes)
parameter sets the maximum file size. When the maximum size is
reached, the file is deleted, and a new file is generated. The trace data is then written to the
new file. The default value is 65536.
The
Trace timeout (minutes)
determines when to stop tracing, i. e. writing to the trace file.
When the value is 0, no trace file will be written.
If
Automatic clear before start
is checked, the existing trace file will be deleted on pressing
the
Submit
button, and a new, empty trace file will be generated. By default, it is unchecked.
You can read the log files by clicking on the appropriate hyperlinks (the hyperlinks work only if
the file in question has been created). The following logs can be viewed:
•
Download trace file
The trace data according to the settings specified for the services.
•
Download boot file
(not present with V2)
The system messages of the booting process. With firmware version V2, these messages
are incorparated in the syslog file (see
Download syslog file
underneath).
•
Download saved trace file
Normally, the trace file is saved only in the phone RAM. When the phone restarts in a con-
trolled manner, the trace file will be saved in permanent memory.
•
Download saved boot file
(not present with V2)
Normally, the boot file is saved only in the phone RAM. When the phone restarts in a con-
trolled manner, the boot file will be saved in permanent memory. With firmware version V2,
these messages will be incorparated in the syslog file (see
Download syslog file
under-
neath).
•
Download upgrade trace file
The trace log created during a software upgrade.
•
Download upgrade error file
(not present with V2)
The error messages created during a software upgrade. With firmware version V2, these
messages will be incorparated in the syslog file (see
Download syslog file
underneath).
•
Download exception file
If an exceptions occurs in a process running on the phone, a message is written to this file.
•
Download old exception file
(not present with V2)
The exception file is stored permanent memory. When the file has reached its size limit, it
will be saved as old exception file, and the current exception file is emptied for future mes-
sages. The old exception file can be viewed here.
•
Download old trace file