[asterisk-bugs] [JIRA] (ASTERISK-15009) Exceptionally long voice queue length queuing to Local/XXXXXXX

[Kevin Harwell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-15009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252374#comment-252374 ] 

Kevin Harwell commented on ASTERISK-15009:
------------------------------------------

[~jguarniz] One possible reason this message may occur is due to a system being overloaded.

However your inquiry with regards to your problem would be better served in a different forum at this time.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> Exceptionally long voice queue length queuing to Local/XXXXXXX
> --------------------------------------------------------------
>
>                 Key: ASTERISK-15009
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-15009
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/Channels
>            Reporter: daren ferreira
>
> Hello
> I'm not in the habit to post request but i tried all i can to solve it without success.
> I saw a thread (ASTERISK-14558) dealing with a look alike problem but i'm not sure it's the same and don't want to disturb it if it is different.
> The symptoms are channels cut or communications disturbed - IAX peers qualification failure, jb sync lost etc.. as showing below:
> [Oct 16 17:55:40] WARNING[2514]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to IAX2/blahblah
> [Oct 16 17:55:40] WARNING[2511]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to IAX2/blahblah
> [Oct 16 17:57:38] NOTICE[2513]: chan_iax2.c:9186 __iax2_poke_noanswer: Peer 'XXX' is now UNREACHABLE! Time: 9
> [Oct 16 17:57:38] NOTICE[2505]: chan_iax2.c:9186 __iax2_poke_noanswer: Peer 'YYY' is now UNREACHABLE! Time: 9
> [Oct 16 17:57:55] WARNING[2505]: chan_iax2.c:804 jb_warning_output: Resyncing the jb. last_delay 0, this delay 22334, threshold 1000, new offset -22334
> [Oct 16 17:57:57] WARNING[2510]: chan_iax2.c:804 jb_warning_output: Resyncing the jb. last_delay -135, this delay 1529, threshold 1000, new offset -1529
> [Oct 16 17:58:05] NOTICE[2507]: chan_iax2.c:8264 socket_process: Peer 'XXX' is now REACHABLE! Time: 4
> [Oct 16 17:58:07] NOTICE[2511]: chan_iax2.c:8264 socket_process: Peer 'YYY' is now REACHABLE! Time: 11
> the only common point i have are Local channels in race condition.
> I have been having such problems for a quite long period and got rid of them by getting rid of local channels (by moving on others servers not using them), but for some services i can hardly get rid of local channels...
> The problems disappeared on servers not using local channels but still goes on with this server.
> As ASTERISK-14558 i had, some weeks ago, file write errors, it seems to be related to hundreds of messages i get while the error occurs, so i applied the "no duplicate log patch", it seems to have no effect on the number of "Exceptionally long voice queue length queuing to Local/" messages (i may have missed something) and worse, the jb resyncing and peers lagged or unreachable messages still goes on.
> I tried the DEBUG_CHANNEL_LOCKS flag but the only lock i got was
> === Thread ID: 1077410128 (do_monitor           started at [16780] chan_sip.c restart_monitor())
> === ---> Lock #0 (chan_sip.c): MUTEX 16726 do_monitor &monlock 0x7f3796d4c620 (1)
> === ---> Lock #1 (chan_sip.c): MUTEX 16748 do_monitor &(peer)->_lock 0x7f379c134af0 (1)
> I removed DEBUG_CHANNEL_LOCKS flag because of crash that this flag lead to.
> If that problem is considered identical to ASTERISK-14558 don't hesitate to merge it to this, if different... let me know.
> If any information is requested, please let me know...



--
This message was sent by Atlassian JIRA
(v6.2#6252)