[asterisk-bugs] [JIRA] (ASTERISK-29860) Segfault in Asterisk 18.8.0

Thu Jan 13 07:36:07 CST 2022

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

Asterisk Team commented on ASTERISK-29860:
------------------------------------------

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

> Segfault in Asterisk 18.8.0
> ---------------------------
>
>                 Key: ASTERISK-29860
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29860
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 18.8.0
>         Environment:  Asterisk 18.8.0 on Ubuntu 20.04
>            Reporter: Xuo Guoto
>              Labels: webrtc
>
> We had observed a segfault in our asterisk today morning. Version in use is Asterisk 18.8.0. This is locally compiled with standard options. Its serving webrtc and couple of SIP trunks. Just before crash saw the following lines in `messages`
> {code:title=asterisk-log|borderStyle=solid}
> [Jan 13 09:56:05] WARNING[808452] http.c: HTTP session count exceeded 100 sessions.
> [Jan 13 09:56:05] WARNING[808453] http.c: HTTP session count exceeded 100 sessions.
> [Jan 13 09:56:06] WARNING[808454] http.c: HTTP session count exceeded 100 sessions.
> [Jan 13 09:56:06] WARNING[808455] http.c: HTTP session count exceeded 100 sessions.
> [Jan 13 09:56:06] ERROR[774409] res_pjsip.c: Error 171060 'Unsupported transport (PJSIP_EUNSUPTRANSPORT)' sending OPTIONS request to endpoint Erx-Dae1s-1100194
> [Jan 13 09:56:06] ERROR[742193] res_pjsip.c: Error 171060 'Unsupported transport (PJSIP_EUNSUPTRANSPORT)' sending OPTIONS request to endpoint Erx-xi6Ve-1100063
> [Jan 13 09:56:06] ERROR[756012] res_pjsip.c: Error 171060 'Unsupported transport (PJSIP_EUNSUPTRANSPORT)' sending OPTIONS request to endpoint Erx-Ahza8-1100153
> [Jan 13 09:56:06] ERROR[807637] res_pjsip.c: Error 70001 'Unknown Error (PJ_EUNKNOWN)' sending OPTIONS request to endpoint Erx-EiD3z-1100028
> [Jan 13 09:56:06] ERROR[807642] res_pjsip.c: Error 70001 'Unknown Error (PJ_EUNKNOWN)' sending OPTIONS request to endpoint Erx-Tith7-1100135
> [Jan 13 09:56:06] ERROR[807647] res_pjsip.c: Error 171060 'Unsupported transport (PJSIP_EUNSUPTRANSPORT)' sending OPTIONS request to endpoint Erx-Dai7w-1100058
> {code}
> the kernel messages are:
> {code:title=syslog|borderStyle=solid}
> Jan 13 09:56:29 erx-q003 kernel: [2658407.847672] show_signal_msg: 20 callbacks suppressed
> Jan 13 09:56:29 erx-q003 kernel: [2658407.847696] asterisk[807966]: segfault at 18 ip 00007f3b65919b30 sp 00007f3b195f4b70 error 4 in libasteriskpj.so.2[7f3b6582c000+fd000]
> Jan 13 09:56:29 erx-q003 kernel: [2658407.847709] Code: 45 40 eb d0 66 0f 1f 44 00 00 f3 0f 1e fa 41 54 4c 8d 67 50 55 48 89 fd 53 48 8b 5f 58 49 39 dc 74 1a 0f 1f 84 00 00 00 00 00 <48> 8b 7b 18 e8 a7 a0 f1 ff 48 8b 5b 08 49 39 dc 75 ee 48 83 7d 40
> {code}
> There is a core dump generated and `bt` is:
> {code:title=bt|borderStyle=solid}
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  grp_lock_acquire (p=0x7f3b30db23a8) at ../src/pj/lock.c:290
> 290             pj_lock_acquire(lck->lock);
> [Current thread is 1 (Thread 0x7f3b195f5700 (LWP 807966))]
> (gdb) bt
> #0  grp_lock_acquire (p=0x7f3b30db23a8) at ../src/pj/lock.c:290
> #1  pj_grp_lock_acquire (grp_lock=0x7f3b30db23a8) at ../src/pj/lock.c:478
> #2  0x00007f3b658a4ec4 in pjsip_tsx_send_msg (tsx=0x7f3b30ab1b38, tdata=tdata at entry=0x7f3b4c075858) at ../src/pjsip/sip_transaction.c:1788
> #3  0x00007f3b23d9a57a in ast_sip_send_stateful_response (rdata=rdata at entry=0x7f3b401bda98, tdata=0x7f3b4c075858, sip_endpoint=sip_endpoint at entry=0x7f3b4c059fc8) at res_pjsip.c:5477
> #4  0x00007f3b2368bf1b in register_aor (aor_name=0x7f3b4c072a60 "Erx-Mee2y-1100130", aor=0x7f3b4c171280, endpoint=0x7f3b4c059fc8, rdata=0x7f3b401bda98) at res_pjsip_registrar.c:1026
> #5  registrar_on_rx_request (rdata=0x7f3b401bda98) at res_pjsip_registrar.c:1221
> #6  0x00007f3b6588a2b3 in pjsip_endpt_process_rx_data (endpt=0x55be0147a968, rdata=rdata at entry=0x7f3b401bda98, p=p at entry=0x7f3b23de1200 <param>, p_handled=p_handled at entry=0x7f3b195f4ce4) at ../src/pjsip/sip_endpoint.c:930
> #7  0x00007f3b23db1093 in distribute (data=0x7f3b401bda98) at res_pjsip/pjsip_distributor.c:955
> #8  0x000055be0006e3e5 in ast_taskprocessor_execute (tps=tps at entry=0x55be01915730) at taskprocessor.c:1237
> #9  0x000055be000750f8 in execute_tasks (data=0x55be01915730) at threadpool.c:1356
> #10 0x000055be0006e3e5 in ast_taskprocessor_execute (tps=0x55be01477530) at taskprocessor.c:1237
> #11 0x000055be000759dc in threadpool_execute (pool=0x55be01477860) at threadpool.c:367
> #12 worker_active (worker=0x7f3b5402f2c0) at threadpool.c:1137
> #13 worker_start (arg=arg at entry=0x7f3b5402f2c0) at threadpool.c:1056
> #14 0x000055be0007d918 in dummy_start (data=<optimized out>) at utils.c:1428
> #15 0x00007f3b650de609 in start_thread (arg=<optimized out>) at pthread_create.c:477
> #16 0x00007f3b64e62293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
> (gdb) 
> {code}
> If some additional data is needed to triage this issue I will be happy to provide. 

--
This message was sent by Atlassian JIRA
(v6.2#6252)