[asterisk-bugs] [JIRA] Commented: (ASTERISK-20335) Crash in ast_cel_report_event

[aragon (JIRA)]

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

aragon commented on ASTERISK-20335:
-----------------------------------

The only thing I find unusual is that there are a lot of ACK's hanging around sip show channels which you can see in the previous attachments (sip show channels)
There are also a lot of zombies hanging around; I think because of the ACK's (I hate zombies).  I think this leads to the locks and crashes because the call limit is reached.  If I had to guess it is because something is waiting on cel to write data to MySQL (pure speculation).
We had DEBUG_THREADS enabled to also capture the core show locks info.
You are correct when you assume it will be some time before we attempt to enable cel any time soon.
But we are willing to test a patch if you can figure things out.
We also haven't had any locks since disabling cel.

> Crash in ast_cel_report_event
> -----------------------------
>
>                 Key: ASTERISK-20335
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20335
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local
>    Affects Versions: 1.8.16.0
>         Environment: Centos server 5.8x64, 8 core CPU, 8GB RAM
>            Reporter: aragon
>            Assignee: aragon
>            Severity: Critical
>         Attachments: AST18-core-verbose.txt, asterisk.txt, core show channels.txt, default-dial-cav-joh-002-000918.txt, optimized backtrace.txt, SIP show channels.txt, verbose CLI sip set debug on.txt
>
>
> On a pretty busy system we get deadlocks and crashes daily since installing Asterisk 1.8.16rc1
> Upgraded from 1.8.12 because we were having problems with leaking bye's fixed in ASTERISK-19455
> We were able to collect verbose CLI, core show channels, sip show channels, and Asterisk CLI with sip set debug on.
> Also back traced a core dump file but this is an optimized build since we could not run non-optimized in this environment.
> Including the back trace anyway since it might help diagnose the problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira