[Home]

Summary:ASTERISK-27466: Asterisk 14.7.3 Crash SIP - chan_sip.c: FRACK!, Failed assertion bad magic number 0x0
Reporter:Renato Monfort Pires (monfort)Labels:
Date Opened:2017-12-07 10:46:23.000-0600Date Closed:2018-07-11 04:36:26
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General Channels/chan_sip/WebSocket
Versions:14.7.3 Frequency of
Occurrence
Related
Issues:
Environment:Debian Jessie Attachments:( 0) core.55PBX-SIP1-2017-12-07T13-44-09-0200-brief.txt
( 1) core.55PBX-SIP1-2017-12-07T13-44-09-0200-full.txt
( 2) core.55PBX-SIP1-2017-12-07T13-44-09-0200-locks.txt
( 3) core.55PBX-SIP1-2017-12-07T13-44-09-0200-thread1.txt
( 4) core.55PBX-SIP1-2017-12-08T22-00-05-0200-brief.txt
( 5) core.55PBX-SIP1-2017-12-08T22-00-05-0200-full.txt
( 6) core.55PBX-SIP1-2017-12-08T22-00-05-0200-locks.txt
( 7) core.55PBX-SIP1-2017-12-08T22-00-05-0200-thread1.txt
( 8) core.55PBX-SIP1-2017-12-11T13-39-09-0200-brief.txt
( 9) core.55PBX-SIP1-2017-12-11T13-39-09-0200-full.txt
(10) core.55PBX-SIP1-2017-12-11T13-39-09-0200-locks.txt
(11) core.55PBX-SIP1-2017-12-11T13-39-09-0200-thread1.txt
(12) core.55PBX-SIP1-2017-12-12T09-54-52-0200-brief.txt
(13) core.55PBX-SIP1-2017-12-12T09-54-52-0200-full.txt
(14) core.55PBX-SIP1-2017-12-12T09-54-52-0200-locks.txt
(15) core.55PBX-SIP1-2017-12-12T09-54-52-0200-thread1.txt
(16) core.55PBX-SIP1-2017-12-12T11-35-27-0200-brief.txt
(17) core.55PBX-SIP1-2017-12-12T11-35-27-0200-full.txt
(18) core.55PBX-SIP1-2017-12-12T11-35-27-0200-locks.txt
(19) core.55PBX-SIP1-2017-12-12T11-35-27-0200-thread1.txt
(20) core.55PBX-SIP1-2017-12-12T12-42-55-0200-brief.txt
(21) core.55PBX-SIP1-2017-12-12T12-42-55-0200-full.txt
(22) core.55PBX-SIP1-2017-12-12T12-42-55-0200-locks.txt
(23) core.55PBX-SIP1-2017-12-12T12-42-55-0200-thread1.txt
(24) sip.conf
Description:Asterisk is crashing every day, almost at same hour and with same indication of chan_sip issue.

chan_sip.c: FRACK!, Failed assertion bad magic number 0x0
Comments:By: Asterisk Team (asteriskteam) 2017-12-07 10:46:23.980-0600

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: Renato Monfort Pires (monfort) 2017-12-07 10:49:15.441-0600

Full backtrace thread's locks.
By: Renato Monfort Pires (monfort) 2017-12-12 09:27:59.511-0600

Please Help! Today my Asterisk crash's 3 times until now. Please Help!
log:
[Dec 12 12:42:54] VERBOSE[5481] logger.c: Got 23 backtrace records
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #0: [0x61858c] main/utils.c:2475 __ast_assert_failed() (0x6184ff+8D)
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #1: [0x45e7c5] main/astobj2.c:192 log_bad_ao2()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #2: [0x45f037] main/astobj2.c:466 __ao2_ref() (0x45efae+89)
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #3: [0x4611aa] main/astobj2_container.c:372 internal_ao2_traverse()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #4: [0x4613f0] main/astobj2_container.c:423 __ao2_callback_data() (0x4613a3+4D)
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #5: [0x7fd0eea29a4b] channels/chan_sip.c:5729 sip_find_peer_full()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #6: [0x7fd0eea29cea] channels/chan_sip.c:5786 sip_find_peer()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #7: [0x7fd0eea64acc] channels/chan_sip.c:17795 register_verify()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #8: [0x7fd0eea9ddf2] channels/chan_sip.c:28652 handle_request_register()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #9: [0x7fd0eea9f555] channels/chan_sip.c:28960 handle_incoming()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #10: [0x7fd0eea9fec0] channels/chan_sip.c:29128 handle_request_do()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #11: [0x7fd0eea1edcf] channels/chan_sip.c:2666 sip_websocket_callback()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #12: [0x7fd1b46877e4] res/res_http_websocket.c:923 __ast_websocket_uri_cb() (0x7fd1b46868ce+F16)
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #13: [0x53919f] main/http.c:1497 handle_uri()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #14: [0x539ffc] main/http.c:1921 httpd_process_request()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #15: [0x53a3c4] main/http.c:1998 httpd_helper_thread()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #16: [0x601561] main/tcptls.c:791 handle_tcptls_connection()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #17: [0x615562] main/utils.c:1233 dummy_start()
[Dec 12 12:42:54] ERROR[5481] chan_sip.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x42ec198 (0)
[Dec 12 12:42:54] VERBOSE[5481] logger.c: Got 19 backtrace records
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #0: [0x61858c] main/utils.c:2475 __ast_assert_failed() (0x6184ff+8D)
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #1: [0x45e7c5] main/astobj2.c:192 log_bad_ao2()
[Dec 12 12:42:54] VERBOSE[5481] logger.c: #2: [0x45e828] main/astobj2.c:196 __ao2_lock() (0x45e7c7+61)
By: Joshua C. Colp (jcolp) 2017-12-22 06:37:20.606-0600

This appears to be an issue in chan_sip. This is community supported but in order to help an individual if they choose to work on it I also suggest providing information about the configuration - such as if you are using realtime or not, and what your configuration looks like.
By: Renato Monfort Pires (monfort) 2017-12-22 07:05:33.304-0600

We are not using realtime and sip.conf has add as an attachment.
By: Joshua C. Colp (jcolp) 2017-12-22 07:08:15.133-0600

I've accepted this as an issue but as I stated this is community supported so there is no timeframe on when it will get looked into.
By: Corey Farrell (coreyfarrell) 2017-12-22 14:20:51.543-0600

The "bad magic number 0x0" is produced by astobj2 and likely indicates that chan_sip is using an object after it was freed.  Please follow the instructions on \[1\], reproduce the error and post the resulting reference log.  When you do so please do not delete the raw 'refs' log, for this issue we may need you to extract additional information from it once we review the processed refs.txt.  Unfortunately the raw 'refs' log will likely be too large to post the complete file here.

\[1\] https://wiki.asterisk.org/wiki/display/AST/Reference+Count+Debugging
By: Joshua C. Colp (jcolp) 2018-07-11 04:36:26.978-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines