Bug 1105338 - [abrt] asterisk: __attempt_transmit(): asterisk killed by SIGABRT
Summary: [abrt] asterisk: __attempt_transmit(): asterisk killed by SIGABRT
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: asterisk
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeffrey C. Ollie
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:3561842de5ce3df48cf856bee2b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-05 22:33 UTC by Samuel Sieb
Modified: 2014-06-19 22:01 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-19 22:01:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (86.98 KB, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: cgroup (151 bytes, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: core_backtrace (72.90 KB, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: dso_list (22.90 KB, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: environ (3.40 KB, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: limits (1.29 KB, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: maps (121.87 KB, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: open_fds (719 bytes, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
File: proc_pid_status (914 bytes, text/plain)
2014-06-05 22:33 UTC, Samuel Sieb 		no flags Details
View All

Description Samuel Sieb 2014-06-05 22:33:43 UTC 
Description of problem:
Asterisk had been running for a couple of months. I got a message saying the phones were down.  When I checked, I saw that it had aborted.

I did just check and I see that there is an update for asterisk available, so this report might already be obsolete.

Version-Release number of selected component:
asterisk-11.8.1-1.fc19

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        asterisk -vvv -c
crash_function: __attempt_transmit
executable:     /usr/sbin/asterisk
kernel:         3.13.7-100.fc19.x86_64
runlevel:       N 3
type:           CCpp
uid:            0
var_log_messages: Jun  5 14:02:54 gw abrt-hook-ccpp[9708]: Saved core dump of pid 8909 (/usr/sbin/asterisk) to /var/tmp/abrt/ccpp-2014-06-05-14:02:35-8909 (95232000 bytes)

Truncated backtrace:
Thread no. 1 (3 frames)
 #5 __attempt_transmit at chan_iax2.c:3607
 #6 iax2_process_thread at chan_iax2.c:11983
 #7 dummy_start at utils.c:1162
Comment 1 Samuel Sieb 2014-06-05 22:33:49 UTC 
Created attachment 902695 [details]
File: backtrace
Comment 2 Samuel Sieb 2014-06-05 22:33:50 UTC 
Created attachment 902696 [details]
File: cgroup
Comment 3 Samuel Sieb 2014-06-05 22:33:53 UTC 
Created attachment 902697 [details]
File: core_backtrace
Comment 4 Samuel Sieb 2014-06-05 22:33:53 UTC 
Created attachment 902698 [details]
File: dso_list
Comment 5 Samuel Sieb 2014-06-05 22:33:54 UTC 
Created attachment 902699 [details]
File: environ
Comment 6 Samuel Sieb 2014-06-05 22:33:55 UTC 
Created attachment 902700 [details]
File: limits
Comment 7 Samuel Sieb 2014-06-05 22:33:56 UTC 
Created attachment 902701 [details]
File: maps
Comment 8 Samuel Sieb 2014-06-05 22:33:57 UTC 
Created attachment 902702 [details]
File: open_fds
Comment 9 Samuel Sieb 2014-06-05 22:33:58 UTC 
Created attachment 902703 [details]
File: proc_pid_status
Comment 10 Samuel Sieb 2014-06-06 01:51:31 UTC 
Looks like the error was "double free or corruption (out)" in __attempt_transmit.
Comment 11 Jeffrey C. Ollie 2014-06-19 21:03:13 UTC 
Please test with 11.9.0 that is the most current stable package or test with 11.10.2 that was just pushed to updates-testing (may take 24hrs or so for the mirrors to catch up).  11.9.0 was made a stable update on 2014-05-08 so it's was out for a month or so before you submitted a report.  If the problem still occurs please open a bug report with Digium.
Comment 12 Samuel Sieb 2014-06-19 21:46:47 UTC 
I did notice that there was an update when I filed this.  I will update to the lastest version over the weekend.  However, since I have no way to reproduce this and the system will get very little use over the next couple of months (it's a school phone system), I guess there's not much more to do here.
Comment 13 Jeffrey C. Ollie 2014-06-19 22:01:26 UTC 
OK, I'm going to close this out then.  If there's any new information reopen the bug.
Note You need to log in before you can comment on or make changes to this bug.