[asterisk-bugs] [JIRA] (ASTERISK-25454) Crashing possibly related to cdr_manager
Zane Conkle (JIRA)
noreply at issues.asterisk.org
Thu Oct 8 10:43:32 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zane Conkle updated ASTERISK-25454:
-----------------------------------
Description:
This is the second time asterisk has crashed within 12 hours of enabling cdr_manager. What is weird is the coredump references a segfault at chan_pjsip.c:1750 and I do not see any threads accessing cdr. It makes me wonder if there is any relation to cdr_manager at all.
We made a very simple change and added linkedid to cdr_manager so I am attaching that change along with the backtrace.
was:
This is the second time asterisk has crashed within 12 hours of enabling cdr_manager. What is weird is the coredump references a segfault at chan_pjsip.c:1750 and I do not see any threads accessing cdr. It makes me wonder if there is any relation to cdr_manager at all.
We made a very simple change and added linked_id to cdr_manager so I am attaching that change along with the backtrace.
> Crashing possibly related to cdr_manager
> ----------------------------------------
>
> Key: ASTERISK-25454
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25454
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Affects Versions: 13.6.0
> Reporter: Zane Conkle
> Attachments: backtrace-2015-10-08.txt, cdr_manager-diff.txt
>
>
> This is the second time asterisk has crashed within 12 hours of enabling cdr_manager. What is weird is the coredump references a segfault at chan_pjsip.c:1750 and I do not see any threads accessing cdr. It makes me wonder if there is any relation to cdr_manager at all.
> We made a very simple change and added linkedid to cdr_manager so I am attaching that change along with the backtrace.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list