v16 Debian 9 to v18 Debian 10 upgrade failing

[jhn]

Hello,
we attempted to update self-hosted 3cx v16 (deb 9) to v18 (deb 10).
Upgrade failed, following info is available in upgrade log:

....
Purging configuration files for postgresql-9.6 (9.6.15-0+deb9u1) ...
W: --force-yes is deprecated, use one of the options starting with --allow instead.
[33m====== [17:22:14] Post-Upgrade: PostgreSQL - Starting new PostgreSQL[39m
[33m====== [17:22:16] Post-Upgrade: PostgreSQL - Waiting 30 seconds to settle[39m
[33m====== [17:22:46] Post-Upgrade: PostgreSQL - Reindexing new database[39m
reindexdb: reindexing database "database_single"
reindexdb: reindexing database "masterprofiles"
reindexdb: reindexing database "postgres"
reindexdb: reindexing database "template1"
[33m====== [17:23:12] Post-Upgrade: Installing latest 3cxpbx package for Debian 10 (v18)[39m
> Execute apt command simulation on "install 3cxpbx"
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
3cxpbx : Depends: gss-ntlmssp but it is not going to be installed
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: Unable to correct problems, you have held broken packages.
> Simulation failed (install 3cxpbx)
...

After restoring VM snapshot and reverting back to pre-upgrade status, v16 is back in business and all works ok.
However, update to v18 is not available anymore (dashboard - updates)...
This is the same for the last few non-upgraded v16 installations we are running - v18 upgrade option is not available anymore.

Is this situation similar to what happened ca month / month and half ago when v18 upgrade was disabled temporarily due to issues which needed to be addressed?

Thank you,
Jakub

 

[NickD_3CX]

Still seeing the following in error log on one server when trying to update from 18.0.1.237 to 18.0.2.302:

Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 http://downloads-global.3cx.com/downloads/debian buster-testing InRelease
Hit:5 http://downloads-global.3cx.com/downloads/debian buster InRelease
Reading package lists...
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Rollback to 18.0.1.237...
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

I updated another machine without any problems.

This is unrelated with the original thread topic. You are already on V18 and Deb 10.

Anyway, I would suggest trying to Reboot the server, then try again.

If that fails, then:

1. Important! Make a full backup and download it to your desktop
2. Log in with SSH and run the command it tells you: sudo dpkg --configure -a
   Note: there is a chance that this will completely uninstall 3CX
3. If after running the command, 3CX is still accessible, try again. if not, delete the machine and redeploy it from the beginning and restore the backup from step #1.

 

[Callinectes]

This is unrelated with the original thread topic. You are already on V18 and Deb 10.

Anyway, I would suggest trying to Reboot the server, then try again.

If that fails, then:

1. Important! Make a full backup and download it to your desktop
2. Log in with SSH and run the command it tells you: sudo dpkg --configure -a
   Note: there is a chance that this will completely uninstall 3CX
3. If after running the command, 3CX is still accessible, try again. if not, delete the machine and redeploy it from the beginning and restore the backup from step #1.

Nick,

Unfortunately I had to recover from a backup. Not a big deal but odd that this one machine had this issue when no others did. It was installed from the 3CX debian ISO.

It is up and running now. Thanks for the assistance.