[Home]

Summary:ASTERISK-30183: SegFault / TCP Stack
Reporter:Tim (TimRSA)Labels:
Date Opened:2022-08-17 05:26:24Date Closed:2022-08-17 05:32:23
Priority:CriticalRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:18.10.0 Frequency of
Occurrence		Frequent
Related
Issues:
duplicatesASTERISK-28689 res_pjsip: Crash when locking group lock when sending stateful response
Environment:VM, 8 cores, 8GB ramAttachments:
Description:We seem to be getting seg faults on a few of our asterisk 18 servers, when reading the backtraces I noticed they appear to all be from ast_sip_send_stateful_response? please see below a snip from the backtrace:

Core was generated by `/usr/sbin/asterisk -f -vvvg -c'.
Program terminated with signal 11, Segmentation fault.
#0  pj_lock_acquire (lock=0x6764697262206568) at ../src/pj/lock.c:180
180    return (*lock->acquire)(lock->lock_object);
#0  pj_lock_acquire (lock=0x6764697262206568) at ../src/pj/lock.c:180
       lock = 0x6764697262206568
#1  0x00007f8f849ae4c1 in grp_lock_acquire (p=0x7f8eb8086848) at ../src/pj/lock.c:290
       glock = 0x7f8eb8086848
       lck = 0x218cf68
#2  pj_grp_lock_acquire (grp_lock=0x7f8eb8086848) at ../src/pj/lock.c:478
No locals.
#3  0x00007f8f8493cf3c in pjsip_tsx_send_msg (tsx=0x7f8f48ae9388, tdata=tdata@entry=0x7f8eb81ad5f8) at ../src/pjsip/sip_transaction.c:1788
       event = {prev = 0x7f8f48ae9388, next = 0x1, type = PJSIP_EVENT_TX_MSG, body = {timer = {entry = 0x7f8eb81ad5f8}, tsx_state = {src = {rdata = 0x7f8eb81ad5f8, tdata = 0x7f8eb81ad5f8, timer = 0x7f8eb81ad5f8, status = -1206200840, data = 0x7f8eb81ad5f8}, tsx = 0x7f8f404c9e90, prev_state = -1206200840, type = 32654}, tx_msg = {tdata = 0x7f8eb81ad5f8}, tx_error = {tdata = 0x7f8eb81ad5f8, tsx = 0x7f8f404c9e90}, rx_msg = {rdata = 0x7f8eb81ad5f8}, user = {user1 = 0x7f8eb81ad5f8, user2 = 0x7f8f404c9e90, user3 = 0x7f8eb81ad5f8, user4 = 0x7f8e70c81e88}}}
       status = <optimized out>
#4  0x00007f8f339a1b5e in ast_sip_send_stateful_response (rdata=rdata@entry=0x7f8e70c81e88, tdata=0x7f8eb81ad5f8, sip_endpoint=sip_endpoint@entry=0x7f8eb804aa88) at res_pjsip.c:5505
       tsx = 0x7f8f48ae9388
       __PRETTY_FUNCTION__ = "ast_sip_send_stateful_response"
#5  0x00007f8f26e72a1e in register_aor (aor_name=0x7f8eb8040d50 "extension-Client", aor=0x7f8eb814fe00, endpoint=0x7f8eb804aa88, rdata=0x7f8e70c81e88) at res_pjsip_registrar.c:1023
       response = {tdata = 0x7f8eb81ad5f8, code = 500}
       contacts = 0x7f8eb804e508
#6  registrar_on_rx_request (rdata=0x7f8e70c81e88) at res_pjsip_registrar.c:1218
       endpoint = 0x7f8eb804aa88
       aor = 0x7f8eb814fe00
       aor_name = 0x7f8eb8040d50 "extension-Client"
       __FUNCTION__ = "registrar_on_rx_request"
       __PRETTY_FUNCTION__ = "registrar_on_rx_request"


I can send you multiple backtraces but I cant attach them here.

Comments:By: Asterisk Team (asteriskteam) 2022-08-17 05:26:29.520-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].