| Summary: | ASTERISK-14882: Asterisk dies with error code 127 | ||
| Reporter: | pta200 (pta200) | Labels: | |
| Date Opened: | 2009-09-24 15:03:51 | Date Closed: | 2011-06-07 14:01:01 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) extensions.conf ( 1) iax.conf ( 2) IAX-DEBUG.txt ( 3) sip.conf ( 4) SIP-DEBUG.txt | |
| 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. ****** STEPS TO REPRODUCE ****** Just call an extension in the inbound-calls context. You can follow through the IVR or not, but as soon as you hang up Asterisk dies. | ||
| Comments: | By: pta200 (pta200) 2009-09-24 15:06:17 IBM System X 3350; machine type 4193 By: pta200 (pta200) 2009-09-24 15:08:18 Intel Chipset; Quad Core Xeon Processor X3370 By: pta200 (pta200) 2009-09-24 16:22:50 Tried 1.4.20.1 svn revision 220375 and have the same problem By: pta200 (pta200) 2009-09-25 15:29:44 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. By: Tilghman Lesher (tilghman) 2009-09-26 23:01:06 Linux distribution problem. | ||