[asterisk-bugs] [JIRA] (ASTERISK-24471) Crash - assert_fail in libc in pjmedia_sdp_neg_negotiate from /usr/local/lib/libpjmedia.so.2
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Wed Nov 5 17:18:29 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-24471:
------------------------------------
Assignee: yaron nahum
Status: Waiting for Feedback (was: Triage)
Yaron - I want to verify - are you able to reproduce this issue?
If not, but you get the crash frequently enough that you expect it to happen again , can you go ahead and recompile pjproject with debug symbols so that we will have that information for your next backtrace?
To investigate further we need you to provide another backtrace, but with debug symbols for pjproject.
When recompiling pjproject, you'll need to specify the CFLAGS param -g in addition to any other configure options or parameters.
{noformat}
./configure CFLAGS='-g'
{noformat}
Be sure to press Enter Feedback or Send Back when replying.
> Crash - assert_fail in libc in pjmedia_sdp_neg_negotiate from /usr/local/lib/libpjmedia.so.2
> --------------------------------------------------------------------------------------------
>
> Key: ASTERISK-24471
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24471
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: pjproject/pjsip, Resources/res_pjsip
> Affects Versions: 12.2.0, 12.6.1
> Environment: centos 6
> Reporter: yaron nahum
> Assignee: yaron nahum
> Severity: Critical
> Attachments: backtrace.txt, yaron.debug.1
>
>
> We have had several crashes recent days on servers running 12.2.0rc1. We upgraded one of the servers to 12.6.1 and it crashed also. The crashes occur every couple of days per server.
> Our service uses AGI's for external logic. It also uses spandsp for fax receiving and sending.
> *** Yaron -
> Going over the debug messages I can see that the last call before the reboot was an incoming that was canceled in the same second of the initial INVITE. In between I can see that we activated a certain AGI, and then after we got the cancel we jumped to h extension there we activated another AGI.
> We are trying to simulated this scenario with SIPP and see if the reboot occurs.
> One more thing I forgot to mention is that we have a lot of zombie processes running all the time related to Asterisk. It might be related to the reboot.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list