[asterisk-bugs] [JIRA] (ASTERISK-28605) chan_dahdi: Deadlock in Hangup Scenarios with concurrent command pri show span X

[George Joseph (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Joseph updated ASTERISK-28605:
-------------------------------------

    Assignee: Dirk Wendland  (was: George Joseph)
      Status: Waiting for Feedback  (was: Open)

Unfortunately,  the backtrace files you attached don't have the debugging symbols included in them.   How did you install Asterisk, from source?  If so, can you rebuild with the DONT_OPTIMIZE flag set and the BETTER_BACKTRACES flag unset, make sure the binaries aren't stripped and then re-create the issue (not on a production system of course)?

If you can do that, run
{noformat}
ast_coredumper --tarball-coredumps --running --no-default-search
{noformat}

The resulting tarball will help us narrow down the original issue.  You can then host the tarball on Google Drive, Dropbox, etc and give us the link.


> chan_dahdi: Deadlock in Hangup Scenarios with concurrent command pri show span X
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28605
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28605
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/General
>    Affects Versions: 16.6.0, 16.6.1
>         Environment: Asterisk 16.6 CentOs 6
>            Reporter: Dirk Wendland
>            Assignee: Dirk Wendland
>         Attachments: core-asterisk-running-2019-11-08T11-08-15+0100-brief.txt, core-asterisk-running-2019-11-08T11-08-15+0100-full.txt, core-asterisk-running-2019-11-08T11-08-15+0100-locks.txt, core-asterisk-running-2019-11-08T11-08-15+0100-thread1.txt, currentLocks.txt
>
>
> We have a Szenario with an high Call Flow ( load tests ).
> Szenario:
> 4 S2M Ports => 60 channels go up in the same second 60 Channels hangs up in the same second
> Every few seconds we check the ISN Lines with the command:
> pri show span X
> After a few iterations asterisk will stop working.
> On the console we can fire up that command only one time then that command line interface hangs.
> localhost*CLI> pri show span 4
> Primary D-channel: 109
> Status: Up, Active
> The next ( Switchtype ) will not be printed
> -----------------------------
> We found the patch/task that created that issue.
> ASTERISK-28525
> If we revert that commit everything works fine.
> Greetings
> Dirk



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