3CX v18 Update Failed

[Ahmed Mahdy]

Hey Peeps,

we have a scheduled 3cx system update running every Tuesday.

one of our customers (just got updated to v18 and already we have another related issue in the following link (https://www.3cx.com/community/threads/3cx-call-log-error-after-v18-upgrade.85530/#post-402063) is having an issue while having the PBX updated every week.

the current version shown on the dashboard is 18.0 (build 1880) although the mail (with the update.log file attached) we receive from PBX states that the current version is 18.0.1.237

we are facing this issue with one customer till now out of around 3 who got upgraded already from v16 to v18 recently.

Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:2 http://downloads-global.3cx.com/downloads/debian buster-testing InRelease
Hit:3 http://downloads-global.3cx.com/downloads/debian buster InRelease
Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [308 kB]
Hit:5 http://deb.debian.org/debian buster InRelease
Get:6 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:7 http://deb.debian.org/debian buster-updates/main amd64 Packages.diff/Index [9100 B]
Get:8 http://deb.debian.org/debian buster-updates/main amd64 Packages 2021-10-26-2004.40.pdiff [283 B]
Get:8 http://deb.debian.org/debian buster-updates/main amd64 Packages 2021-10-26-2004.40.pdiff [283 B]
Fetched 435 kB in 3s (170 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
3cxpbx is already the newest version (18.0.1.237).
The following packages were automatically installed and are no longer required:
libip6tc0 libiptc0 libnetfilter-conntrack3 libnfnetlink0
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
W: --force-yes is deprecated, use one of the options starting with --allow instead.

Did anyone face an issue like this before

thanks and cheers

 

[VasilisV_3CX]

Hi @Ahmed Mahdy,

As mentioned in: https://www.3cx.com/community/threads/3cx-call-log-error-after-v18-upgrade.85530/#post-402063, I suggest reinstallation using our 3CX ISO, after backing up your PBX.

 

[gadgetman99]

So if 3CX spun up the instance in a self hosted Google cloud and we are forced to upgrade to V18 but the upgrade does not work because of an issue with forcing us to move to a new version of Debian 3CXs official recommendation is to reinstall using an ISO and restore from backup? With as many failed upgrades that are filling the forum I would expect any self respecting company that is forcing its customers to upgrade would have 1.) support during the upgrade for all current customers, because what I am seeing in the forums is not support it is reinstall and restore from backup as the default answer to an internal issue with 3CX. 2.) Better internal code QA prior to upgrade so that base installations of 3CX spun up by 3CX not by the customer actually worked. And a decent set of documents outlining what is supported (as far as apps) and what is not. 3CX has gone downhill and acts like a company that hates its customers.

 

[VasilisV_3CX]

Hi @gadgetman99,

To clear something up here that you said:

With as many failed upgrades that are filling the forum I would expect any self respecting company that is forcing its customers to upgrade would have

What you're seeing here, is statistically under 0.1% of our total installations. It's actually a very rare thing for our upgrade process to fail.

3CXs official recommendation is to reinstall using an ISO and restore from backup?

Now if you're unlucky enough to fall into the 0.1%, then yes, this is our recommendation.