[Home]

Summary:ASTERISK-27057: Seg Fault in ast_sorcery_object_get_id at sorcery.c
Reporter:Ryan Smith (ryan_k_smith)Labels:
Date Opened:2017-06-14 09:50:26Date Closed:2017-06-27 08:02:39
Priority:CriticalRegression?
Status:Closed/CompleteComponents:Core/Sorcery
Versions:13.15.0 Frequency of
Occurrence		Occasional
Related
Issues:
Environment:Centos 6.8 FinalAttachments:( 0) backtrace1.txt
Description:Segmentation fault leading to core dump.
{quote}
[2017-06-14 14:41:35] DEBUG[39132] res_pjsip_pubsub.c: sub_tree 0x7f77d035eb20 sub_tree state TerminatePending
[2017-06-14 14:41:35] DEBUG[39132] res_pjsip_pubsub.c: sub_tree 0x7f77d035eb20 sub_tree state TerminatePending
[2017-06-14 14:41:35] DEBUG[39132] res_pjsip_pubsub.c: evsub 0x7f77d0197e38 state TERMINATED event USER sub_tree 0x7f77d035eb20 sub_tree state TerminateInProgress
[2017-06-14 14:41:35] DEBUG[39132] res_pjsip_pubsub.c: Removing subscription 'sip_name1_here->101' from list of subscriptions
[2017-06-14 14:41:35] DEBUG[39132] res_pjsip_pubsub.c: Removing subscription 0x7f77d009f5d0 sip_name1_here->101' reference to subscription tree 0x7f77d035eb20
[2017-06-14 14:41:35] DEBUG[39132] res_pjsip_pubsub.c: Destroying subscription tree 0x7f77d035eb20 sip_name1_here->101'
[2017-06-14 14:41:58] Asterisk 13.15.0 built by root @ sip02 on a x86_64 running Linux on 2017-05-30 11:00:04 UTC
{quote}
{quote}
#0  0x00000000005cf41a in ast_sorcery_object_get_id (object=0x7f77d815e258) at sorcery.c:2257
2257            return details->object->id;
#0  0x00000000005cf41a in ast_sorcery_object_get_id (object=0x7f77d815e258) at sorcery.c:2257
       details = 0x7f77d815e258
#1  0x00007f77e8ce2db5 in destroy_subscription (sub=0x7f77d009f5d0) at res_pjsip_pubsub.c:1110
       __PRETTY_FUNCTION__ = "destroy_subscription"
#2  0x00007f77e8ce4aaa in subscription_tree_destructor (obj=0x7f77d035eb20) at res_pjsip_pubsub.c:1270
       sub_tree = 0x7f77d035eb20
       __PRETTY_FUNCTION__ = "subscription_tree_destructor"

{quote}
Comments:By: Asterisk Team (asteriskteam) 2017-06-14 09:50:27.137-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Ryan Smith (ryan_k_smith) 2017-06-14 09:54:28.498-0500

backtrace.txt
By: George Joseph (gjoseph) 2017-06-14 11:00:57.795-0500

Yep, we're trying to debug print the id of the endpoint after we're released the endpoint.

By: George Joseph (gjoseph) 2017-06-15 07:50:53.599-0500

There's a patch available to test if you'd like to.
Click the Gerrit Reviews tab and grab the one for the branch you're working on.

By: Ryan Smith (ryan_k_smith) 2017-06-15 07:56:39.927-0500

Hi - I'd already grabbed it this morning and have applied it to the server in question, I will be able to reboot the server once traffic dies down.

Many Thanks.
By: Ryan Smith (ryan_k_smith) 2017-06-27 08:00:13.087-0500

Scaled to 1200 Endpoints - originally saw issues around 300-400 every 48 hours.

System uptime: 1 week, 7 hours, 5 minutes, 51 seconds

No crashes so far, all looks good.

By: Joshua C. Colp (jcolp) 2017-06-27 08:02:39.347-0500

Great. I'm closing this issue out as fixed.