| Summary: | ASTERISK-23410: Asterisk not executing properly on CentOS 6.5 | ||
| Reporter: | Trent Creekmore (tcreek) | Labels: | |
| Date Opened: | 2014-03-01 18:57:40.000-0600 | Date Closed: | 2014-03-04 19:30:23.000-0600 |
| Priority: | Trivial | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 1.8.12.2 1.8.25.0 11.7.0 12.0.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS 6.5 latest update | Attachments: | |
| Description: | Compiling on the machine doing:
/configure make menuselect (tried Build Native checked and unchecked after v1.8.12) make make install starting with /usr/sbin/safe_asterisk Versions 11 and 12 are reporting: Asterisk ended with exit status 127 Asterisk died with code 127. Automatically restarting Asterisk Version 1.8.x is not reporting any errors, just refuses to load any modules. This have been tested on four different machines with different CPUs (P4, AMD X2s, and Intel Core 2 Duo). | ||
| Comments: | By: Matt Jordan (mjordan) 2014-03-02 09:46:49.424-0600 Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Trent Creekmore (tcreek) 2014-03-04 19:25:11.386-0600 You can close this. It was how I was build the versions. Sorry | ||