Segmentation fault PIAF-Bronze

[Bruce]

Hi everyone,

I am pretty sure someone knows what is happnening these days with Piaf (well, mostly FreePBX probably) with the new segmentation fault. I am guessing it's FreePBX because when I upgraded the module to latest stable 2.8x version Asterisk randomely disconnects and sometimes comes back but sometimes crashes until I have to do asterisk -g again.

Here is what I have:

Since Asterisk 1.6.2.19 we get segmentation faults when commiting changes via the freepbx console.

This applies to both 2.9 and 2.8 versions of FreePBX, using asterisk 1.6.2.19 RPMs from the asterisk repo

Whenever we apply changes to the freepbx screen we get this-

/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.

I appreciate some input on this.

Bronze installed: 1.6.2.19

What could be the issue?

Thanks

 

[darmock]

I suppose I need to ask how you are applying the asterisk RPM's as we dont use them in PBX in a Flash? If you are doing in place upgrades using the asterisk repo then this is your problem as you should not ever mix rpm installs with compiled installs too many problems.

The rpm method is NOT supported for asterisk specifically.

So are u running PIAF or the freepbx distro? If you are running PIAF then please attach the output from status as a starting point.

If you are running freepbx distro you need to talk to them in their forums


Tom


Tom

 

[Bruce]

Hi,

As I mentioned it's PiaF and I haven't used Digium repos at all. This is a fresh install of Piaf alone. Below is the status from the system:

┌────────────────────────System Information───────────────────────────┐
│ Asterisk = ONLINE | Dahdi = ONLINE | MySQL = ONLINE │
│ SSH = ONLINE | Apache = ONLINE | Iptables = ONLINE │
│ Fail2ban = ONLINE | Internet = ONLINE | Ip6Tables = ONLINE │
│ BlueTooth = ONLINE | Hidd = ONLINE | NTPD = ONLINE │
│ SendMail = ONLINE | Samba = OFFLINE | Webmin = ONLINE │
│ Ethernet0 = ONLINE | Ethernet1 = N/A | Wlan0 = N/A │
│ │
│ PBX in a Flash Version = 1.7.5.5 Running on *HARDWARE* │
│ FreePBX Version = 2.8.1.4 │
│ Running Asterisk Version = 1.6.2.19 │
│ Asterisk Source Version = 1.6.2.19 │
│ Dahdi Source Version = 2.4.1.2+2.4.1 │
│ Libpri Source Version = 1.4.12 │
│ Addons Source Version = 1.6.2.3 │
│ IP Address = 192.168.0.99 on eth0 │
│ Operating System = CentOS release 5.6 (Final) │
│ Kernel Version = 2.6.18-194.26.1.el5 - 32 Bit


What I mentioned was that when I used FreePBX modules upgrade to upgrade it from the 2.6x (because PBXinaFLASH has a FreePBX base of 2.6x still) to 2.8 then it crashes. This is all done through the FreePBX GUI upgrades only. Nothing more.

There are some complains on Digium lists as well regarding Asterisk 1.6.2.19 crashing. This could also be due to OOH322 or other modules enabled by FreePBX...I have seen this behaviour in the past few weeks on multiple installs.

Where would an Asterisk segmentation fault be logged usually on PiaF installed system?

Regards,

 

[darmock]

Hi,

As I mentioned it's PiaF and I haven't used Digium repos at all. This is a fresh install of Piaf alone. Below is the status from the system:

┌────────────────────────System Information───────────────────────────┐
│ Asterisk = ONLINE | Dahdi = ONLINE | MySQL = ONLINE │
│ SSH = ONLINE | Apache = ONLINE | Iptables = ONLINE │
│ Fail2ban = ONLINE | Internet = ONLINE | Ip6Tables = ONLINE │
│ BlueTooth = ONLINE | Hidd = ONLINE | NTPD = ONLINE │
│ SendMail = ONLINE | Samba = OFFLINE | Webmin = ONLINE │
│ Ethernet0 = ONLINE | Ethernet1 = N/A | Wlan0 = N/A │
│ │
│ PBX in a Flash Version = 1.7.5.5 Running on *HARDWARE* │
│ FreePBX Version = 2.8.1.4 │
│ Running Asterisk Version = 1.6.2.19 │
│ Asterisk Source Version = 1.6.2.19 │
│ Dahdi Source Version = 2.4.1.2+2.4.1 │
│ Libpri Source Version = 1.4.12 │
│ Addons Source Version = 1.6.2.3 │
│ IP Address = 192.168.0.99 on eth0 │
│ Operating System = CentOS release 5.6 (Final) │
│ Kernel Version = 2.6.18-194.26.1.el5 - 32 Bit


