[asterisk-bugs] [JIRA] (ASTERISK-28960) system gets into state where bridges collapse within a few seconds

Wed Jun 24 00:37:25 CDT 2020

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

Asterisk Team commented on ASTERISK-28960:
------------------------------------------

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> system gets into state where bridges collapse within a few seconds
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-28960
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28960
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_simple
>    Affects Versions: 16.10.0
>         Environment: ubunut 18.04, docker asterisk 16.10
>            Reporter: Robert Sutton
>
> system gets into state where bridges collapse within a few seconds
> calls kept flowing into the system, but bridges would collapse without error within a few seconds of starting.
> Seems to be happening about once a week.
> This particular system has only ever run 16.10
> I have a core dump from the running system and full logs including a period with debug set to 4
> below is a typical call flow while the system was in this state.
> {noformat}
> Jun 24 10:53:29      -- Executing [555555555 at routesv2-inbound:1] Set("PJSIP/trunk-00000fa4", "AGIEXITONHANGUP=yes") in new stack
> Jun 24 10:53:29      -- Executing [555555555 at routesv2-inbound:2] Set("PJSIP/trunk-00000fa4", "recovery-did=555555555") in new stack
> Jun 24 10:53:29      -- Executing [555555555 at routesv2-inbound:3] AGI("PJSIP/trunk-00000fa4", "agi://127.0.0.1/route?targ=555555555&ctx=Pre-Inbound") in new stack
> Jun 24 10:53:34      -- AGI Script Executing Application: (mixmonitor) Options: (/var/spool/asterisk/monitor/1592960009.5408-4444444444-3333333333-I-1.wav,,curl 'http://127.0.0.1:8080/rest/recordingMigration/migrate?guid=1592960014936-35584&apiKey=xxxxxxxxxxxx')
> Jun 24 10:53:34    == Begin MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:34      -- Started music on hold, class 'queue17', on channel 'PJSIP/trunk-00000fa4'
> Jun 24 10:53:35      -- PJSIP/417-00000faa is ringing
> Jun 24 10:53:35      -- PJSIP/417-00000faa is ringing
> Jun 24 10:53:40      -- PJSIP/417-00000faa answered
> Jun 24 10:53:40      -- Executing [activity-agi at activity:1] Set("PJSIP/417-00000faa", "AGIEXITONHANGUP=yes") in new stack
> Jun 24 10:53:40      -- Executing [activity-agi at activity:2] AGI("PJSIP/417-00000faa", "agi://127.0.0.1/activityAgi") in new stack
> Jun 24 10:53:40    == Begin MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:40      -- AGI Script Executing Application: (bridge) Options: (PJSIP/trunk-00000fa4,x)
> Jun 24 10:53:40      -- Stopped music on hold on PJSIP/trunk-00000fa4
> Jun 24 10:53:40    == Spawn extension (routesv2-inbound, 555555555, 3) exited non-zero on 'Surrogate/PJSIP/trunk-00000fa4'
> Jun 24 10:53:40      -- Channel PJSIP/trunk-00000fa4 joined 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:40      -- Channel PJSIP/417-00000faa joined 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:40    == Begin MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:40  OK  == End MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:40  OK  == End MixMonitor Recording PJSIP/trunk-00000fa4
> Jun 24 10:53:41      -- Channel PJSIP/trunk-00000fa4 left 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:41      -- Channel PJSIP/417-00000faa left 'simple_bridge' basic-bridge <67256011-e289-430d-bc1c-08b96c97811e>
> Jun 24 10:53:41      -- Manager 'njcontact' from 127.0.0.1, hanging up channel: PJSIP/417-00000faa
> Jun 24 10:53:41    == Spawn extension (activity, activity-agi, 2) exited non-zero on 'PJSIP/417-00000faa'
> Jun 24 10:53:42  OK  == End MixMonitor Recording PJSIP/trunk-00000fa4
> {noformat}
> for future reference:
> {noformat}
> the issue started somewhere between 10:38 and 10:46
> debug  set to level 4 at 10:56:08
> core dump triggered at 10:55:32
> system restart at 10:57:30 approx
> {noformat}

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