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

 

[Evolute IT]

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

Take a backup and spin a new VM with v18 directly. This is due to a component that's probably not available anymore for Deb10 so it refuses to install and upgrade. "Gss-ntlmssp" was used for Exchange sync I believe.

 

[jhn]

Thanks.

Let's wait and see what 3CX has to say about the "upgrade to v18" option getting removed from all v16 / deb 9 setups. We have just a few left, all of them don't have the in-place upgrade available at the moment.
I do believe it has been pulled back for good reason.

 

[jhn]

Quick update in case someone else stumbles upon this post.

Info provided by 3CX in support case:

"We are aware of an issue caused by the packages having unmet dependencies and are currently looking into this, in the meantime, we have removed the update from the management console.

Once we have resolved the issue we will re-enable the update. "

 

[c2y]

Clean install from v18 iso also wasn't working 12 hours ago
after reboot, instead of asking if i want to configure pbx via web interface or shell, it just boots to root login screen.

 

[ChrisC_3CX]

We'll be updating this thread accordingly once we have an update on this.


@c2y

Clean install from v18 iso also wasn't working 12 hours ago
after reboot, instead of asking if i want to configure pbx via web interface or shell, it just boots to root login screen.

This should not be related. Please download the very latest 3CX ISO again from the 3CX customer portal and try it again. Make absolutely sure that the machine has an internet connection during the whole process.

 

[IPMG]

I have some licences that I cannot renew currently because they are on V16.

Any updates on when updates will be available again

 

[ChrisC_3CX]

I have some licences that I cannot renew currently because they are on V16.

Any updates on when updates will be available again

Not yet but rest assured we'll update this thread as soon as we have something.

 

[TagleRock]

Does this mean that even new installs of version 18 will fail?

 

[ChrisC_3CX]

Does this mean that even new installs of version 18 will fail?

No, new deployments directly to v18 and Debian 10 should work just fine.

 

[amplisys]

I was not able to do a clean install of v18 either, it would reboot straight to the login prompt as opposed to the wizard.

A clean install of v16 works fine.

 

[Evolute IT]

I was not able to do a clean install of v18 either, it would reboot straight to the login prompt as opposed to the wizard.

A clean install of v16 works fine.

Make sure you used the most recent ISO. The previous one didn't support SecureBoot or UEFI correctly, which it now does.

 

[TagleRock]

I was not able to do a clean install of v18 either, it would reboot straight to the login prompt as opposed to the wizard.

A clean install of v16 works fine.

To share my experience I had downloaded an ISO called "debian-10.9.0_1c40016-amd64-netinst-3cx.iso". This seems to have just installed the stock Debian OS and no 3cx services, so the wizard didn't come up. I downloaded a version 18 iso from our partner portal this morning and used that and it worked normally. That would seem to reinforce what ConceptsWeb stated.

 

[Evolute IT]

To share my experience I had downloaded an ISO called "debian-10.9.0_1c40016-amd64-netinst-3cx.iso". This seems to have just installed the stock Debian OS and no 3cx services, so the wizard didn't come up. I downloaded a version 18 iso from our partner portal this morning and used that and it worked normally. That would seem to reinforce what ConceptsWeb stated.

Those ISOs (with a build number) were the Beta ones.

 

[DSXVOICE]

Not yet but rest assured we'll update this thread as soon as we have something.

Please let us know the anticipated timing on the fix. We have a number of V16 licenses to renew which won't happen until we are able to update the instances to V18.

 

[ChrisC_3CX]

Please let us know the anticipated timing on the fix. We have a number of V16 licenses to renew which won't happen until we are able to update the instances to V18.

This may very well be sorted today: https://www.3cx.com/community/threads/upgrade-to-v18-and-debian-10-buster.81956/post-406086

 

[Zuppke]

We had a similar issue with this package. We solved it by trying to install gss-ntlmssp by hand, this revealed a dependancy called libwbclient0 which couldn't be installed.

apt-get install gss-ntlmssp

We then checked the apt-cache

apt-cache policy libwbclient0

if there was a version available, this was the u2 version but wouldn't be installed.
3CX places a version pinning file in

/etc/apt/preferences.d

called 3cxpbx.

This file said it needs libwbclient0 specific version u1. Changing this to the correct version in the repo made the package install again.

I'm not sure if there are any changes to the package that interfere with 3CX, so far we haven't had any issues (mind you; on 1 PBX).

 

[ChrisC_3CX]

UPDATE: The V18 & OS upgrade should be now be available through the Management Console again for 3CX v16 running on Debian 9. Please let us know if you face any issues with it.

@Zuppke
I wouldn't recommend attempting to resolve this manually especially if the 3CX deployment is a fully 3CX Supported configuration as we will not be able to guarantee the 3CX PBX's integrity after performing such tasks.

 

[pivotal]

Thanks 3CX! The update to V18 on Debian worked fine for us. After the update, we were able to move forward with renewing our client's license.

We appreciate your hard work and quick turn around on this issue.

 

[Callinectes]

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.