| Summary: | ASTERISK-23928: Device state collector stop to work | ||||
| Reporter: | Matteo (mpiazzatnetbug) | Labels: | |||
| Date Opened: | 2014-06-25 07:01:49 | Date Closed: | 2014-06-25 11:13:59 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | General | ||
| Versions: | 11.10.2 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Debian 6.0.7 virtualized on Proxmox 3.1 (KVM) Memory 1Gb CPU 2.27 GHz (1 socket) | Attachments: | ( 0) asterisk.11.10.2-lock-device.txt ( 1) backtrace-threads-lock-device.txt | ||
| Description: | After some running times (1-2 hours) the asterisk stops to collect the device state.
When this happens i can see a lock with core show locks. The core stop now command become unresposive As attachment the result of the core show lock and the relative backtrace. on this asterisk instances we collect 5000 device state. | ||||
| Comments: | By: Matt Jordan (mjordan) 2014-06-25 11:13:59.085-0500 Your backtrace shows that this is occurring due to a known issue with DEBUG_THREADS. Please disable DEBUG_THREADS - that should resolve the particular locking issue you are seeing. This issue is currently being tracked under ASTERISK-22851. If the locking issue persists after disabling DEBUG_THREADS, please comment on this issue. | ||||