[asterisk-bugs] [JIRA] (ASTERISK-23410) Asterisk not executing properly on CentOS 6.5
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Sun Mar 2 09:47:48 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-23410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215974#comment-215974 ]
Matt Jordan commented on ASTERISK-23410:
----------------------------------------
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
> Asterisk not executing properly on CentOS 6.5
> ---------------------------------------------
>
> Key: ASTERISK-23410
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-23410
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Affects Versions: 1.8.12.2, 1.8.25.0, 11.7.0, 12.0.0
> Environment: CentOS 6.5 latest update
> Reporter: Trent Creekmore
> Severity: Critical
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list