Console login error after doing yum update sangoma-pbx.noarch 0:1712-1.sng7

Can reproduce.

I do a fresh install of the SNG7-FPBX-64bit-1710-1.iso installation.

I let the system reboot after the installation.

I can login via the console or SSH to the machine as root.

I do a yum update sangoma-pbx and the sangoma-pbx.noarch 0:1712-1.sng7 package is installed.

Now if I login via the console or ssh to the machine, I get logged in… I see:

the FreePBX text splash screen with:

Current Network Configuration
. ip address, mac address, etc… normal stuff…
but then the connection to the machine closes with no errors…

Connection to closed.

happens if I ssh in or of If I use the console.

  • jack

On my error above… I expected the error since it has been 100% reproducable over the last 2 days of doing this install, so I left a logged in session going. In there I did:
yum history list
yum history info X ( where X was the # of the latest entry )
yum history undo X ( where X was the # of the latest entry )
and I got:

Loaded plugins: fastestmirror, versionlock
Undoing transaction 7, from Thu Dec 7 19:37:38 2017
Updated sangoma-pbx-1710-1.sng7.noarch @anaconda/1710
Update 1712-1.sng7.noarch @sng-pkgs
Loading mirror speeds from cached hostfile
Resolving Dependencies
–> Running transaction check
—> Package sangoma-pbx.noarch 0:1710-1.sng7 will be a downgrade
—> Package sangoma-pbx.noarch 0:1712-1.sng7 will be erased
–> Finished Dependency Resolution

Dependencies Resolved

Package Arch Version Repository Size

sangoma-pbx noarch 1710-1.sng7 sng-pkgs 11 k

Transaction Summary

Downgrade 1 Package

Total download size: 11 k
Is this ok [y/d/N]: y
Downloading packages:
sangoma-pbx-1710-1.sng7.noarch.rpm | 11 kB 00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : sangoma-pbx-1710-1.sng7.noarch 1/2
Redirecting to /bin/systemctl restart httpd.service
Machine not activated. No Sysadmin services available.
Cleanup : sangoma-pbx-1712-1.sng7.noarch 2/2
Verifying : sangoma-pbx-1710-1.sng7.noarch 1/2
Verifying : sangoma-pbx-1712-1.sng7.noarch 2/2

sangoma-pbx.noarch 0:1712-1.sng7

sangoma-pbx.noarch 0:1710-1.sng7


after this… I can login to the console from the terminal and ssh again successfully.

  • jack

I just tested and it works fine for me and I have sangoma-pbx-1712-1.sng7.noarch