Segmentation fault when applying changes

Hi,

We are running FPBX 2.9.0.7 on centos 5.6 and asterisk 1.6.2.19

Whenever we commit a configuration change via the admin screen we often crash the asterisk process with a segmentation fault-

[[email protected] ~]# /usr/sbin/safe_asterisk: line 145: 7518 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.

It occurs about 50% of the time when we commit changes by pressing the orange bar

They should be the same version, I installed everything from asterisk’s own yum repo !

The backtrace can be found here-
http://files.onecomms.co.uk/backtrace.txt

Check that your Asterisk modules in /usr/lib/asterisk/modules are with the same date.
How to debug Asterisk: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

Have you updated Centos?
Do you run this in a XEN environment?

No, this is a standard Centos5 install from Centos repos.
kernel is 2.6.18-238.12.1.el5

Any updates have always been done via yum.

Its happening on several of our PBXs now, all running asterisk 1.6.2.19 and FPBX 2.8.1 as well as 2.9

Hi,

This does like like exactly the same issue I am seeing on my thread http://www.freepbx.org/forum/freepbx/general-help/asterisk-crashing-on-reload-after-system-recording#comment-39559.

Thanks for the heads up and I have subscribed.

Graham

Heres another example, completely different PBX, running asterisk 1.6.2.19 and FPBX 2.8.1.4

Again, the asterisk process crashes whenever we commit a change via FPBX

http://files.onecomms.co.uk/backtrace2.txt

tonyclewis,

I need the fax modules in for Fax for Asterisk to work, or do you mean just as a temporary test?

Mickecarlsson,

I am using PIAF so I will need to find out how to move to an earlier version of Asterisk.

Graham

Hi,

This is the backtrace from clicking the red bar after using system recordings.

https://docs.google.com/leaf?id=0B2XXjV4PAzIwNzkwMTI5OTctNjZkZi00MGExLWI4ZjEtMGJlZmI2MTJmOThm&hl=en_US&authkey=CIGVt7wK

Regards,

Graham

Hi,

I have checked the module dates and they are all July 3rd except res_fax_digium.so and res_fax.so, I assume because they are installed separately as part of Asterisk Fax.

Graham

Remove those files or noload them in /etc/asterisk/modules.conf

GWalmsley, you need to recompile Asterisk and select DONT_OPTIMIZE in menuselect.
What happens if you install 1.6.2.18?

Bug in Asterisk 1.6.2.19:
https://issues.asterisk.org/jira/browse/ASTERISK-18103

yep, Ive just downgraded to the previous RPM, 1.6.2.18-2 and it works fine now!

Ok, so I just need to work out how to downgrade to 1.6.2.18-2 in PIAF and its fixed.

Shame Digium introduce a bug in the final ‘bugfix’ but then won’t fix it.

Graham

Hi,

Just a quick update, the bug is going to be fixed in 1.6.2.19.1.

https://issues.asterisk.org/jira/browse/ASTERISK-18103

Graham