[Home]

Summary:ASTERISK-14546: Crash in autoservice (locking)
Reporter:Badalian Vyacheslav (slavon)Labels:
Date Opened:2009-07-28 01:58:42Date Closed:2011-06-07 14:00:46
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) gdb_10aug.txt
( 1) gdb_28jul.txt
( 2) gdb_29jul.txt
( 3) gdb_31jul.txt
( 4) gdb_3aug.txt
( 5) gdb_5aug.txt
( 6) gdb_7aug.txt
( 7) gdbx.txt
Description:i be in console when it crash :) BT file attached. this i see in console before crash:

[Jul 28 10:06:02] ERROR[13978]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:431 __ast_pthread_mutex_lock: autoservice.c line 263 (ast_autoservice_stop): Error obtaining mutex: Invalid argument                                        
[Jul 28 10:06:02] ERROR[13978]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:506 __ast_pthread_mutex_unlock: autoservice.c line 289 (ast_autoservice_stop): attempted unlock mutex '&(&aslist)->lock' without owning it!                
[Jul 28 10:06:02] ERROR[13978]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:508 __ast_pthread_mutex_unlock: (null) line 1 ((null)): '&(&aslist)->lock' was locked here.                                                                
[Jul 28 10:06:02] ERROR[13978]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:531 __ast_pthread_mutex_unlock: autoservice.c line 289 (ast_autoservice_stop): Error releasing mutex: Invalid argument                                      
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:431 __ast_pthread_mutex_lock: autoservice.c line 263 (ast_autoservice_stop): Error obtaining mutex: Invalid argument                                        
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:506 __ast_pthread_mutex_unlock: autoservice.c line 289 (ast_autoservice_stop): attempted unlock mutex '&(&aslist)->lock' without owning it!                
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:508 __ast_pthread_mutex_unlock: (null) line 2063597568 ((null)): '&(&aslist)->lock' was locked here.                                                        
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:531 __ast_pthread_mutex_unlock: autoservice.c line 289 (ast_autoservice_stop): Error releasing mutex: Invalid argument                                      
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:431 __ast_pthread_mutex_lock: autoservice.c line 263 (ast_autoservice_stop): Error obtaining mutex: Invalid argument                                        
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:506 __ast_pthread_mutex_unlock: autoservice.c line 289 (ast_autoservice_stop): attempted unlock mutex '&(&aslist)->lock' without owning it!                
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:508 __ast_pthread_mutex_unlock: (null) line 101 ((null)): '&(&aslist)->lock' was locked here.                                                              
[Jul 28 10:06:02] ERROR[12505]: /usr/src/asterisk-1.4.26/include/asterisk/lock.h:531 __ast_pthread_mutex_unlock: autoservice.c line 289 (ast_autoservice_stop): Error releasing mutex: Invalid argument                                      
Comments:By: Badalian Vyacheslav (slavon) 2009-08-10 00:20:48

And many new crash. As i see is two different crashes.
One this and one then i do asterisk -rx "queues show" i think.
By: Mark Michelson (mmichelson) 2009-08-10 10:01:09

Your crashes are happening in very many areas. I would suggest running Asterisk under valgrind if possible. See instructions in doc/valgrind.txt
By: Badalian Vyacheslav (slavon) 2009-08-11 00:20:55

Ghm.... not posible... not have mutch CPU for this. Without valgrind asterisk use about 60% cpu...
By: Leif Madsen (lmadsen) 2009-09-15 12:34:25

Closing this issue for now as the reporter is unable to run this under valgrind, but the developers can't move this issue forward without it.

If you're able to reproduce this in a lab scenario and capture the output under valgrind, then please reopen this issue. Thanks!