[Home]

Summary:ASTERISK-21122: Documentation on the various methods of changing verbosity can be confusing
Reporter:Richard Miller (ulogic)Labels:
Date Opened:2013-02-16 01:39:28.000-0600Date Closed:
Priority:MinorRegression?Yes
Status:Open/NewComponents:Core/General Documentation
Versions:11.3.0 13.18.4 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) verbosetesting.txt
Description:When issuing "asterisk -r", no messages are shown.
"core show settings" displays
Verbosity: 3
But until you issue
"core set verbose 3"
nothing is displayed in the current console session

Workaround:

asterisk -rvvv
Comments:By: Matt Jordan (mjordan) 2013-02-16 11:02:34.562-0600

From the CHANGES file and the [New in 11|https://wiki.asterisk.org/wiki/display/AST/New+in+11]:

{quote}
Each logging destination and console now have an independent notion of the current verbosity level. logger.conf now allows an optional argument to the 'verbose' specifier, indicating the level of verbosity sent to that particular logging destination. Additionally, remote consoles now each have their own verbosity level. The command core set verbose will now set a separate level for each remote console without affecting any other console.
{quote}

What is set in your logger.conf?

By: Richard Miller (ulogic) 2013-02-16 12:17:05.020-0600

Logger.conf contains
console => notice,warning,error,debug,verbose(3)

I would think that the default would be whatever verbosity the initial instance was started at (via safe_asterisk) and also the one displayed by "core show settings".

By: Rusty Newton (rnewton) 2013-02-18 19:45:51.408-0600

Richard, hopefully this helps out. After a little testing:

'core show settings': the verbosity displayed from this command appears to only be affected by the setting in asterisk.conf

'core set verbose <integer>': sets the verbosity for the remote console you are on

defining VERBOSE in logger.conf for a file like "full" does result in at least VERBOSE level 3 messages being written to the full log

defining VERBOSE in logger.conf for the "console" only results in a level of 0 for any remote console

defining VERBOSE with an integer level in logger.conf for the "console" results in a level of 0 for any remote console

defining VERBOSE with an integer level in asterisk.conf results in a default verbosity of that same level on any remote console

The logger.conf documentation is ambiguous regarding the integer level and whether the special console filename is affected or not "; Verbose takes an additional argument, in the form of an integer level.; Messages with higher levels will be ignored.  If verbose is specified at; all, it will default to 3."


Concerning the 'v' and 'd' options for the Asterisk binary - asterisk.conf seems to override those. So starting asterisk with 'asterisk -cvvv' won't do anything if asterisk.conf has verbose=0.


So in summary, if you set a level for verbosity in asterisk.conf then that will be your default for any remote console.  The documentation in logger.conf and the text for 'core show settings', as well as the man page for asterisk should probably be tweaked for clarification.


By: Rusty Newton (rnewton) 2013-02-18 19:48:03.591-0600

Attached a verbosetesting.txt summarizing some notes on the testing I did with verbose for reference.

By: Richard Miller (ulogic) 2013-02-19 01:08:27.216-0600

Thank you for your thorough testing and the clarification of the verbosity behavior you published in the attachment.