| Summary: | ASTERISK-18202: deadlock in sip | ||
| Reporter: | caspy (caspy) | Labels: | |
| Date Opened: | 2011-07-28 09:48:17 | Date Closed: | 2011-09-22 07:16:18 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | . I did not set the category correctly. |
| Versions: | 1.8.5.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | debian, last stable updated, dahdi version: 2.4.1.2 | Attachments: | ( 0) gdb.201107281827 ( 1) locks.201107281827 |
| Description: | asterisk get locked 1-2 times a day. timing module - res_timing_dahdi, i have dahdi card | ||
| Comments: | By: caspy (caspy) 2011-07-28 09:53:09.532-0500 core show locks, gdb's bt By: Ernie Dunbar (ernied) 2011-08-03 10:50:53.744-0500 You might try a hardware reset on this server. I've been struggling with this for weeks and unloaded res_timing_timerfd.so as recommended, but kept getting multiple SIP deadlocks every day. After rebooting the machine, asterisk has been running without a deadlock for 5 days now (although Asterisk restarts every night). Which leads me to believe that there may also be some kind of memory leak when this happens, that keeps the problem coming back. By: Leif Madsen (lmadsen) 2011-09-22 07:16:18.547-0500 The backtrace shows the use of res_timing_pthread (which will be loaded prior to res_timing_dahdi). Please disable res_timing_pthread. I'm closing this issue as a known issue with res_timing_pthread. | ||