asterisk users - Jul 2018 - dialplan reload not showing debug info even with debug on (ast 15.5)

I've not needed to do a dialplan reload for a while, so I don't know
exactly which version is stopped working, but on 15.5, I'm not seeing
ANY debug info at any debug level.
So I'm not really sure how to find mistakes in the dialplan.  This is
all I get... how do I enable this debug mode to see the previous
behaviour? Thanks

asterisk -rvvvvvddddd
(enters console)
dialplan reload
Dialplan reloaded.
[...]
    -- pbx_config successfully loaded 125 contexts (enable debug for details).

On Sat, Jul 28, 2018 at 1:10 PM, Jonathan H <lardconcepts at gmail.com>
wrote:
> I've not needed to do a dialplan reload for a while, so I don't
know
> exactly which version is stopped working, but on 15.5, I'm not seeing
> ANY debug info at any debug level.
> So I'm not really sure how to find mistakes in the dialplan.  This is
> all I get... how do I enable this debug mode to see the previous
> behaviour? Thanks
>
> asterisk -rvvvvvddddd
> (enters console)
> dialplan reload
> Dialplan reloaded.
> [...]
>     -- pbx_config successfully loaded 125 contexts (enable debug for
> details).
>
Many of those messages now go out as DEBUG level 1 messages.  You would
need to enable those to go out to your console in logger.conf if they
aren't enabled.
Or you need to look at one of the logging files (like full) that has debug
messages
routed to it.

https://issues.asterisk.org/jira/browse/ASTERISK-27084 is the issue that
did that
which went out in v15.3.0 and is mentioned in the CHANGES file:

Core
------------------
 * During dialplan reload log messages are produced for each context,
   extension and include.  These messages are no longer printed by the
   verbose loggers, they are now only logged as debug messages.


Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180729/047372aa/attachment.html>

OK, many thanks for that. Not sure I see the point of the change, but
at least I can get the info back by changing

console => notice,warning,error
to
console => notice,warning,error,debug

That said, dialplan reload seems to show significantly fewer items
than before. I've got loads of extensions, and it does indeed seem to
reload them all, but only shows about 1/4 of them in the console when
doing dialplan reload. Hmmm...

Incidentally, just while I'm here, is there a particular reason that
debug can only every be pushed higher when connecting to the console?
it's always been the case since I started using Asterisk 3 years ago
so I guess there's a reason, and I never questioned it before. I'm
just curious!
For example:


asterisk -rvddd
Core debug was 2 and is now 3.

asterisk -rvdddd
Core debug was 3 and is now 4.

asterisk -rvdd
Core debug is still 4.

asterisk -rvd
Core debug is still 4.

But it always respects "core set debug" in whichever direction of
verbosity is required.

Thanks again!
On Sun, 29 Jul 2018 at 13:14, Richard Mudgett <rmudgett at digium.com>
wrote:
>
>
>
> On Sat, Jul 28, 2018 at 1:10 PM, Jonathan H <lardconcepts at
gmail.com> wrote:
>>
>> I've not needed to do a dialplan reload for a while, so I don't
know
>> exactly which version is stopped working, but on 15.5, I'm not
seeing
>> ANY debug info at any debug level.
>> So I'm not really sure how to find mistakes in the dialplan.  This
is
>> all I get... how do I enable this debug mode to see the previous
>> behaviour? Thanks
>>
>> asterisk -rvvvvvddddd
>> (enters console)
>> dialplan reload
>> Dialplan reloaded.
>> [...]
>>     -- pbx_config successfully loaded 125 contexts (enable debug for
details).
>
>
> Many of those messages now go out as DEBUG level 1 messages.  You would
> need to enable those to go out to your console in logger.conf if they
aren't enabled.
> Or you need to look at one of the logging files (like full) that has debug
messages
> routed to it.
>
> https://issues.asterisk.org/jira/browse/ASTERISK-27084 is the issue that
did that
> which went out in v15.3.0 and is mentioned in the CHANGES file:
>
> Core
> ------------------
>  * During dialplan reload log messages are produced for each context,
>    extension and include.  These messages are no longer printed by the
>    verbose loggers, they are now only logged as debug messages.
>
>
> Richard
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users