Summary:ASTERISK-13014: Crash while processing events in manager.c
Reporter:Marcin Kowalczyk (kowalma)Labels:
Date Opened:2008-11-04 15:03:41.000-0600Date Closed:2009-01-20 14:03:01.000-0600
Versions:Frequency of
Environment:Attachments:( 0) core.asterisk-IBM-2008-11-04T17_55.txt

My Asterisk box crashed today. At begining I thought it was caused by chan_iax but it was caused by manager.c


Asterisk @ IBM x3400 + Sangoma A104d (wanpipe 3.3.14) + DAHDI 2.0 + asterisk-addons + asterisk patch for chan_iax.c
Kernel 2.6.19-7
gcc 4.1.2

Approx 30 clients connects to manager port to check queue status.

It was one crash I've noticed at the moment. I've setup tcpdump to monitor what is send to manager port and I will try to reproduce this error.

Please find attached backtrace from this crash.
Comments:By: Tilghman Lesher (tilghman) 2008-11-04 15:28:31.000-0600

To me, this suggests possible memory corruption.  Could you please follow the instructions in doc/valgrind.txt ?

By: Marcin Kowalczyk (kowalma) 2008-11-04 15:41:11.000-0600

valgrind configured. let's wait for crash.

By: Tilghman Lesher (tilghman) 2008-11-04 16:36:46.000-0600

Please understand that while valgrind may prevent the crash from occurring, the output that it generates is still very valuable.  Once you hit the load that previously caused this issue, it may be worth simply uploading the resulting file.

By: Leif Madsen (lmadsen) 2008-12-22 11:26:12.000-0600

kowalma:  it's been a while since we've heard from you. Do you happen to have the requested information? If not, then we'll need to close the issue due to lack of response.


By: Marcin Kowalczyk (kowalma) 2008-12-22 16:31:29.000-0600


I was out of office last time, but I'm back. My box start crashing again on IAX2 bug ASTERISK-12914.

I've also applied on the box, and I don't see any crash caused by manager.c

By: Leif Madsen (lmadsen) 2009-01-20 14:03:00.000-0600

Closing this as it appears the reporter can no longer reproduce on a newer version. Please find a bug marshal on the IRC network irc.freenode.net in #asterisk-bugs to have the issue reopened should you feel this issue was closed in error.