[Home]

Summary:ASTERISK-20173: segfault Asterisk
Reporter:JS (jusi)Labels:
Date Opened:2012-07-26 09:39:47Date Closed:2012-08-29 08:59:23
Priority:CriticalRegression?
Status:Closed/CompleteComponents:
Versions:Frequency of
Occurrence
Frequent
Related
Issues:
Environment:Attachments:
Description:[1707741.703754] asterisk[24829]: segfault at 7fb500000019 ip 00007fb62abfaa66 sp 00007fb603b1a040 error 4 in libc-2.11.3.so[7fb62ab86000+159000]

sometimes ( every 2 weeks) the service "asterisk" close due to segfault.

Asterisk Version :   Asterisk 1.8.11.1
OS : Linux version 2.6.32-5-amd64 (Debian 2.6.32-41squeeze2)
third party : freepbx , mysql, apache2
Frequency and timing of the issue : random but near every 2 weeks
Symptoms : Close asterisk's service

12 Go Ram
4 CPU

Around 160 users

I can't reproduce this bug.

Comments:By: Rusty Newton (rnewton) 2012-07-26 09:50:19.953-0500

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. You may find it helpful to read the Asterisk Issue Guidelines https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf). Thanks!


Please include an Asterisk full log with DEBUG of level 5 leading up to the seg fault, and follow the instructions here to obtain a backtrace: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

By: Matt Jordan (mjordan) 2012-08-29 08:59:15.661-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines