trixter aka Bret McDanel
2006-Jun-05 20:32 UTC
[Asterisk-Users] show channel issue with 1.2.9
has anyone else noticed what appears to be a threading issue in asterisk 1.2.9 (it broke sometime between 1.2.4 and 1.2.9) where if you have about > 50 calls and do asterisk -rx show channels it will display the header but nothing about channels, total calls, active calls, etc. -- Trixter http://www.0xdecafbad.com Bret McDanel Belfast IE +44 28 9099 6461 DE +49 801 777 555 3402 Utrecht NL +31 306 553058 US WA +1 360 207 0479 US NY +1 516 687 5200 FreeWorldDialup: 635378 http://www.trxtel.com we pay you to terminate calls with us! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20060605/babc7863/attachment.pgp
asterisk-user@dualcall.com
2006-Jun-05 22:37 UTC
[Asterisk-Users] show channel issue with 1.2.9
try asterisk -rx 'show channels' Cheers, Madhawa trixter aka Bret McDanel wrote:> has anyone else noticed what appears to be a threading issue in asterisk > 1.2.9 (it broke sometime between 1.2.4 and 1.2.9) where if you have > about > 50 calls and do > asterisk -rx show channels > it will display the header but nothing about channels, total calls, > active calls, etc. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
----- trixter aka Bret McDanel <trixter@0xdecafbad.com> wrote:> It acts almost like a race condition that 'wins' when the channel > count > is low, but looses almost always when it gets to a moderate level. > Why > I was thinking it was a threading issue.I believe this has been a known problem for a while, where 'asterisk -rx' does not reliably wait until the output has been generated/flushed before exiting the remote console process. Why it would have suddenly started affecting you I can't guess :-) -- Kevin P. Fleming Senior Software Engineer Digium, Inc.