[asterisk-bugs] [Asterisk 0014747]: Coredump of asterisk in ramdom time
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Apr 9 10:56:29 CDT 2009
The following issue has been CLOSED
======================================================================
http://bugs.digium.com/view.php?id=14747
======================================================================
Reported By: cmorata
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14747
Category: General
Reproducibility: unable to reproduce
Severity: crash
Priority: normal
Status: closed
Asterisk Version: 1.4.21.1
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2009-03-25 07:19 CDT
Last Modified: 2009-04-09 10:56 CDT
======================================================================
Summary: Coredump of asterisk in ramdom time
Description:
Hi.
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 at 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 at 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.
======================================================================
----------------------------------------------------------------------
(0103006) lmadsen (administrator) - 2009-04-09 10:56
http://bugs.digium.com/view.php?id=14747#c103006
----------------------------------------------------------------------
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!
Issue History
Date Modified Username Field Change
======================================================================
2009-04-09 10:56 lmadsen Note Added: 0103006
2009-04-09 10:56 lmadsen Status new => closed
======================================================================
More information about the asterisk-bugs
mailing list