my Freepbx is v14.1… A message from the server to update modules.
The Sysadmin upgrade was required. Instead of clicking the “purchase” button, I clicked the upgrade. Now the sysadmin modules is disabled (Disabled; Pending Upgrade to 14.0.11). It won’t let me do anything recover the error. Only options available from the module manage, “Upgrade to 14.0.11 and Enable” and “Uninstall”. Clicked the “upgrade…” the server gets an error and hangs the GUI. It’s won’t let me uninstall the module.
[[email protected] ~]# yum install sangoma-pbx
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
–> Running transaction check
—> Package sangoma-pbx.noarch 0:1801-3.sng7 will be installed
–> Processing Dependency: kmod-forcedeth for package: sangoma-pbx-1801-3.sng7.noarch
–> Running transaction check
—> Package kmod-forcedeth.x86_64 0:0.64-4.sng7 will be installed
–> Finished Dependency Resolution
Package Arch Version Repository Size
sangoma-pbx noarch 1801-3.sng7 sng-pkgs 16 k
Installing for dependencies:
kmod-forcedeth x86_64 0.64-4.sng7 sng-pkgs 45 k
Install 1 Package (+1 Dependent package)
Total download size: 61 k
Installed size: 140 k
Is this ok [y/d/N]: y
(1/2): sangoma-pbx-1801-3.sng7.noarch.rpm | 16 kB 00:00
(2/2): kmod-forcedeth-0.64-4.sng7.x86_64.rpm | 45 kB 00:01
Total 50 kB/s | 61 kB 00:01
Running transaction check
Running transaction test
Transaction test succeeded
Installing : kmod-forcedeth-0.64-4.sng7.x86_64 1/2
Working. This may take some time …
Installing : sangoma-pbx-1801-3.sng7.noarch 2/2
warning: /etc/schmooze/pbx-brand created as /etc/schmooze/pbx-brand.rpmnew
Redirecting to /bin/systemctl restart httpd.service
Redirecting to /bin/systemctl restart xinetd.service
Machine not eligible for ftp configuration.
Verifying : kmod-forcedeth-0.64-4.sng7.x86_64 1/2
Verifying : sangoma-pbx-1801-3.sng7.noarch 2/2
I have no idea how that managed to be deleted - it is, in fact, a protected RPM, you shouldn’t be able to delete it at all. What’s the history of this machine? Did you install it from 6 and then upgrade? Or was it installed as 7 from an ISO (and if, so, do you know which ISO?)
It would be SUPER handy if you could run this command and send me a PM with the output:
I did exactly as mentioned at the beginning of my post. It’s definitely a bug in the software. I installed the freepbx from the Sangome download site (SNG7-FPBX-64bit-1707-1). It’s a vanilla installation on a Hyper-v server.
That is quite an old ISO, and because of a couple of reports of people accidentally removing sangoma-pbx, I protected that specific package in 1711-1.
If you had typed ‘yum remove nodejs’ (or any one of 15 other RPMs that you thought you didn’t need) it would have removed that RPM, and almost nothing would have broken, until 6 months later - now - when we’re sure that everyone has upgraded, we can start relying on that RPM existing, and… whoops, you were one of the ones that deleted it, and didn’t notice.
Just install it, and everything will be fine.
yum install sangoma-pbx
If it errors, you might need to rm -rf /etc/sangoma and then try the install again.
I recalled recently I had trouble updating the system update. I had to comment out sangoma-pbx in the /etc/yum/protected.d/sngoma-pbx.conf in order to perform the update. The system update must have erased the /etc/sangoma directory