[asterisk-bugs] [JIRA] Feedback Entered: (ASTERISK-20335) Crash in ast_cel_report_event
aragon (JIRA)
noreply at issues.asterisk.org
Wed Aug 29 09:23:07 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
aragon updated ASTERISK-20335:
------------------------------
Status: Waiting for Feedback (was: Waiting for Feedback)
gdb asterisk --pid=`pidof asterisk`
And doing "thread apply all bt" would give the needed information?
> 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, core show channels.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 https://issues.asterisk.org/jira/browse/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
More information about the asterisk-bugs
mailing list