sarcasm?
No, I am just not a particular believer in ‘coincidences’ being unrelated.
Did you check your memory’s integrity yet ? It would be one thing to check off the list .
can’t… see post above
Boot a “recovery iso” that can bypass uefi perhaps ? (it might be a bios thing needed . . .)
at this point I’m installing the ISO on a usb stick and I’m going to reload from scratch and restore a backup.
1 Like
On fresh installs, I always add a ‘root kit’ detector as soon as possible, you never know . . .
I had this exact same issue today, however on another platform. My client is running FreePBX 15 on Sangoma Linux 7 and this morning I got the call the phones were down. The only way I could get the PBX back online was to run yum erase asterisk16-res_digium_phone which disabled the DPMA module. When I tried to re-install the module, asterisk again started to crash every few seconds with the same segfault error. Thankfully I am able run this PBX without the Digium Module and failing finding a solution, I may have to do a fresh install as well.
Thank you for informing us about the downgrade. This resolved the issue on my PBX as well. From an uninstalled state, I ran yum install asterisk16-res_digium_phone which installed version 3.6.5.1 and then without an asterisk restart I immediately ran yum downgrade asterisk16-res_digium_phone which installed version 3.6.3.2 then finally ran fwconsole reload
This restored the Digium Module to a good working state with no segfault crashes.
Seeing the same issue here on a Asterisk 13 system.
On Monday evening (9/20), all packages were updated (fwconsole updateall and yum update):
—> Package asterisk13-res_digium_phone.x86_64 0:3.6.3-2.sng7 will be updated
—> Package asterisk13-res_digium_phone.x86_64 0:3.6.5-1.sng7 will be an update
Starting this morning, roughly 32 hours after upgrade, we started seeing problems, and I can see asterisk crashes when I see DPMA messages in the console. Looking back at monitoring, I can see this was a problem since the upgrade.
Downgrading res_digium_phone seems to have solved the issue.
yum downgrade asterisk13-res_digium_phone
—> Package asterisk13-res_digium_phone.x86_64 0:3.6.3-2.sng7 will be a downgrade
—> Package asterisk13-res_digium_phone.x86_64 0:3.6.5-1.sng7 will be erased
I then had to restart the system as I couldn’t get asterisk to restart cleanly.
The good news is they finally have a fix for this: https://issues.freepbx.org/browse/FREEPBX-22835
https://wiki.freepbx.org/display/FPG/Endpoint+Manager+Vs+FreePBX+Digium+Phone+Module
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
Not sure if it makes sense to post this here given it concerns PBXACt, but my situation seems similar?
I have tried a yum erase asterisk13-res_digium_phone.x86_64 0:3.6.5-1.sng7 and then a yum install asterisk13-res_digium_phone.x86_64 0:3.6.5-1.sng7
The requests completed fine - and while the digium phone app is erased, the system works but as soon as it’s present, asterisk just keeps restarting…
Thank you! and sorry if not relevant…
“Do a asterisk-version-switch to asterisk 16 then load the asterisk16-res_digium_phone_public package.”
My notes about a similar issue that I had on a older system.
EDIT:
Just noticed this is for a PBXACt system. I don’t know how relevant this post is any more.
Asterisk 16 has gone end of life since the original posting.
Eh just regurgitating what my notes from forever ago said. 