Summary: | ASTERISK-23623: chan_sip deadlocks with TCP connections | ||
Reporter: | Artem Makhutov (artem) | Labels: | |
Date Opened: | 2014-04-12 03:37:58 | Date Closed: | 2014-04-29 15:57:20 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Channels/chan_sip/TCP-TLS |
Versions: | 11.8.1 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Gentoo, Asterisk 11.8.1 | Attachments: | ( 0) core_show_locks.txt |
Description: | My asterisk box has 3 x Cisco 9971 and 1 x Grandstream GXV 3000 Phone all connected via TCP.
The deadlock happands almost once a day and requires a restart of asterisk. There is always a lock in do_monitor and usually several locks on handle_tcptls_connection. apollo*CLI> core show locks Edit - removed pasted output and attached as {{.txt}} file. | ||
Comments: | By: Richard Mudgett (rmudgett) 2014-04-14 11:02:39.821-0500 Please *attach* debug output files as {{.txt}} files to issues rather than pasting them in the comments or issue description. By: Rusty Newton (rnewton) 2014-04-14 15:47:14.489-0500 Artem, can you recompile Asterisk with the BETTER_BACKTRACES compiler flag in addition to DEBUG_THREADS and then get the "core show locks" output again? You can see an example of how it is helpful, [here on the wiki|https://wiki.asterisk.org/wiki/display/AST/CLI+commands+useful+for+debugging#CLIcommandsusefulfordebugging-coreshowlocks]. By: Matt Jordan (mjordan) 2014-04-14 16:11:17.001-0500 This looks suspiciously like the {{DEBUG_THREADS}} mechanism causing problems. Does the issue occur when {{DEBUG_THREADS}} is not enabled? By: Matt Jordan (mjordan) 2014-04-29 15:57:29.115-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 |