Collecting Debug Information for the Asterisk Issue Tracker
This document will provide instructions on how to collect debugging logs from an Asterisk machine, for the purpose of helping bug marshals troubleshoot an issue on https://issues.asterisk.org
- Asterisk 1.4.30 or greater.
1. Edit the logger.conf file to enable debug output to your filesystem. Add the following line. The word "myDebugLog" can be changed to anything you want, as that is the filename the logging will be written to. A good example might be something like: issue_12345_full_log
2. From the Asterisk CLI, restart the logger module:
Optionally, if you've used this file to record data previously, then rotate the logs:
2.1. Depending on your issue and if a protocol level trace is requested, be sure to enable logging for the channel driver or other module.
|Module (version)||CLI Command|
|New PJSIP driver (12 or higher)|
pjsip set logger on
|SIP (1.6.0 or higher)|
sip set debug on
sip set debug
|IAX2 (1.6.0 or higher)|
iax2 set debug on
iax2 set debug
3. Reproduce your issue.
4. Once finished, be sure to disable the extra debugging:
4.1. Again, remember to disable any extra logging if you enabled it in the
SIP (1.4 or higher)
IAX2 (1.4 or higher)
5. Upload the file located in /var/log/asterisk/myDebugLog to the issue tracker.
6. Disable logging to the filesystem. Edit the logger.conf file and comment out or delete the line you added in step 1. Using a semi-colon as the first character on the line will comment out the line.
Then reload the logger module like in step 2: