Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sun, Jan 15, 2017 at 10:55:01PM +0100, Bernhard Schmidt wrote: > > 3.) I have just uploaded asterisk 1:13.13.1~dfsg-3~exp1 into > experimental, which has the upstream patch for improved pjproject > loglevels attached. Binaries should be available in experimental > tomorrow (I hope). Please test whether this version makes a > difference. I finally found binaries for that version in http://ftp.de.debian.org/debian/pool/main/a/asterisk/ https://packages.qa.debian.org/a/asterisk.html has a link to exp, but only give a "Package not available in this suite." Good news: At first glance, it seems to work. No console cluttering :-) The only side effect I noticed is an additional dependancy on libsdl-image1.2. I still need to make some calls to check for regressions. Thanks a lot for your efforts, Joerg signature.asc Description: PGP signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sun, Jan 15, 2017 at 10:55:01PM +0100, Bernhard Schmidt wrote: > > 1.) Please verify that your initscript is indeed the one shipped by the > current version of the package (md5sum > 965f4ae93665ecbd957ac5b0a1dced52) and that you don't set any > additional options in /etc/default/asterisk # md5sum /etc/init.d/asterisk 965f4ae93665ecbd957ac5b0a1dced52 /etc/init.d/asterisk ~# ps auxwww|grep asterisk root 1365 0.0 0.0 13276 960 pts/4S+ 23:06 0:00 grep asterisk root 11799 0.0 0.0 4284 1564 pts/3S+ Jan07 0:00 /bin/sh /etc/init.d/asterisk debug asterisk 11806 0.5 0.8 2700988 69688 pts/3 Sl+ Jan07 58:50 /usr/sbin/asterisk -p -U asterisk -cvd asterisk 11807 0.0 0.0 15232 1768 pts/3S+ Jan07 0:04 astcanary /var/run/asterisk/alt.asterisk.canary.tweet.tweet.tweet 11806 > > 2.) Please diff _all_ of your Asterisk configuration to the one shipped > in asterisk-config. Something like (untested!) > > mkdir /tmp/asterisk.my > cd /etc/asterisk; for i in *; do sed -r -e '/^\s*;/d' -e '/^\s*$/d' $i > > /tmp/asterisk.my/$i; done > > and the same for an extracted asterisk-config package. Then you need > to diff all files, filter private information and check/try > possible changes yourself. > > I'm afraid this is quite some work. I am indeed afraid this will take a bit of time. Please remind me in a couple of days if I have not come to do that yet. > > 3.) I have just uploaded asterisk 1:13.13.1~dfsg-3~exp1 into > experimental, which has the upstream patch for improved pjproject > loglevels attached. Binaries should be available in experimental > tomorrow (I hope). Please test whether this version makes a > difference. That sounds faster to do than 2.) BTW, my current list of packets is # dpkg-query -W|grep asterisk asterisk1:13.13.1~dfsg-2 asterisk-config 1:13.13.1~dfsg-2 asterisk-core-sounds-en-gsm 1.4.27-1 asterisk-dev1:13.13.1~dfsg-2 asterisk-modules1:13.13.1~dfsg-2 asterisk-prompt-de 2.0-1.1 Thanks for your effort! Bye, Joerg signature.asc Description: PGP signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sat, Jan 14, 2017 at 12:55:08PM +0100, Joerg Dorchain wrote: Hi Joerg, > > > I would like config parts containing personal access details > > > not to be part of the public bug tracker for avoiding security > > > breaches and direct monetary costs arrising from that, so I did > > > not sent them to the public bug report on purpose. > > > > Could you please then send such a diff (or set of config files, if that > > is smaller) privately to Bernhard and to me? > > On the way. Unfortunately I could not find anything obvious in your SIP configuration. Three more things to check, then I'm out of ideas 1.) Please verify that your initscript is indeed the one shipped by the current version of the package (md5sum 965f4ae93665ecbd957ac5b0a1dced52) and that you don't set any additional options in /etc/default/asterisk 2.) Please diff _all_ of your Asterisk configuration to the one shipped in asterisk-config. Something like (untested!) mkdir /tmp/asterisk.my cd /etc/asterisk; for i in *; do sed -r -e '/^\s*;/d' -e '/^\s*$/d' $i > /tmp/asterisk.my/$i; done and the same for an extracted asterisk-config package. Then you need to diff all files, filter private information and check/try possible changes yourself. I'm afraid this is quite some work. 3.) I have just uploaded asterisk 1:13.13.1~dfsg-3~exp1 into experimental, which has the upstream patch for improved pjproject loglevels attached. Binaries should be available in experimental tomorrow (I hope). Please test whether this version makes a difference. Bernhard signature.asc Description: Digital signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sat, Jan 14, 2017 at 12:10:59PM +0200, Tzafrir Cohen wrote: > > > > I would like config parts containing personal access details > > not to be part of the public bug tracker for avoiding security > > breaches and direct monetary costs arrising from that, so I did > > not sent them to the public bug report on purpose. > > Could you please then send such a diff (or set of config files, if that > is smaller) privately to Bernhard and to me? On the way. Bye, Joerg signature.asc Description: PGP signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sat, Jan 14, 2017 at 09:21:59AM +0100, Joerg Dorchain wrote: > On Fri, Jan 13, 2017 at 06:53:15PM +0100, Bernhard Schmidt wrote: > > > > Can you try to diff the content of your /etc/asterisk and the package > > content of asterisk-config to find the relevant setting? > > > > I would like config parts containing personal access details > not to be part of the public bug tracker for avoiding security > breaches and direct monetary costs arrising from that, so I did > not sent them to the public bug report on purpose. Could you please then send such a diff (or set of config files, if that is smaller) privately to Bernhard and to me? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Fri, Jan 13, 2017 at 06:53:15PM +0100, Bernhard Schmidt wrote: > > Can you try to diff the content of your /etc/asterisk and the package > content of asterisk-config to find the relevant setting? > I would like config parts containing personal access details not to be part of the public bug tracker for avoiding security breaches and direct monetary costs arrising from that, so I did not sent them to the public bug report on purpose. Bye, Joerg signature.asc Description: PGP signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sat, Dec 31, 2016 at 09:30:35AM +0100, Joerg Dorchain wrote: Hi Joerg, > 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 > > 09:22:39.015 rtp0x558b74e70 Mutex released by thread timer > > 09:22:39.015 ioq0x7f4f0c001 Mutex: thread timer is waiting > > 09:22:39.015 ioq0x7f4f0c001 Mutex acquired by thread timer > > 09:22:39.015 ioq0x7f4f0c001 Mutex released by thread timer > > 09:22:39.025 rtp0x558b74e70 Mutex: thread timer is waiting > > 09:22:39.025 rtp0x558b74e70 Mutex acquired by thread timer > > 09:22:39.025 rtp0x558b74e70 Mutex released by thread timer > > 09:22:39.025 ioq0x7f4f0c001 Mutex: thread timer is waiting > > 09:22:39.025 ioq0x7f4f0c001 Mutex acquired by thread timer > > 09:22:39.025 ioq0x7f4f0c001 Mutex released by thread timer > > 09:22:39.035 rtp0x558b74e70 Mutex: thread timer is waiting > > 09:22:39.035 rtp0x558b74e70 Mutex acquired by thread timer > > 09:22:39.035 rtp0x558b74e70 Mutex released by thread timer > > 09:22:39.035 ioq0x7f4f0c001 Mutex: thread timer is waiting > > 09:22:39.035 ioq0x7f4f0c001 Mutex acquired by thread timer > > 09:22:39.035 ioq0x7f4f0c001 Mutex released by thread timer > > 09:22:39.045 rtp0x558b74e70 Mutex: thread timer is waiting > > 09:22:39.045 rtp0x558b74e70 Mutex acquired by thread timer > > 09:22:39.045 rtp0x558b74e70 Mutex released by thread timer > > 09:22:39.045 ioq0x7f4f0c001 Mutex: thread timer is waiting > > 09:22:39.045 ioq0x7f4f0c001 Mutex acquired by thread timer > > 09:22:39.045 ioq0x7f4f0c001 Mutex released by thread timer > 09:22:39.055 rtp0x558b74e70 Mutex: thread timer is waiting > 09:22:39.055 rtp0x558b74e70 Mutex acquired by thread timer > 09:22:39.055 rtp0x558b74e70 Mutex released by thread timer > 09:22:39.055 ioq0x7f4f0c001 Mutex: thread timer is waiting > 09:22:39.055 ioq0x7f4f0c001 Mutex acquired by thread timer > 09:22:39.055 ioq0x7f4f0c001 Mutex released by thread timer > ... > > This effectivly renders the debug console unusable. I cannot reproduce this with both my config and the sample config from a clean reinstall of asterisk(-config). So something in your config seems to be triggering this. Can you try to diff the content of your /etc/asterisk and the package content of asterisk-config to find the relevant setting? Bernhard signature.asc Description: Digital signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sun, Jan 01, 2017 at 09:41:57PM +0100, Bernhard Schmidt wrote: > > I think this could fix it. > > https://issues.asterisk.org/jira/browse/ASTERISK-26630 > https://gerrit.asterisk.org/#/c/4516/ > > It is already in the upstream Asterisk 13 branch, but not in any 13.x > release. But I'm sure this will be sooner than later. You probably know better, I found the patch in the pipe for 14.x release. Anyway, it will come, and in a way that I can use it even before switching from chan_sip to chan_pjproject :-) > > If you change pjproject.conf to read > > [log_mappings] > asterisk_debug = "3,4,5,6" > > does that help? No. I would not expect so, as /etc/init.d/asterisk debug starts asterisk with debug level output. Bye, Joerg signature.asc Description: PGP signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
Control: forwarded -1 https://issues.asterisk.org/jira/browse/ASTERISK-26630 On Sun, Jan 01, 2017 at 12:09:58PM +0100, Joerg Dorchain wrote: Hi, > Downgrading these to 2.5.5~dfsg-3 from snapshot.debian.org indeed > helped the problem. So far, so easy. > > To keep me happy, I see some options. Most obvious, do we really > need that loglevel? If yes, it should be mentioned in > pjproject.conf, with the option to silence them, maybe with a > word of warning for the clutter on the console. I think this could fix it. https://issues.asterisk.org/jira/browse/ASTERISK-26630 https://gerrit.asterisk.org/#/c/4516/ It is already in the upstream Asterisk 13 branch, but not in any 13.x release. But I'm sure this will be sooner than later. If you change pjproject.conf to read [log_mappings] asterisk_debug = "3,4,5,6" does that help? Bernhard signature.asc Description: Digital signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sun, Jan 01, 2017 at 11:22:25AM +0100, Bernhard Schmidt wrote: > Hi, > > > The messages comes from pjproject. 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? > > As a sidenote, I have enabled log level 6 in pjproject 2.5.5~dfsg-4 > (which has hit testing as well yesterday) following the non-ABI breaking > suggestions in > https://github.com/asterisk/asterisk/blob/master/third-party/pjproject/patches/config_site.h > . So these messages weren't generated before I guess. > > Joerg, can you test downgrading pjproject to -3? Hm, I have some packages with that version number indeed: dpkg-query -W|grep 2.5.5~dfsg-5 libpj2:amd642.5.5~dfsg-5 libpjlib-util2:amd642.5.5~dfsg-5 libpjmedia-audiodev2:amd64 2.5.5~dfsg-5 libpjmedia-codec2:amd64 2.5.5~dfsg-5 libpjmedia-videodev2:amd64 2.5.5~dfsg-5 libpjmedia2:amd64 2.5.5~dfsg-5 libpjnath2:amd642.5.5~dfsg-5 libpjsip-simple2:amd64 2.5.5~dfsg-5 libpjsip-ua2:amd64 2.5.5~dfsg-5 libpjsip2:amd64 2.5.5~dfsg-5 libpjsua2:amd64 2.5.5~dfsg-5 libpjsua2-2v5:amd64 2.5.5~dfsg-5 and asterisk has it in its dependency chain. Downgrading these to 2.5.5~dfsg-3 from snapshot.debian.org indeed helped the problem. So far, so easy. To keep me happy, I see some options. Most obvious, do we really need that loglevel? If yes, it should be mentioned in pjproject.conf, with the option to silence them, maybe with a word of warning for the clutter on the console. Bye, Joerg signature.asc Description: PGP signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
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=-cvd. 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 -rvd, 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 signature.asc Description: PGP signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
On Sun, Jan 01, 2017 at 11:06:30AM +0100, Tzafrir Cohen wrote: Hi, > The messages comes from pjproject. 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? As a sidenote, I have enabled log level 6 in pjproject 2.5.5~dfsg-4 (which has hit testing as well yesterday) following the non-ABI breaking suggestions in https://github.com/asterisk/asterisk/blob/master/third-party/pjproject/patches/config_site.h . So these messages weren't generated before I guess. Joerg, can you test downgrading pjproject to -3? Bernhard signature.asc Description: Digital signature
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
Hi, 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=-cvd. 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. The messages comes from pjproject. 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? 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. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best tzaf...@debian.org|| friend
Bug#849804: /etc/init.d/asterisk debug unusable for continous output
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 09:22:39.015 rtp0x558b74e70 Mutex released by thread timer 09:22:39.015 ioq0x7f4f0c001 Mutex: thread timer is waiting 09:22:39.015 ioq0x7f4f0c001 Mutex acquired by thread timer 09:22:39.015 ioq0x7f4f0c001 Mutex released by thread timer 09:22:39.025 rtp0x558b74e70 Mutex: thread timer is waiting 09:22:39.025 rtp0x558b74e70 Mutex acquired by thread timer 09:22:39.025 rtp0x558b74e70 Mutex released by thread timer 09:22:39.025 ioq0x7f4f0c001 Mutex: thread timer is waiting 09:22:39.025 ioq0x7f4f0c001 Mutex acquired by thread timer 09:22:39.025 ioq0x7f4f0c001 Mutex released by thread timer 09:22:39.035 rtp0x558b74e70 Mutex: thread timer is waiting 09:22:39.035 rtp0x558b74e70 Mutex acquired by thread timer 09:22:39.035 rtp0x558b74e70 Mutex released by thread timer 09:22:39.035 ioq0x7f4f0c001 Mutex: thread timer is waiting 09:22:39.035 ioq0x7f4f0c001 Mutex acquired by thread timer 09:22:39.035 ioq0x7f4f0c001 Mutex released by thread timer 09:22:39.045 rtp0x558b74e70 Mutex: thread timer is waiting 09:22:39.045 rtp0x558b74e70 Mutex acquired by thread timer 09:22:39.045 rtp0x558b74e70 Mutex released by thread timer 09:22:39.045 ioq0x7f4f0c001 Mutex: thread timer is waiting 09:22:39.045 ioq0x7f4f0c001 Mutex acquired by thread timer 09:22:39.045 ioq0x7f4f0c001 Mutex released by thread timer 09:22:39.055 rtp0x558b74e70 Mutex: thread timer is waiting 09:22:39.055 rtp0x558b74e70 Mutex acquired by thread timer 09:22:39.055 rtp0x558b74e70 Mutex released by thread timer 09:22:39.055 ioq0x7f4f0c001 Mutex: thread timer is waiting 09:22:39.055 ioq0x7f4f0c001 Mutex acquired by thread timer 09:22:39.055 ioq0x7f4f0c001 Mutex released by thread timer ... This effectivly renders the debug console unusable. Bye, Joerg signature.asc Description: PGP signature
