[Home]

Summary:ASTERISK-18100: chan_sip not responding sometimes until asterisk restart
Reporter:Ivan Anishchuk (i_anishchuk)Labels:
Date Opened:2011-07-07 21:49:01Date Closed:2011-09-14 08:38:23
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General Channels/chan_sip/Registration
Versions:1.8.4 Frequency of
Occurrence
Frequent
Related
Issues:
Environment:Debian GNU/Linux 6.0 with 2.6.32-5 kernel on amd64Attachments:( 0) messages
Description:Sometimes (we could not find a trend) asterisk just stops responding to sip registration requests. At the same time it responds to console commands (e.g. sip show channels outputs channels which was active at the freeze moment) excepts "sip reload", which does not work.

This happens two or three times a day, it isn't good for our call center. Which information should we provide? (full log with enabled sip debug, verbose 4, and debug 4 have size about 800 MiB)
Comments:By: Ivan Anishchuk (i_anishchuk) 2011-07-07 22:06:56.197-0500

Messages log. About [Jul  8 10:49:05] chan_sip freezed out and asterisk has been restarted.

By: Leif Madsen (lmadsen) 2011-07-11 14:51:32.749-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
gdb> bt full
gdb> thread apply all bt

Then attach the core-show-locks.txt and backtrace.txt files to this issue. Thanks!

Looks like a deadlock, in which case you'll need to provide a backtrace from the running process along with 'core show locks' data.

By: Leif Madsen (lmadsen) 2011-08-09 09:05:46.735-0500

Assigned to reporter after requesting feedback.

By: Leif Madsen (lmadsen) 2011-09-14 08:38:18.327-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