File: HOWTO_collect_debug_information.txt

package info (click to toggle)
asterisk 1%3A1.8.13.1~dfsg1-3%2Bdeb7u3
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 49,336 kB
  • sloc: ansic: 497,975; sh: 11,763; cpp: 5,934; makefile: 3,065; perl: 3,019; yacc: 2,147; xml: 498; sql: 387; tcl: 113; php: 62; python: 42
file content (89 lines) | stat: -rw-r--r-- 2,640 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
===============================================================================
===
=== HowTo: Collect Debug Information for the Asterisk Issue Tracker
===
=== Written by: Paul Belanger
=== Last updated: 2010-04-12
===============================================================================

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
-------------------------------------------------------------------------------
--- PREREQUISITES
-------------------------------------------------------------------------------

- Asterisk 1.4.30 or greater.

-------------------------------------------------------------------------------
--- STEPS
-------------------------------------------------------------------------------

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

   myDebugLog => notice,warning,error,debug,verbose,dtmf

2. From the Asterisk CLI, restart the logger module:

   *CLI> core set verbose 15
   *CLI> core set debug 15
   *CLI> module reload logger

   Optionally, if you've used this file to record data previously, then rotate
   the logs:

   *CLI> logger rotate

2.1. Depending on your issue, be sure to enable the channel driver logging.

     SIP (1.6.0 or higher)

        *CLI> sip set debug on

     SIP (1.4)

        *CLI> sip set debug

     IAX2 (1.6.0 or higher)

        *CLI> iax2 set debug on

     IAX2 (1.4)

        *CLI> iax2 set debug

3. Reproduce your issue.

4. Once finished, be sure to disable the extra debbuging:

   *CLI> core set verbose 0
   *CLI> core set debug 0

4.1. Again, remember to disable any extra logging if you enabled it in the
     channel driver.

     SIP (1.4 or higher)

        *CLI> sip set debug off

     IAX2 (1.4 or higher)

        *CLI> iax2 set debug off

5. Upload the file located in /var/log/asterisk/myDebugLog to the issue tracker.

   *** IMPORTANT ***
   Do NOT post the output of your file as a comment. This clutters the issue
   and will only result in your comment being deleted.

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:

   *CLI> module reload logger