[asterisk-bugs] [JIRA] (ASTERISK-25349) Asterisk freeze due to schedule ID cancellation failure

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25349:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Asterisk freeze due to schedule ID cancellation failure
> -------------------------------------------------------
>
>                 Key: ASTERISK-25349
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25349
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.32.0
>         Environment: Linux Debian 7.7
> 3.2.0-4-amd64
>            Reporter: Philip Mott
>            Severity: Critical
>
> The issue starts when we get a schedule ID warning from Asterisk, of which I have provided a few examples below.  Then over the next minute or so Asterisk seems to seize up, in that it stops processing any SIP data and calls stop flowing.  The only way to resolve the issue seems to be to restart Asterisk.  Unfortunately we are unable to provide a backtrace, as implementing debugging symbols is not an option as Asterisk being used in a high-performance production environment and we do not know how to replicate the issue ourselves.  I really hope you are able to fix this soon, as we route over 100 million calls per month and it is the only major source of instability we have found in your platform.
> WARNING[41873] chan_sip.c: Unable to cancel schedule ID 1294416.  This is probably a bug (chan_sip.c: send_response, line 4400).
> WARNING[1473] chan_sip.c: Unable to cancel schedule ID 2566854.  This is probably a bug (chan_sip.c: sip_hangup, line 6605).
> WARNING[1494] chan_sip.c: Unable to cancel schedule ID 177341.  This is probably a bug (chan_sip.c: update_provisional_keepalive, line 4341).



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