[asterisk-bugs] [Asterisk 0015958]: Asterisk dies with error code 127

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Sep 25 15:29:44 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15958 
====================================================================== 
Reported By:                pta200
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15958
Category:                   Channels/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.26.2 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 219986 
Request Review:              
====================================================================== 
Date Submitted:             2009-09-24 15:03 CDT
Last Modified:              2009-09-25 15:29 CDT
====================================================================== 
Summary:                    Asterisk dies with error code 127
Description: 
Asterisk dies with error code 127 right after hanging up a call using
either SIP or IAX. The system is running on CentOS release 5.3

I also tried using 1.4.26 and 1.4.22 and then 1.6.0.9 and finally
1.6.0.15. There are nore core dumps and no messages in the logs. Asterisk
dies after the hang up and then safe_asterisk restarts. I have the exact
same configuration running on a 32bit linux box running Fedora Core 5 with
no problems. The 1.6.0.15 svn revision is 220222.
====================================================================== 

---------------------------------------------------------------------- 
 (0111389) pta200 (reporter) - 2009-09-25 15:29
 https://issues.asterisk.org/view.php?id=15958#c111389 
---------------------------------------------------------------------- 
Figured out what the problems was. The system writes cdr to a MySQL
database. For some reason yum installed two versions of the MySQL ODBC
drivers and there was an issue with the MySQL database itself. Due to this
issues when the call was hung up Asterisk would crash while trying to write
the record to the database but provide no core dump, error log, anything to
indicate the nature of the crash. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-25 15:29 pta200         Note Added: 0111389                          
======================================================================




More information about the asterisk-bugs mailing list