Summary:ASTERISK-20830: Asterisk crash
Reporter:Osvaldo Tuphiq Smera Neto (osvaldo)Labels:
Date Opened:2012-12-18 12:40:42.000-0600Date Closed:2013-02-04 13:50:28.000-0600
Status:Closed/CompleteComponents:Addons/cdr_mysql Applications/app_originate Applications/app_queue
Versions: Frequency of
Environment:auto dialer with agents in DACAttachments:( 0) bt.txt
( 1) btFull.txt
( 2) core.astCobresp-2012-12-18T140423-0200.tar
( 3) valgrind.txt
Description:Asterisk crash occur in daily schedules like at least twice daily. what can it be? 've tried everything. I have an auto dialer.
Comments:By: Osvaldo Tuphiq Smera Neto (osvaldo) 2012-12-18 13:28:39.092-0600

when the crash occurs, the following message appears:

Asterisk ended with exit status 134 Asterisk exited on signal 6
Asterisk ended with exit status 134 Asterisk exited on signal 11.

By: Richard Mudgett (rmudgett) 2012-12-18 15:29:29.939-0600

Valgrind is pointing out that /opt/khomp/pth_tls/lib/libpth_tls.so.20.0.27 is the culprit corrupting memory.

After that the problems just seem to snowball into these modules:

By: Osvaldo Tuphiq Smera Neto (osvaldo) 2012-12-19 07:12:46.492-0600

That means there is a problem in physical memory or are only those modules?
The crash was occurring before the module Khomp (E1 card) was installed. Really started to occur more often.
Already envieie email to the manufacturer of the card and they are already analysand logs. An interesting information is that the crash's always occur at similar times.
There is some indication of what can I do?

By: Rusty Newton (rnewton) 2012-12-19 08:48:07.126-0600

Richard's analysis indicates the Khomp modules as the most likely issue. We recommend working with them to troubleshoot the issue further.

If you can reproduce the issue without any of those modules involved, and provide backtraces and debug from that new reproduction, then we can look further into it. You can open a new issue at that point.

By: Osvaldo Tuphiq Smera Neto (osvaldo) 2012-12-19 12:45:02.375-0600

I disabled the module Khomp. I'll report the result.

By: Osvaldo Tuphiq Smera Neto (osvaldo) 2012-12-20 08:09:20.364-0600

Even without module Khomp activated happen again fall in asterisk. Any other suggestions?

By: Matt Jordan (mjordan) 2012-12-20 08:17:32.701-0600

Saying "Asterisk fails" without providing any artifacts showing the failure doesn't help those triaging this issue.

# Completely remove all third party modules from Asterisk.
# Run Asterisk under valgrind, using the instructions linked below [1]
# Attach the valgrind output to this issue.


[1] https://wiki.asterisk.org/wiki/display/AST/Valgrind

By: Osvaldo Tuphiq Smera Neto (osvaldo) 2012-12-26 11:20:08.176-0600

I can not start with the command under valgrind

valgrind - suppressions = / usr/src/asterisk- - log-fd = 9 vvvvcg asterisk-9> valgrind.txt.

The computer processing becomes overloaded and autodial can not be started.
Any suggestions?

By: Rusty Newton (rnewton) 2013-01-17 15:55:42.064-0600

Can you test with asterisk 1.8.20? There are enhancements to the MALLOC_DEBUG compilation option that could possibly give us more info, but likely not enough to pinpoint the issue. After compilation and reproduction, post /var/log/asterisk/mmlog

Other that, I'm afraid we may be out of options unless you can reproduce the issue on a system where you can run valgrind.

By: Rusty Newton (rnewton) 2013-02-04 13:50:28.843-0600

Closing this until we get valgrind or mmlog (MALLOC_DEBUG) output to help narrow down the issue. Feel free to re-open or contact a bug marshal in #asterisk-bugs if you are able to obtain the debug required. You can always contact other users on the asterisk users list for help in troubleshooting or gathering debug.