What I mentioned was that when I used FreePBX modules upgrade to upgrade it from the 2.6x (because PBXinaFLASH has a FreePBX base of 2.6x still) to 2.8 then it crashes. This is all done through the FreePBX GUI upgrades only. Nothing more.

There are some complains on Digium lists as well regarding Asterisk 1.6.2.19 crashing. This could also be due to OOH322 or other modules enabled by FreePBX...I have seen this behaviour in the past few weeks on multiple installs.

Where would an Asterisk segmentation fault be logged usually on PiaF installed system?

Regards,

/var/log/asterisk


Also in your previous post you say

" This applies to both 2.9 and 2.8 versions of FreePBX, using asterisk 1.6.2.19 RPMs from the asterisk repo"

This indicates to me that you upgraded Asterisk from the asterisk repo which we dont use. Do you understand why I concluded you were using a non standard method or install?

On our reference platform with the latest build of bronze we cannot duplicate this problem I am afraid. I would recommend you buy some support time from freepbx as this seems to be your main problem.



Good luck with it.

Tom

 

[darmock]

For posterity's sake underlines and bolded added

Hi everyone,

I am pretty sure someone knows what is happnening these days with Piaf (well, mostly FreePBX probably) with the new segmentation fault. I am guessing it's FreePBX because when I upgraded the module to latest stable 2.8x version Asterisk randomely disconnects and sometimes comes back but sometimes crashes until I have to do asterisk -g again.

Here is what I have:

Since Asterisk 1.6.2.19 we get segmentation faults when commiting changes via the freepbx console.

This applies to both 2.9 and 2.8 versions of FreePBX, using asterisk 1.6.2.19 RPMs from the asterisk repo

Whenever we apply changes to the freepbx screen we get this-

/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.

I appreciate some input on this.

Bronze installed: 1.6.2.19

What could be the issue?

Thanks

 

[malcolmd]

Someone's opened an issue on the issue tracker about it here:
https://issues.asterisk.org/jira/browse/ASTERISK-18103

The issue was initially closed because it was marked against 1.6.2; but since it was a regression, that was a mistake.

We've re-opened the issue and we'll be looking into it as soon as we can, and we're on the record (http://lists.digium.com/pipermail/asterisk-users/2011-July/264758.html) for pushing a release to fix it, even though 1.6.2 is otherwise security-only.

Meanwhile, if anyone else is able to pin it down, and provide a patch, that'd speed things up.

Thanks for your assistance.

 

[jbh]

I got what seemed like the same issue a while back, firstly when trying to test a tagged release of Asterisk 1.8.4.1 - see the ninth post in this thread http://pbxinaflash.com/community/threads/polycom-tls-broken-in-asterisk-1-8-3-3.10431/?t=10431

I also subsequently had the same issue when either reloading from FreePBX or doing an amportal restart (I forget which) with the default purple 1.8.4.1 install. I had thought this might have been a sign of the hardware I was using for testing showing its age (a clunky old Dell Optiplex GX270) but now I'm not so sure. After a reinstall I have not yet seen this issue again, but this does raise a suspicion that it might not be restricted to the 1.6 branch.

 

[jbh]

Just for clarity - I am however unable to duplicate the problem now on the same hardware with another install, albeit updated to Asterisk 1.8.5.0. However many amportal restarts I do, I cannot make it misbehave.

 

[Bruce]

Yeah, seems like they fixed the issue for 1.8x 10 days ago but only tried fixing 1.6x after many complaints just today:

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

-Bruce

 

[wardmundy]

This bug was pretty easy to replicate. Apparently all you had to do was add an extension or restart Asterisk. And POOF! Keep in mind that this was supposed to have been the final release of Asterisk 1.6. So much for testing...

 

[Bruce]

That is a really nice puppy they have

1.6.2.20 is now released. Should simple update-source do now?

Thanks

 

[darmock]

yep just ensure the /etc/pbx/digiumsource.conf reflects the current version number


Tom