| Summary: | ASTERISK-23926: Asterisk locks after 'restart now' command | ||||
| Reporter: | c0rnoTa (c0rnota) | Labels: | |||
| Date Opened: | 2014-06-25 00:53:27 | Date Closed: | 2014-06-25 11:16:22 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Core/General | ||
| Versions: | 1.8.28.2 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Gentoo 3.2.12-gentoo x86_64 on hardware server Perl scripts with AMI connection and *.call file creation | Attachments: | ( 0) backtrace-threads.txt ( 1) show_locks | ||
| Description: | I have an autodialing system based on Asterisk 1.8.28.2.
Perl scripts generate call files for outgoing calls, internal buddies are connected to queue as Agents. After a while time of working, when I send 'core restart now' command, asterisk locks. It could execute commands but does not procces calls because waiting for restart. In log i see message: [Jun 25 03:30:27] ERROR[18676] astobj2.c: user_data is NULL | ||||
| Comments: | By: c0rnoTa (c0rnota) 2014-06-25 00:57:38.842-0500 I have made dump of 'core show locks' at this moment. Here it is By: c0rnoTa (c0rnota) 2014-06-25 03:47:14.053-0500 Got a backtrace of a deadlock By: c0rnoTa (c0rnota) 2014-06-25 09:51:42.590-0500 Looks like it stable when not compiled with DEBUG options. (DONT_OPTIMIZE, DEBUG_THEADERS and BETTER_BACKTRACES) By: Richard Mudgett (rmudgett) 2014-06-25 10:34:25.814-0500 You should *not* normally run with DEBUG_THREADS enabled. It can really slow down your system and can cause its own locking problems. By: Matt Jordan (mjordan) 2014-06-25 11:16:22.698-0500 This issue has been reported a lot under a number of different names. To keep the issue tracker sane - and so everyone who runs into this problem can find the same solution - I'm closing this out as a duplicate of ASTERISK-22851. | ||||