Summary:ASTERISK-04234: [request] Enable debug on by default if set in logger.conf
Reporter:Chris Hozian (chozian)Labels:
Date Opened:2005-05-19 15:15:03Date Closed:2011-06-07 14:04:51
Versions:Frequency of
Description:I am no longer receiving debug output on the console.  This problem was introduced sometime in the last couple of days.

My logger.conf file contains:

console => notice,warning,error,debug

I was getting debug output on the console a couple days ago.  I have made no modifications to my logger.conf file since then.  I do a CVS update every morning.  I just now noticed the problem.
Comments:By: Paul Cadach (pcadach) 2005-05-19 15:18:33

Probably you run Asterisk without debugging. Is "set debug 1" helps?

By: Michael Jerris (mikej) 2005-05-19 15:35:40

This is the result of http://bugs.digium.com/view.php?id=4294.  You need to set debug 1.  Please reopen if this does not fix the issue.

By: Chris Hozian (chozian) 2005-05-19 15:45:26

I have tried "show debug 1".  It is a valid workaround.

I don't like the functionality of that patch listed at 4294.  If I set debug for my console in logger.conf it should output debug information on my console like it did before.  I shouldn't have to type "show debug 1" in order to get debug information on my console.  I feel that many people will be disappointed with this change.

Debug should only get set to 0 if debug is not listed for the console in logger.conf.

What does everyone else think about this?

By: Mark Spencer (markster) 2005-05-19 16:29:56

Reverted the broken patch from 4294

By: Kevin P. Fleming (kpfleming) 2005-05-19 16:30:30

logger.conf controls what is accepted for display/logging, not what is generated. Also keep in mind that you could have 'debug' listed for any or all entries in logger.conf, not just the console.

Essentially, this is the same as 'verbose'... even with 'verbose' in an entry in logger.conf, if 'set verbose 1' (or higher) has not been executed, then nothing will be displayed/logged.