[Home]

Summary:ASTERISK-28408: Asterisk crashes intermittently if use sipML5 as the SIP client, regardless of the total number of peers in use.
Reporter:Maksim Suminov (smvtv)Labels:
Date Opened:2019-05-08 10:28:05Date Closed:
Priority:CriticalRegression?
Status:Open/NewComponents:Channels/chan_sip/WebSocket Resources/res_http_websocket
Versions:13.18.0 16.3.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:VMWare VM, Ubuntu 14.04.6 LTS GNU/Linux 3.13.0-169-generic x86_64Attachments:( 0) core.asterisk-brief.txt
( 1) core.asterisk-full.txt
( 2) core.asterisk-locks.txt
( 3) core.asterisk-thread1.txt
( 4) sip.conf.txt
Description:5-10 minutes before Asterisk crashes, errors appear in the CLI:
[May  6 20:20:43] ERROR[111246] chan_sip.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x381bf90 (0)
[May  6 20:20:43] ERROR[111246] : Got 11 backtrace records
# 0: /usr/sbin/asterisk(__ao2_lock+0x8b) [0x45d1ab]
# 1: /usr/lib/asterisk/modules/chan_sip.so(+0x9fbf7) [0x7f0900786bf7]
# 2: /usr/lib/asterisk/modules/chan_sip.so(+0xa25c1) [0x7f09007895c1]
# 3: /usr/lib/asterisk/modules/chan_sip.so(+0xa4cce) [0x7f090078bcce]
# 4: /usr/lib/asterisk/modules/chan_sip.so(+0xa6b25) [0x7f090078db25]
# 5: /usr/lib/asterisk/modules/res_http_websocket.so(__ast_websocket_uri_cb+0xdb5) [0x7f09035d3265]
# 6: /usr/sbin/asterisk() [0x5e812e]
# 7: /usr/sbin/asterisk() [0x5e836c]
# 8: /usr/sbin/asterisk() [0x5a1519]
# 9: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8184) [0x7f096127e184]
#10: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f096085a03d]
Comments:By: Asterisk Team (asteriskteam) 2019-05-08 10:28:06.649-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].

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.
By: George Joseph (gjoseph) 2019-05-08 10:31:22.034-0500

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Maksim Suminov (smvtv) 2019-05-08 10:33:08.977-0500

Register several sipML-based SIP clients and wait several hours while they are active.
By: George Joseph (gjoseph) 2019-05-08 12:03:50.852-0500

Which version of asterisk are the backtraces against?  Do a "core show version".  If not against 13.26 or 16.3, please reproduce the problem under one of those versions.

thanks.


By: Maksim Suminov (smvtv) 2019-05-08 13:20:04.531-0500

Asterisk 16.3.0 is currently installed. Backtrace was generated on this version
By: George Joseph (gjoseph) 2019-05-09 08:30:24.532-0500

Based on the backtrace, it looks like there was some sort of memory corruption while trying to copy a contact URI during a REGISTER.

Unfortunately...

The chan_sip channel driver is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available.

Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1]

If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way.

[1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
[2]: http://www.asterisk.org/community/discuss
[3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties