Bug#849804: /etc/init.d/asterisk debug unusable for continous output

[Joerg Dorchain]

On Sun, Jan 01, 2017 at 11:06:30AM +0100, Tzafrir Cohen wrote:
> On Sat, Dec 31, 2016 at 09:30:35AM +0100, Joerg Dorchain wrote:
> > Package: asterisk
> > Version: 1:13.13.1~dfsg-2
> > 
> > Hello,
> > 
> > following testing, after upgrading to asterisk 1:13.13.1~dfsg-2,
> > /etc/init.d/asterisk debug endlessly repeats the following screen
> > output rapidly:
> > ...
> > 09:22:39.015 rtp0x558b74e70  Mutex: thread timer is waiting
> > 09:22:39.015 rtp0x558b74e70  Mutex acquired by thread timer
> 
> AST_DEBUG_PARAMS=-cvvvvvddddd. That is: verbose level 4 and debug level
> 5. It also means that asterisk remains attached to the terminal it was
> run from and offers aconsole there. Frankly I hardly recall needing to
> use this while debugging and frankly I completely forgot this option.

I like it as I start my low-usage home PBX manually.

When I start it with /etc/init.d/asterisk start, and then connect
to the console with asterisk -rvvvvvddddd, I do not see these
messages. It only says Core debug is still 6.

I suppose some logging logic changed from the previous release
when there is a controlling tty at startup.

> The messages comes from pjproject.

I do not use pjproject knowingly. As least, I do not have any
modules loaded that have *pj* in the name and use chan_sip for
sip connections.

> The messages are relatively low
> priority ones there.
> 
> However just from reading the code I'm a bit lost. That message seems to
> be at log priorty 6 in pjproject:
> http://sources.debian.net/src/pjproject/2.5.5~dfsg-5/pjlib/src/pj/os_core_unix.c/?hl=1361#L1361
> (And likewise in 2.4.5)
> 
> Asterisk maps by default pjproject log levels 3, 4 and 5 to "debug" (see
> pjproject.conf) and I don't see anything about 6. Do you have anything
> customized there? Can you play with the definitions in that file?

I have not modified this file from the default distribution. I
can try different settings there. What would you suggest?

> 
> That said, I'm not really surprise if at debug level 5 the console is
> not usable. I suppose there may be other messages that may lead to such
> a flood.

Actually, I use that feature (/etc/init.d/asterisk debug) since
asterisk 1.2 and it worked quite well since then. It helps me to
determine reasons for failed calls more easily.

Bye,

Joerg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 898 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20170101/7cf281f7/attachment.sig>