| Add_workflow_for_techpubs |
|---|
| AUTH1 | |
|---|
| JIRAIDAUTH | SYM-28494 |
|---|
| REV5 | |
|---|
| REV6 | |
|---|
| REV3 | |
|---|
| REV1 | |
|---|
|
Overview
The
logging service allows you to troubleshoot issues such as call signaling, call quality and performance by collecting activity logs from its subsystems. These logging records can then be analyzed to diagnose problems and optimize the performance of
for your environment.
The
system supports the following methods for recording logs:
- Remote Syslog configuration, uses a syslog server to store a larger amount of log activity for extended period of time. Using a Remote Logging configuration is the recommended logging method since it allows for a greater logging history and level of detail. You must use this method of logging when working with Technical Support (TAC).
Local Log configuration (available only on the SBC 2000, Ribbon SBC 1000 v2 equipped with eUSB, and SBC SWe Lite), stores temporary log files directly on the system. Each local log file retains a limited amount of recorded log messages. Local logging is only useful for quick, high level, troubleshooting, and is not recommended (nor suited) for extended troubleshooting sessions.
| Warning |
|---|
| title | Logging at Debug or Trace Level |
|---|
|
- Increasing the local log level of any subsystem to Debug or Trace levels should be performed only if requested by Technical Support (TAC).
- After completing the collection of logs from the tests, all subsystems with custom log level must be reset to the Default local log level (Warning) or deleted.
- Avoid performing this action on a production system.
|
A fully running
system can generate a large amount of logging information. For this reason, the
logging service allows you to customize the types of logging messages (and level of detail) you wish to be recorded by
Managing Subsystems Logging and Log Profiles.
Debug
Logs using LX
Refer to
| Link_in_new_tab |
|---|
| Text | Log Exchange - LX |
|---|
| URL | Log Exchange - LX |
|---|
|
documentation for details.
Debug Easy Configuration Errors
This section includes how to capture logs for debugging Easy Configuration errors as follows:
- In the WebUI, click the Diagnostics tab.
In the Logs page, click the Logs > Web Error Logs.
View the lighttpd.error.log file.
| Tip |
|---|
If Easy Configuration encounters an error condition, the system will roll back the changes made up to that point. To help with troubleshooting, you can view where the roll back began in the lighttpd.error.log file. |