[asterisk-bugs] [JIRA] (ASTERISK-28395) Asterisk occasionally fails to hangup channels

Kevin Harwell (JIRA) noreply at issues.asterisk.org
Thu Apr 25 18:25:47 CDT 2019


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

Kevin Harwell commented on ASTERISK-28395:
------------------------------------------

[~stefffan at gmx.de] Let me start by saying thank you for the level of effort put into your report, and into the collection of the data!

As a heads up I'll mention that these channel drivers don't see a lot of updates, and bug fixes these days. For instance, _chan_sip_ is officially deprecated, and is mostly community supported by developers outside Sangoma. So "fix times" will be reflective of that.

That being said there are at least two things to try that could be helpful:

1. You're on 13.8.2. This of course is an older version of Asterisk. Please upgrade to the latest release (currently 13.26.0 and 16.3.0). _chan_iax_ doesn't appear to have as many updates since then, but there are a few in _chan_sip_, so maybe something got fixed.

2. A backtrace of Asterisk when a channel gets stuck could potentially help. Running an older version you'll have to do this more manually [1]. However, if you are able to upgrade then you can use the _ast_coredumper_ script [2] to obtain a "running" core dump & subsequent backtrace of Asterisk. *Note*, using _ast_coredumper's_ '--running' option will interrupt call processing.

[1] https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=5243139
[2] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

> Asterisk occasionally fails to hangup channels
> ----------------------------------------------
>
>                 Key: ASTERISK-28395
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28395
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2, Channels/chan_sip/General, PBX/General
>    Affects Versions: 13.8.2
>         Environment: Debian Linux
>            Reporter: Stefan Repke
>         Attachments: case1.txt, case2.txt, case3.txt
>
>
> Our Asterisk servers occasionally fail to hangup channels (IAX2 or SIP).
> We are running version: 13.8.2.
> The symptoms are as follows:
> * We observe a HangupRequest event via AMI but the Hangup event does not occur.
> * One Asterisk thread starts consuming 100% CPU, i.e. burning one core.
> * Strange warning messages occur in CLI and log repeatedly every few seconds:
> ** IAX case:
> {noformat}
> WARNING[15982] chan_iax2.c: Max retries exceeded to host 10.101.1.5 on IAX2/125-5832 (type = 6, subclass = 11, ts=119996, seqno=24)
> {noformat}
> ** SIP case:
> {noformat}
> WARNING[21518]: chan_sip.c:4333 __sip_autodestruct: Autodestruct on dialog 'e8954fa42ffee2d1ace1ac4c6323d990 at 10.249.4.97' with owner SIP/999222-0000149c in place (Method: BYE). Rescheduling destruction for 10000 ms
> {noformat}
> * The channel stays alive (i.e. still visible via CLI, AMI status, ARI, etc).
> * The channel cannot be hungup (via CLI, AMI, etc).
> * The only fix is to restart Asterisk.
> Up to now, we were facing this problem three times:
> # IAX2 channel, thread {{bridge_channel_depart_thread}}
> # SIP channel, thread {{pbx_thread}}
> # SIP channel, thread {{pbx_thread}}, with thread debugging enabled (includes {{strace}} output).
> I've attached the debug info for each of the above cases.
> Maybe this bug is related to:
> * ASTERISK-25911
> * ASTERISK-27538
> ---
> I can imagine that you need more detailed information to track down this bug.
> If so, please let me know how I can provide it and I will try to reproduce this problem.



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



More information about the asterisk-bugs mailing list