[asterisk-bugs] [JIRA] (ASTERISK-29101) Asterisk Dead lock on SIP and RTP

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Sep 29 00:00:36 CDT 2020


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

Asterisk Team commented on ASTERISK-29101:
------------------------------------------

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

> Asterisk Dead lock on SIP and RTP
> ---------------------------------
>
>                 Key: ASTERISK-29101
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29101
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/format_mp3, Addons/res_config_mysql
>    Affects Versions: 16.1.1
>         Environment: CentOS Linux release 7.6.1810 (Core) 
>            Reporter: Vijo Jose
>            Severity: Critical
>
> Hi all.
> I have an asterisk server installed with version 16.1.1 on centos 7 Os.
> I have noticed that sometimes my all SIP peers going unreachable including the looping SIP trunk(127.0.0.1) which I have. I was checking for the locks in asterisk using asterisk -rx “core show locks” and below is my result.
> ===
> === Thread ID: 0x7f1ea0930700 LWP:30389 (do_monitor           started at [29979] chan_sip.c restart_monitor())
> === ---> Lock #0 (chan_sip.c): MUTEX 29340 handle_request_do &netlock 0x7f1f01b2f680 (1)
> 	asterisk(__ast_pthread_mutex_lock+0x85) [0x501885]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0xa33d6) [0x7f1f018ff3d6]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0xa4fcf) [0x7f1f01900fcf]
> 	asterisk(ast_io_wait+0x7a) [0x4f517a]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x8086c) [0x7f1f018dc86c]
> 	asterisk() [0x5a0412]
> 	/usr/lib64/libpthread.so.0(+0x7dd5) [0x7f1f2690cdd5]
> 	/usr/lib64/libc.so.6(clone+0x6d) [0x7f1f25caf02d]
> === ---> Lock #1 (chan_sip.c): MUTEX 9370 sip_pvt_lock_full pvt 0x7f1e000661a0 (1)
> 	asterisk(__ast_pthread_mutex_lock+0x85) [0x501885]
> 	asterisk(__ao2_lock+0x1c5) [0x45d7f5]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x14bd5) [0x7f1f01870bd5]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0xa3405) [0x7f1f018ff405]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0xa4fcf) [0x7f1f01900fcf]
> 	asterisk(ast_io_wait+0x7a) [0x4f517a]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x8086c) [0x7f1f018dc86c]
> 	asterisk() [0x5a0412]
> 	/usr/lib64/libpthread.so.0(+0x7dd5) [0x7f1f2690cdd5]
> 	/usr/lib64/libc.so.6(clone+0x6d) [0x7f1f25caf02d]
> === ---> Lock #2 (rtp_engine.c): MUTEX 692 ast_rtp_instance_set_prop instance 0x7f1e000347c0 (1)
> 	asterisk(__ast_pthread_mutex_lock+0x85) [0x501885]
> 	asterisk(__ao2_lock+0x1c5) [0x45d7f5]
> 	asterisk(ast_rtp_instance_set_prop+0x29) [0x53ed79]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x27ee4) [0x7f1f01883ee4]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x95f88) [0x7f1f018f1f88]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x9771c) [0x7f1f018f371c]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x9a820) [0x7f1f018f6820]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0xa0bcd) [0x7f1f018fcbcd]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0xa351e) [0x7f1f018ff51e]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0xa4fcf) [0x7f1f01900fcf]
> 	asterisk(ast_io_wait+0x7a) [0x4f517a]
> 	/usr/lib64/asterisk/modules/chan_sip.so(+0x8086c) [0x7f1f018dc86c]
> 	asterisk() [0x5a0412]
> 	/usr/lib64/libpthread.so.0(+0x7dd5) [0x7f1f2690cdd5]



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



More information about the asterisk-bugs mailing list