[asterisk-bugs] [JIRA] Commented: (ASTERISK-20347) Asterisk 1.8.16rc1 deadlock in cdr_mysql

[aragon (JIRA)]

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

aragon commented on ASTERISK-20347:
-----------------------------------

This is an 8 core 64 bit machine with 8 GB RAM.
And even so the system was so bogged down by the non-optimized build I installed last night that no phones could even register.  The system was completely unusable.  The best we were able to do here is to collect some core show locks data before the system had a chance to lock.  I've attached those logs to this ticket.

I hope there is enough data already provided to get a handle on this issue and get it fixed because I don't know what else to do...  

> Asterisk 1.8.16rc1 deadlock in cdr_mysql
> ----------------------------------------
>
>                 Key: ASTERISK-20347
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20347
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/cdr_mysql
>    Affects Versions: 1.8.16.0
>         Environment: Centos 5.8 x64, 8core, 8GB RAM
>            Reporter: aragon
>            Severity: Critical
>         Attachments: coreshowlocks.txt, thread-apply-all-bt.txt
>
>
> As per Matt Jordan I am opening a bug report for a deadlock found in Asterisk 1.8.16rc and cdr_mysql.
> All I have for now is a gdb backtrace unoptimized but should soon be able to provide a non-optimized bt and core show locks output.  Opening ticket without that for now...

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