Upgrade from 16.0.6.655 to 16.0.7.1078 from admin's console

[vasya_pupkin]

Yea, this trouble again, read some pages on this forum
" apt list --upgradable
Listing... Done
3cxpbx/testing,stable 16.0.8.16 amd64 [upgradable from: 16.0.6.655]
"
but
"apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
3cxpbx libpam-systemd
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded."

How to force update from Linux CLI without clean/fresh installation?

 

[NickD_3CX]

Hi!

What happens when you try to upgrade from the Management Console?
If it fails, do you get an email with an error?

 

[vasya_pupkin]

i wrote PM to you

 

[NickD_3CX]

So the screenshots you sent in the PM show that the upgrade from the Management Console just logs you out and does not upgrade.
I would have to make a guess that the reason might be the same as what you getting when running the command manually from CLI.

Before going any further, I want to point out that probably the fastest way to get this machine upgrade to v16.0.8.16 would be to:

1. Take Full Backup and download
2. Format host
3. Download V16 Debian 9 ISO.
4. Re-install V16 and restore backup.

This is what 3CX recommends.

Also at this point, make a Full Backup and download it to your local PC because any changes you may make from this point may cause the system to stop working, so you may have to do the above steps anyway.

If you do really want to troubleshoot further, could you tell me what you get prompted with when you run command apt update and then apt install 3cxpbx?

 

[vasya_pupkin]

sorry, forgot to say
we need 18 version for upgrade to Enterprise
Another words - i want to do several upgrades from and to 16 version (for example from 16.0.6.655 to 16.0.8.16 etc), and final upgrade to 18

second - it is production instance in cloud and we need CLI upgrade only if possible

 

[NickD_3CX]

Another words - i want to do several upgrades from and to 16 version (for example from 16.0.6.655 to 16.0.8.16 etc), and final upgrade to 18

Not being able to upgrade via the Management Console is not a common problem. If all your 3CX installs are having the same problem, then I am inclined to believe you might have done something not per the 3CX guides on all of them.

second - it is production instance in cloud and we need CLI upgrade only if possible

Then the recommendation when there is a problem and the 3CX is in the Cloud is exactly the same as the 4 steps I explained, with the difference that you should use the 3CX Configuration Wizard in the Customer Portal or the 3CX Marketplace images to deploy it again, instead of the ISO that I previously suggested.

This of course implies that you are using a supported/tested Hosted Platform:
https://www.3cx.com/partners/hosted-pbx-providers/


I asked though also what you get with the 2 commands. Did you try that?

 

[vasya_pupkin]

OK, what about version 18?
may be I have to fresh install (v18) https://downloads-global.3cx.com/downloads/debian10iso/debian-amd64-netinst-3cx.iso

What about compatibility between backup from version 16 and fresh install of 18?

 

[NickD_3CX]

OK, what about version 18?
may be I have to fresh install (v18) https://downloads-global.3cx.com/downloads/debian10iso/debian-amd64-netinst-3cx.iso

What about compatibility between backup from version 16 and fresh install of 18?

You can do this, but usually we recommend that the backup you take on V16, be from the last service pack of that major release, which in the case of V16 is U8/U8A.
You are currently on V16 U6.

To answer your question, V18 won't complain about importing a backup from V16 U6, it is just not as tested as restoring a V16 U8 backup.

If you want to be 100% safe, what you can do is:

1. Take a Full Backup from your V16 U6.
2. Shut down (not delete) you V16 U6 VM
3. Install V16 locally from the ISO on a VM that will install V16 U8A and restore the backup as part of the installation.
4. Make a new Backup from V16 U8A
5. Shut down the local installation.
6. Install a new V18 installation in your hosting provider and restore the V16 U8A backup.