Summary:ASTERISK-21695: Crash Asterisk
Reporter:Osvaldo Tuphiq Smera Neto (osvaldo)Labels:
Date Opened:2013-04-25 14:18:34Date Closed:2013-04-29 19:00:07
Versions: Frequency of
Environment:Attachments:( 0) backtrace2404.txt
( 1) backtrace250415.txt
( 2) backtrace250417.txt
( 3) backtrace-threads.txt
( 4) mmlog
Description:Open to question ASTERISK-20830, where there's no asterisk crash after some time of use. Be finding the memory, changed server and resolved. To my surprise, after 3 months of use, the crash's occur again, as before, at the same time every day. Interestingly, just as occurred in another server, slow to occur, occur at the same time, and I'm afraid to go and also pass to run more than once a day. Here's the last 2 core and mmlog.
Comments:By: Rusty Newton (rnewton) 2013-04-26 09:53:06.678-0500

The cores are not useful, please follow the instructions here: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace to provided the needed backtrace. Attach them separately to the ticket in .txt format.

By: Osvaldo Tuphiq Smera Neto (osvaldo) 2013-04-26 15:12:38.009-0500

Following files over crash.

By: Richard Mudgett (rmudgett) 2013-04-26 20:24:56.633-0500

These crashes are from memory corruption just like the previous issue ASTERISK-20830.
Valgrind output or MALLOC_DEBUG output from *Asterisk v1.8.20* or newer is needed.  Asterisk v1.8.20 improved MALLOC_DEBUG to catch and detect more problems.

The MALLOC_DEBUG mmlog from an earlier Asterisk version you have provided is showing some fence violations.  The improved MALLOC_DEBUG from Asterisk v1.8.20 or newer should give better information.

By: Osvaldo Tuphiq Smera Neto (osvaldo) 2013-04-29 14:29:22.401-0500

The problem reinstalling the asterisk is that likely to be regular for 3 months and then reverts to crash's exactly how the issue ASTERISK-20830. What is more strange is that always occur daily at the exact time, and probably, as in issue ASTERISK-20830 will occur more cases per day. I will reinstall on another server with new version of Asterisk, and hopefully not having to open the call within 3 months! Are there any recommendations?

By: Rusty Newton (rnewton) 2013-04-29 19:00:08.003-0500

Please follow Richard's recommendation. Also if possible, keep a rotating Asterisk full log (logger.conf) gathering VERBOSE and DEBUG at level 5. When the crash happens save attach the last few minutes of that log to this issue.

I'll suspend this issue until you are able to gather the next set of data. When that happens just comment on this issue, or ping a bug marshal in #asterisk-bugs on irc.freenode.net.