|Summary:||ASTERISK-18248: SIP crash but Asterisk stay UP|
|Reporter:||Tch Logos (tchlogos)||Labels:|
|Date Opened:||2011-08-09 04:50:52||Date Closed:||2011-09-14 08:54:04|
|Versions:||1.8.3 184.108.40.206||Frequency of|
|Environment:||Linux 2.6.32-33-generic-pae #70-Ubuntu SMP Thu Jul 7 22:51:12 UTC 2011 i686 GNU/Linux||Attachments:|
|Description:||During a call between two devices the RTP session crash, then all the devices stop registering. This happening occur once a week, or twice randomly.|
|Comments:||By: David Woolley (davidw) 2011-08-11 06:19:03.474-0500|
I don't believe there is enough information for anyone to progress this. You probably need to provide the SIP protocol trace. As there are hints that this may involve a deadlock, you also need to follow the procedures for reporting deadlocks.
Also severities represent the severity to the whole Asterisk community, not that to the reporter, Blocker is reserved for the developers.
Edited - technology was given, but only in the summary.
By: Paul Belanger (pabelanger) 2011-08-11 11:27:00.730-0500
Thank you for your bug report. In order to move your issue forward, we require a backtrace from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:
After enabling, reproduce the crash, and then execute the backtrace instructions. When complete, attach that file to this issue report.
By: Richard Mudgett (rmudgett) 2011-08-11 12:02:09.962-0500
Debugging deadlocks: Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags section of menuselect. Recompile and install Asterisk (i.e. make install). This will then give you the console command "core show locks." When the symptoms of the deadlock present themselves again, please provide output of the deadlock via:
# asterisk -rx "core show locks" | tee /tmp/core-show-locks.txt
# gdb -se "asterisk" <pid of asterisk> | tee /tmp/backtrace.txt
gdb> bt full
gdb> thread apply all bt
Then attach the core-show-locks.txt and backtrace.txt files to this issue. Thanks!
This issue is not a crash since Asterisk stays "UP".
A crash means a segfault happened.
By: Leif Madsen (lmadsen) 2011-08-11 13:22:56.312-0500
Assigned to developer to provide the requested (required) feedback.
By: Leif Madsen (lmadsen) 2011-09-14 08:53:55.754-0500
Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines