Summary:ASTERISK-13825: Coredump of asterisk in ramdom time
Reporter:C. Morata (cmorata)Labels:
Date Opened:2009-03-25 07:19:34Date Closed:2011-06-07 14:00:40
Versions:Frequency of
Environment:Attachments:( 0) core.2009-03-03T18:04:59+0100.script
( 1) core.2009-03-03T18:04:59+0100.txt
( 2) core.2009-03-03T20:18:31+0100.script
( 3) core.2009-03-11T18:10:46+0100.script
( 4) core.2009-03-12T18:00:54+0100.script
( 5) core.2009-03-13T19:04:00+0100.script
( 6) core.2009-03-17T11:06:14+0100.script
( 7) core.2009-03-23T18:06:53+0100.txt
( 8) core.2009-03-24T12:10:03+0100.txt
( 9) core.2009-03-24T14:04:57+010.txt

We are running asterisk with 65 agents, that is running with several queues and a month ago its have started to crash and write coredumps in /tmp.

We don't change anything in asterisk.

In the last month its has done 10 coredumps.

The memory in the server is:

user@ldebian:/tmp$ free
            total       used       free     shared    buffers     cached
Mem:       1035528     910992     124536          0     187940     551760
-/+ buffers/cache:     171292     864236
Swap:      1951856         36    1951820

The uptime its:
user@debian:/tmp$ uptime
13:15:20 up 22 days, 18:57,  1 user,  load average: 0.42, 0.73, 1.08

We think that it's possible that the problem came from the ram but we are not sure.

I attach 9 backtraces for yours information.

Cheers and best regards.
Comments:By: Eliel Sardanons (eliel) 2009-03-25 16:04:10

cmorata, thanks for reporting the issue, I have seen you core dumps and they have not useful information to find why is asterisk crashing in your environment.
I think this is because asterisk is compiled with DONT_OPTIMIZE disabled. Please run 'make menuselect' and go to the "Compiler Flags" menu and select the "DONT_OPTIMIZE" option. Re-compile asterisk, wait for a crash and run again gdb and upload the 'bt full', etc.

Thanks in advanced

By: C. Morata (cmorata) 2009-03-26 05:41:53

Hi eliel

First one, a lot of thanks for your reply. :)

We have decided add ram and then test it before change the flags in asterisk for rule out possibles problems with the amount and quality in the RAM.

Today we going to realize the change, we hope thats its resolve the problem. :)

Cheers and thank you.

By: Leif Madsen (lmadsen) 2009-04-09 10:56:28

I'm going to close this out since the reporter has not said anything for about 2 weeks, and thus I'll assume changing the RAM fixed his issue. If not, then please feel free to reopen. Thanks!