Your 3CX Debian OS failed to update

[sonnyh1]

Hi,
Currently runnung:
Product Professional Annual
Version Number 18.0 Update 9 (Build 20)
Debian 10 Buster (AWS)

Update is showing:
Version 20 is now available. Before upgrading, take a full backup of 3CX and save it outside of the instance. This upgrade will also upgrade Debian from 10 to 12.

When I try to update I receive the following error:
Your 3CX Debian OS failed to update
3CX Phone System Management Console ID: 10012

Thoughts / suggestions?

 

[bitn2]

How much will it need to run the update successfully? Can it be changed back to its original 15GB after the update is completed?

You need at least 30GB HDD to install v20, (Sorry that i wrote in german before).

 

[Agathocles Prodromou]

[33m====== [16:01:18] Upgrade Result: *******************************************[39m
{
"result": "aborted",
"time": "24-07-2024 16:01:18",
"title": "Unable to determine the PostgreSQL cluster version",
"message": "The script was unable to determine PostgreSQL cluster version. This may be a result of postgresql misconfiguration or service problem."
}
[31m[16:01] aborted: Unable to determine the PostgreSQL cluster version - 0[39m

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

You have two options:

1. If you took a snapshot of the system/vm before initiating the upgrade (as recommended), revert to it, remove /etc/apt/sources.list.d/microsoft-prod.list and try upgrading again. (Skipping the step of restoring won't work).
   
   
2. Spawn a new V20 instance using the 3CX ISO and restore from backup.

The recommended way is (2), starting fresh.

 

[konosEP]

You have two options:

1. If you took a snapshot of the system/vm before initiating the upgrade (as recommended), revert to it, remove /etc/apt/sources.list.d/microsoft-prod.list and try upgrading again. (Skipping the step of restoring won't work).
   
   
2. Spawn a new V20 instance using the 3CX ISO and restore from backup.

The recommended way is (2), starting fresh.

We took a backup but no vm snapshot. That's alright though cause the update never happened. Either way, we're going to proceed with option number 2 (which is recommended).
@bitn2 Thank you for replying! We gave it 40GB! hopefully, it'll go smoothly. (No problem, that's what google translate is for haha)

 

[bitn2]

We took a backup but no vm snapshot. That's alright though cause the update never happened. Either way, we're going to proceed with option number 2 (which is recommended).
@bitn2 Thank you for replying! We gave it 40GB! hopefully, it'll go smoothly. (No problem, that's what google translate is for haha)

That sounds like a good idea and should work for you.

 

[mheathman]

To anyone that might find this useful:

I ran into this issue 10012 when trying to upgrade from 3CX to V20. As mentioned in this guide you're required to have 2 vCPU as a minimum. So, I snapshotted my Lightsail instance, then proceeded to create the new instance from the snapshot with 2vCPU. Logged into the console and kicked off the upgrade again.

Again, this failed. 10012. (starting to feel this is a generic "something isn't right in the pre-stage" type error)

Digging deeper, I reviewed /var/log/apt/term.log (apt-get terminal output) and discovered that due to a change in lightsail being on nvme from the older sda drive mounts, grub was prompting for user interaction causing the failure in 3cx. I ran apt-get manually, answered the question for grub's prompt, then re-ran the update from the console. This time it was successful.

Note: Update took about 20~25 minutes, so don't reboot your instance or you'll have to run "sudo apt-get install 3cxpbx" then "sudo 3CXStartServices" to repair the broken services, make sure you can either login to the new version or if failed, the old version. You can use "top" to monitor the various dpkg-deb, dpkg, apt-get, gzip processes that this update spawns and wait until you see the 3cx services fire back up. The instance should restart on it's own to complete the upgrade to 3CX.

Hope it helps!