Summary: | ASTERISK-26073: chan_sip: Crash when cleaning up pruned peers | ||||
Reporter: | Anton Satskiy (satskiy.a) | Labels: | asterisk sip webrtc | ||
Date Opened: | 2016-05-30 10:20:05 | Date Closed: | |||
Priority: | Major | Regression? | |||
Status: | Open/New | Components: | Channels/chan_sip/General | ||
Versions: | 13.9.1 | Frequency of Occurrence | Frequent | ||
Related Issues: |
| ||||
Environment: | CentOS release 6.8 (Final) | Attachments: | ( 0) 2016-05-30_18_22_05-sip.asterisk.if.ua_MidnightBlue.zoc_[evaluation_mode].png ( 1) backtrace.txt ( 2) backtracenew.txt ( 3) debug_log_1000last ( 4) extensions_incoming.ael ( 5) extensions_macros.ael ( 6) extensions_outgoing_expertit.ael ( 7) extensions_outgoing_office.ael ( 8) extensions_route.ael ( 9) extensions.ael (10) hints.ael (11) sip_db.conf (12) sip_peers.conf (13) sip_users.conf (14) sip.conf | ||
Description: | asterisk suddenly crash | ||||
Comments: | By: Asterisk Team (asteriskteam) 2016-05-30 10:20:06.492-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]. By: Anton Satskiy (satskiy.a) 2016-05-30 10:22:14.505-0500 backtrace By: Anton Satskiy (satskiy.a) 2016-05-30 10:23:46.587-0500 Compiler Flags By: Anton Satskiy (satskiy.a) 2016-05-30 10:31:18.750-0500 from 1 to 3 times a day asterisk suddenly crashes backtrace and compiled flags are in the attach (there was a problem with Asterisk from official repository and persists with Asterisk from source) Please help to solve issue By: Joshua C. Colp (jcolp) 2016-05-30 10:52:59.664-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Anton Satskiy (satskiy.a) 2016-06-01 07:58:58.026-0500 i cant attach debug file it is 1.3GB (only 10MB allowed) any other posibbility? meanwhile i will attach new backtraceNEW --- let me mention that there is no steps sustem is working,people are calling and suddenly it craches with Segmentation fault we are using asterisk with sip phones and webrtc phones for calls update me if U need sip.conf or extensions.ael Regards By: Anton Satskiy (satskiy.a) 2016-06-01 08:03:54.692-0500 new backtrace By: Rusty Newton (rnewton) 2016-06-14 09:22:28.639-0500 Yes, please provide the configs for the system if possible. In addition please provide the last 1000 lines of debug before the crash. By: Anton Satskiy (satskiy.a) 2016-06-15 07:28:19.560-0500 configs By: Anton Satskiy (satskiy.a) 2016-06-15 07:29:12.701-0500 news crash with CLI logs maybe it will help [Jun 15 13:59:10] VERBOSE[26885] config.c: Parsing '/etc/asterisk/sip_notify_additional.conf': Found [Jun 15 13:59:10] WARNING[26885] chan_sip.c: Unable to cancel schedule ID 877094969. This is probably a bug (chan_sip.c: peer_sched_cleanup, line 3151). [Jun 15 13:59:10] ERROR[26885] astobj2.c: bad magic number 0x755f706d for object 0x3bc7428 [Jun 15 13:59:10] WARNING[26885] chan_sip.c: Unable to cancel schedule ID 1851748709. This is probably a bug (chan_sip.c: peer_sched_cleanup, line 3155). [Jun 15 13:59:10] ERROR[26885] astobj2.c: bad magic number 0x755f706d for object 0x3bc7428 [Jun 15 13:59:10] WARNING[26885] chan_sip.c: Unable to cancel schedule ID 1953718586. This is probably a bug (chan_sip.c: peer_sched_cleanup, line 3159). [Jun 15 13:59:10] ERROR[26885] astobj2.c: bad magic number 0x755f706d for object 0x3bc7428 By: Anton Satskiy (satskiy.a) 2016-06-15 07:32:45.953-0500 last 1000 lines of debug By: Anton Satskiy (satskiy.a) 2016-06-16 05:29:21.791-0500 asterisk kernel stops FYI: Jun 16 12:59:29 asterisk kernel: asterisk[28736]: segfault at ffffffff047ed9f0 ip 00000000005d511b sp 00007fa5d91cb9d0 error 4 in asterisk[400000+349000] By: Anton Satskiy (satskiy.a) 2016-06-24 08:51:03.343-0500 almost month with no resolution --- Severity Updated By: Joshua C. Colp (jcolp) 2016-06-24 08:52:03.271-0500 I can understand how this may be critical to you, but I've put it back to where I feel it fits as a project which is major. By: Anton Satskiy (satskiy.a) 2016-07-08 03:14:21.229-0500 what else can i do to speed up the solution ? By: Joshua C. Colp (jcolp) 2016-07-08 05:16:06.469-0500 You can try to find a consultant who will fix the issue, but they will likely charge money. The asterisk-biz list can be used for this. You can also post a bounty[1] but the minimum is $500. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties |