Summary:ASTERISK-07890: Asterisk Server Crash 5 times in one day
Reporter:Jorge Cisneros (jorgeci)Labels:
Date Opened:2006-10-06 14:01:04Date Closed:2011-06-07 14:00:48
Versions:Frequency of
Environment:Attachments:( 0) core.bt
Description:When i upgrade my asterisk form verion 1.2.9 to 1.2.11 the asterisk crash 5 times in just one day.

Attach the core and the gdb bt full
Comments:By: Anthony LaMantia (alamantia) 2006-10-06 14:15:09

please make sure your copy of asterisk is built with make dont optimize  , and do include a console debug log so we can get more of an idea about what is going on inside of asterisk on your server.

By: Serge Vecher (serge-v) 2006-10-06 14:17:16

also, the latest Asterisk release is, not 1.2.11

By: Jorge Cisneros (jorgeci) 2006-10-06 14:42:08

Ths last log from console

   -- Executing Set("SIP/8823-2501", "the_num=52228371") in new stack
   -- Executing Dial("SIP/8823-2501", "Unicall/g1/52228371|120|rwW") in new stack
   -- Called g1/52228371
   -- Hungup 'UniCall/34-1'
 == Spawn extension (macro-dialout-trunk, s, 23) exited non-zero on 'SIP/8647-8c90' in macro 'dialout-trunk'
 == Spawn extension (macro-dialout-trunk, s, 23) exited non-zero on 'SIP/8647-8c90'
   -- Executing Macro("SIP/8647-8c90", "hangupcall") in new stack
   -- Executing ResetCDR("SIP/8647-8c90", "w") in new stack
   -- Executing NoCDR("SIP/8647-8c90", "") in new stack
   -- Executing Wait("SIP/8647-8c90", "5") in new stack
 == Spawn extension (macro-hangupcall, s, 3) exited non-zero on 'SIP/8647-8c90' in macro 'hangupcall'
 == Spawn extension (macro-hangupcall, s, 3) exited non-zero on 'SIP/8647-8c90'
 == End MixMonitor Recording SIP/8647-8c90

By: Jorge Cisneros (jorgeci) 2006-10-06 14:42:50

The asterisk terminet with

Asterisk ended with exit status 137
Asterisk exited on signal 9.

By: Anthony LaMantia (alamantia) 2006-10-06 14:55:09

please try upgrading to the latest 1.2 release from SVN. this has a good chance of resolving your problem

By: Serge Vecher (serge-v) 2006-10-06 16:04:19

as alamantia said, this should be fixed by the recent round of bug-fixes to app_mixmonitor in 1.2 branch code. Please checkout the 1.2 svn branch or wait for 1.2.13 release. If problems still exists in those versions, please reopen the bug with the backtrace attached and a noting revision / release used. Thank you.