Upgrade from v18.0.9 to V20 failed

[aangeles]

Trying to upgrade the 3CX Phone system v18.0.9 to the latest version 20 hosted in Azure with a valid license until November 2025.
According to the system alert logs, "not enough CPU resources", we try to increase it to 8vCPU, which is above the required 2CPU cores.


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

Hit:1 http://repo.3cx.com/debian/1809 buster InRelease
Hit:2 http://repo.3cx.com/debian-security/1809 buster InRelease
Hit:3 http://repo.3cx.com/3cx buster-testing InRelease
Hit:4 http://repo.3cx.com/3cx buster InRelease
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
[33m====== [17:23:40] Preparation: Not enough CPU cores. At least 2 CPU cores are required for a smooth upgrade.[39m
[33m====== [17:23:40] Upgrade Result: *******************************************[39m
{
"result": "aborted",
"time": "28-07-2025 17:23:40",
"title": "Insufficient CPU cores",
"message": "There are not enough CPU cores. Please make sure there are at least 2 CPU cores before upgrading."
}
::FAIL::


Any input on this issue?

 

[KyriacosS_3CX]

Hi,

Can you run
cat /proc/cpuinfo | less

so we can see how many CPUs/cores the operating system sees?

Best,
KS.

 

[KyriacosS_3CX]

And should have asked, did you reboot the VM after resizing?

 

[aangeles]

Hi KyriacosS_3CX,

Good day, and thank you for your response.
I tried your suggestion to run the command "cat /proc/cpuinfo | less" on the terminal of 3CX Console, but the command is not allowed.

On the reboot/restart,
Yes, I was able to reboot the 3CX via Terminal on the 3CX Dashboard and even request that the Admin who handles the Azure instance of 3CX reboot the systems after adjusting the resources.

 

[KyriacosS_3CX]

I suggest that, unless somebody with similar experience chimes in, open a ticket as it is quite a specialized error you are getting here.

 

[AC_IT]

Hi @aangeles I hope you are well!

Strange that despite increasing the vCPU count, the upgrade process believes you have less than the 2vCPU requirement. Using the "Terminal" within the 3CX Admin Console gives a restricted amount of commands to be able to use - have you tried asking your Azure VM admin to connect directly to the VM and run the commands from there to confirm it can see the increased amount of vCPUs?

Alternatively, have you considered deploying a new V20 instance from your V18 backup? Obviously I do not know your IT setup and the feasibility for your IT team to do this, but it may be a quicker approach than trying to ascertain the issue here and allows you to proceed with the migration to a V20 instance.