[asterisk-bugs] [JIRA] (ASTERISK-23328) Asterisk crash in ast_cdr_setapp() at cdr.c

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-23328:
----------------------------------------

I threw this back into Triage because quite frankly, I have no idea how this got into this state - and I have no idea how we would go about fixing something that doesn't seem to mesh with what the backtrace is showing us.
                
> Asterisk crash in ast_cdr_setapp() at cdr.c
> -------------------------------------------
>
>                 Key: ASTERISK-23328
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23328
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/cdr_adaptive_odbc, CDR/General
>    Affects Versions: 1.8.25.0
>         Environment: OS: Linux CentOS 5.5
> Kernel: 2.6.18-348.16.1.el5PAE
> Hardware: Dell PowerEdge R210 II
>            Reporter: David Hajek
>            Assignee: Matt Jordan
>            Severity: Critical
>         Attachments: backtrace.txt, callfile.txt
>
>
> We are experiencing random asterisk crash (segfaults) on a busy server, which is doing about 50k calls a day. We see asterisk crash every other day.
> This server is running a callcenter and in addition to regular in/out calls this server is processing callfiles (about 3 per second). Some AGI dialplan scripts are processed using FastAGI over tcp sockets.
> We see that all crashes are in ast_cdr_setapp() - we tried both 1.8.24 and 1.8.25.
> For CDR we use cdr_adaptive_odbc with MySQL backend.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira