3CX broken after forced Debian 9 upgrade

[jakorsme]

My 3CX iphone app would just crash on launch.

A updated 3CX client app appeared in iphone App Store. I installed it.

It came up on the phone alright, but said it had disabled all incoming calls until I upgraded 3CX (what????)

Since 3CX is already current, I figure it must be requiring the Debian 8 to Debian 9 upgrade the 3CX console keeps nagging about displaying a notice to do.

So I follow the doc to upgrade from debian 8 to 9.

The Debian upgrade goes fine and the server is up on debian 9.

However 3cx services never start and I have no idea why.

Now I'm without a phone system and thinking I'm going to have to lose my existing 3CX configured system and start all over with a new 3CX. I just don't have time for that.

 

[Saqqara]

the latest ver 16 only worked on Debian 9 , not Debian 8.

do you know what version you where running ? Version 15 worked on Debian 8

do you have a valid backup, if so you maybe able to restore the system using this backup. using the Debian iso image, and within the wizard select restore from backup https://www.3cx.com/docs/upgrading-pbx-v16/

 

[SteveITS]

It came up on the phone alright, but said it had disabled all incoming calls until I upgraded 3CX (what????)

FWIW:
https://www.3cx.com/blog/releases/remote-working-video-app/
https://www.3cx.com/blog/releases/new-ios-app-swift/
https://www.3cx.com/blog/releases/apple-push-update-windows/

 

[jakorsme]

the latest ver 16 only worked on Debian 9 , not Debian 8.

do you know what version you where running ? Version 15 worked on Debian 8

do you have a valid backup, if so you maybe able to restore the system using this backup. using the Debian iso image, and within the wizard select restore from backup https://www.3cx.com/docs/upgrading-pbx-v16/

No backup, I didn't expect an os upgrade to kill an application. But it is what it is.

I thought I was on 16, but logs are saying 15.5.

I just ran - /sbin/3CXStartServices and it seemed to create a bunch of service related files. Now the 3CX Management Console login screen comes up but I get a red "Server Error". 3CX Web Client also comes up, but I get a "502 - OK" error (both upon trying to login.

 

[jakorsme]

root@3CX:~# systemctl start 3CXPhoneSystemMC01


Job for 3CXPhoneSystemMC01.service failed because a timeout was exceeded.


See "systemctl status 3CXPhoneSystemMC01.service" and "journalctl -xe" for details.


root@3CX:~# sudo 3CXStopServices && 3CXStartServices


Created symlink /etc/systemd/system/3CXEventNotificationManager.service → /lib/systemd/system/3CXEventNotificationManager.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXEventNotificationManager.service → /lib/systemd/system/3CXEventNotificationManager.service.


Created symlink /etc/systemd/system/3CXCfgServ01.service → /lib/systemd/system/3CXCfgServ01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXCfgServ01.service → /lib/systemd/system/3CXCfgServ01.service.


Created symlink /etc/systemd/system/3CXMediaServer.service → /lib/systemd/system/3CXMediaServer.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXMediaServer.service → /lib/systemd/system/3CXMediaServer.service.


Created symlink /etc/systemd/system/3CXPhoneSystemMC01.service → /lib/systemd/system/3CXPhoneSystemMC01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXPhoneSystemMC01.service → /lib/systemd/system/3CXPhoneSystemMC01.service.


Created symlink /etc/systemd/system/3CXPhoneSystem01.service → /lib/systemd/system/3CXPhoneSystem01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXPhoneSystem01.service → /lib/systemd/system/3CXPhoneSystem01.service.


Created symlink /etc/systemd/system/3CXIVR01.service → /lib/systemd/system/3CXIVR01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXIVR01.service → /lib/systemd/system/3CXIVR01.service.


Created symlink /etc/systemd/system/3CXQueueManager01.service → /lib/systemd/system/3CXQueueManager01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXQueueManager01.service → /lib/systemd/system/3CXQueueManager01.service.


Created symlink /etc/systemd/system/3CXCallFlow01.service → /lib/systemd/system/3CXCallFlow01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXCallFlow01.service → /lib/systemd/system/3CXCallFlow01.service.


Created symlink /etc/systemd/system/3CXSystemService01.service → /lib/systemd/system/3CXSystemService01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXSystemService01.service → /lib/systemd/system/3CXSystemService01.service.


Created symlink /etc/systemd/system/3CXTunnel01.service → /lib/systemd/system/3CXTunnel01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXTunnel01.service → /lib/systemd/system/3CXTunnel01.service.


Created symlink /etc/systemd/system/3CXAudioProvider01.service → /lib/systemd/system/3CXAudioProvider01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXAudioProvider01.service → /lib/systemd/system/3CXAudioProvider01.service.


Created symlink /etc/systemd/system/3CXHotelModule01.service → /lib/systemd/system/3CXHotelModule01.service.


Created symlink /etc/systemd/system/multi-user.target.wants/3CXHotelModule01.service → /lib/systemd/system/3CXHotelModule01.service.


Job for 3CXPhoneSystemMC01.service failed because a timeout was exceeded.


See "systemctl status 3CXPhoneSystemMC01.service" and "journalctl -xe" for details.


Job for 3CXQueueManager01.service failed because a timeout was exceeded.


See "systemctl status 3CXQueueManager01.service" and "journalctl -xe" for details.


Job for 3CXCallFlow01.service failed because a timeout was exceeded.


See "systemctl status 3CXCallFlow01.service" and "journalctl -xe" for details.


Job for 3CXSystemService01.service failed because a timeout was exceeded.


See "systemctl status 3CXSystemService01.service" and "journalctl -xe" for details.


root@3CX:~#


root@3CX:~#


root@3CX:~# journalctl -xe


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: Main process exited, code=killed, status=9/KILL


Jun 11 19:28:50 3CX systemd[1]: Failed to start 3CX PhoneSystem 01 CallFlow Server.


-- Subject: Unit 3CXCallFlow01.service has failed


-- Defined-By: systemd


-- Support: https://www.debian.org/support


--


-- Unit 3CXCallFlow01.service has failed.


--


-- The result is failed.


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: Unit entered failed state.


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: Failed with result 'timeout'.


Jun 11 19:29:05 3CX systemd[1]: 3CXSystemService01.service: State 'stop-final-sigterm' timed out. Killing.


Jun 11 19:29:05 3CX systemd[1]: 3CXSystemService01.service: Killing process 8017 (3cxSystemServic) with signal SIGKILL.


Jun 11 19:29:05 3CX systemd[1]: 3CXSystemService01.service: Main process exited, code=killed, status=9/KILL


Jun 11 19:29:05 3CX systemd[1]: Failed to start 3CX PhoneSystem 01 System Server.


-- Subject: Unit 3CXSystemService01.service has failed


-- Defined-By: systemd


-- Support: https://www.debian.org/support


--


-- Unit 3CXSystemService01.service has failed.


--


-- The result is failed.


Jun 11 19:29:05 3CX systemd[1]: 3CXSystemService01.service: Unit entered failed state.


Jun 11 19:29:05 3CX systemd[1]: 3CXSystemService01.service: Failed with result 'timeout'.


root@3CX:~# systemctl status 3CXCallFlow01.service


● 3CXCallFlow01.service - 3CX PhoneSystem 01 CallFlow Server


Loaded: loaded (/lib/systemd/system/3CXCallFlow01.service; enabled; vendor preset: enabled)


Active: failed (Result: timeout) since Thu 2020-06-11 19:28:50 PDT; 1min 40s ago


Process: 8230 ExecStart=/usr/lib/3cxpbx/3CXCallFlow -p /var/run/phonesystem/3CXCallFlow01.pid /var/lib/3cxpbx/Bin/config.json (code=k


Main PID: 8230 (code=killed, signal=KILL)





Jun 11 19:27:05 3CX systemd[1]: Starting 3CX PhoneSystem 01 CallFlow Server...


Jun 11 19:28:35 3CX systemd[1]: 3CXCallFlow01.service: Start operation timed out. Terminating.


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: State 'stop-final-sigterm' timed out. Killing.


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: Killing process 8230 (3CXCallFlow) with signal SIGKILL.


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: Main process exited, code=killed, status=9/KILL


Jun 11 19:28:50 3CX systemd[1]: Failed to start 3CX PhoneSystem 01 CallFlow Server.


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: Unit entered failed state.


Jun 11 19:28:50 3CX systemd[1]: 3CXCallFlow01.service: Failed with result 'timeout'.


root@3CX:~# sudo lsb_release -a


No LSB modules are available.


Distributor ID: Debian


Description: Debian GNU/Linux 9.12 (stretch)


Release: 9.12


Codename: stretch


root@3CX:~#

 

[jakorsme]

When doing apt-get upgrade


Updating from Version 15.5.15502.6


Loading global scripts...


Loading instance scripts...


Loading instances...


Npgsql.NpgsqlException (0x80004005): Exception while connecting


---> System.Net.Sockets.SocketException (111): Connection refused


at Npgsql.NpgsqlConnector.Connect(NpgsqlTimeout timeout)


at Npgsql.NpgsqlConnector.Connect(NpgsqlTimeout timeout)


at Npgsql.NpgsqlConnector.RawOpen(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)


at Npgsql.NpgsqlConnector.Open(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)


at Npgsql.NpgsqlConnection.<>c__DisplayClass32_0.<<Open>g__OpenLong|0>d.MoveNext()


--- End of stack trace from previous location where exception was thrown ---


at Npgsql.NpgsqlConnection.Open()


at Updater2Db.UpdateInfoExtractor.LoadInstances()


at Updater2Db.UpdateInfoExtractor.Init(Func`2 configRepository)


at UpdaterNx.Program.DoUpdate(String scriptFolder)


at UpdaterNx.Program.Main(String[] args)


dpkg: error processing package 3cxpbx (--configure):


subprocess installed post-installation script returned error exit status 1


Errors were encountered while processing:


3cxpbx


E: Sub-process /usr/bin/dpkg returned an error code (1)