Setting the log levels for DNCA processes for troubleshooting
The DNCA processes generate messages. For normal operations, the logging levels are set to a default level. During a troubleshooting situation, Support Services might ask you to adjust the logging levels to see additional information to resolve issues. Logging levels are set in the .bashrc file on the Linux server. Increasing the levels increases the number of events that are generated and the size of the log files must be checked constantly to not use up too much space. Changing the levels is only recommended for a short period for debugging.
About this task
You can set the logging levels for these DNCA processes:
- pipelined
- routerd
- reassd
- listend
- tcld
- deliverd
- captured
Logging types and levels are:
To log only these messages | Set the log level to | What it is used for |
---|---|---|
LOG_EMERG | 0 | This level is not currently used by Discover, only third-party software. |
LOG_ALERT | 1 | This level is not currently used by Discover. |
LOG_CRIT | 2 | Needs immediate attention. |
LOG_ERR | 3 | Some error was encountered and the software tries to correct it as best it can. This condition should be fixed for optimal operation. |
LOG_WARNING | 4 | Things are not working as they should. This condition must be fixed for optimal operation. |
LOG_NOTICE | 5 | Advisory log, for example the configuration was changed. |
LOG_INFO | 6 | This level is same as NOTICE and they are used interchangeably. This level might help in debugging by providing current state information. |
LOG_DEBUG | 7 | This level is the most useful for debugging. It provides the most in-depth information on the working of the DNCA. |