Upgrading to V18 from a Debian 9 / V16 cloud server

[caseyswoods]

I installed V16 on a self managed Debian 9 server that I have running in a cloud environment. It is now running V 16.0.8.16.

I'm being given the option in the 3CX web dashboard of upgrading to "Version 18 (Includes OS upgrade from Debian 9 to 10)". I'm wondering if this is wise?

I'm tempted to do the following:

1. Create a backup of my existing V16 installation
2. Create a new Debian 10 server
3. Install V18 on the new server
4. Fire up 3CX and restore from my V16 backup

Will this work? Or should I try clicking the "Version 18 (Includes OS upgrade from Debian 9 to 10)" button and holding my breath?

 

[NickD_3CX]

Hi!

First of all, I need to mention that the only supported/tested 3CX Linux deployment is if you have deployed via:

• 3CX ISO
• Customers Portal Deployment Wizard
• 3CX Marketplace Images

If you have installed via any of the above methods, you should be fine.

Moving onto my suggestion:

1. Make a Full 3CX Backup and download it to your local computer
2. Press the Upgrade button from within the 3CX Management Console and allow up to an hour.
3. If for whatever reason the upgrade fails, you can always fall back to doing what you suggested.

 

[videojedi]

Hi,
I installed two systems via, the 'express' method to google cloud. I am offered the option of upgrading to v18 and debian 10, but both instances fail with the same error- related to the debian update.

Should I be able to upgrade?

Thanks

 

[NickD_3CX]

It may be a small problem with the repositories Google adds to each of their VMs.

Can you log into both instances via SSH and run the command apt update and copy-paste the output here?

 

[videojedi]

hi, here is the output...

:~$ sudo apt update

Get:1 http://security.debian.org stretch/updates InRelease [53.0 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://downloads-global.3cx.com/downloads/debian stretch-testing InRelease
Get:4 http://deb.debian.org/debian stretch-updates InRelease [93.6 kB]
Hit:5 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Get:6 http://deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Get:7 http://deb.debian.org/debian stretch Release [118 kB]
Get:8 http://deb.debian.org/debian stretch Release.gpg [3,177 B]
Get:9 http://security.debian.org stretch/updates/main Sources [407 kB]
Get:10 http://security.debian.org stretch/updates/main amd64 Packages [771 kB]
Get:11 http://security.debian.org stretch/updates/main Translation-en [362 kB]
Get:12 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease [6,785 B]
Get:13 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease [5,525 B]
Err:6 http://deb.debian.org/debian stretch-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
Err:12 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEB
Err:13 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEB
Get:14 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease [5,555 B]
Err:14 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEB
Fetched 1,918 kB in 1s (1,640 kB/s)Reading package lists...
Done
Building dependency tree
Reading state information...
Done
105 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: http://deb.debian.org/debian stretch-backports InRelease:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9W:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEBW:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: http://packages.cloud.google.com/apt google-compute-engine-stretch-stable
InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEBW:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch
InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEBW:
Failed to fetch http://deb.debian.org/debian/dists/stretch-backports/InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9W:
Failed to fetch http://packages.cloud.google.com/apt/dists/cloud-sdk-stretch/InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEBW:
Failed to fetch http://packages.cloud.google.com/apt/dists/google-compute-engine-stretch-stable/InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEBW:
Failed to fetch http://packages.cloud.google.com/apt/dists/google-cloud-packages-archive-keyring-stretch/InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEBW:
Some index files failed to download. They have been ignored, or old ones used instead.

 

[NickD_3CX]

It's what I suspected, the recommended solution, as well as what is causing this, is described here:
https://www.3cx.com/community/threa...ade-from-9-to-10-gcp-hosted.87046/post-411143

 

[videojedi]

It's what I suspected, the recommended solution, as well as what is causing this, is described here:
https://www.3cx.com/community/threa...ade-from-9-to-10-gcp-hosted.87046/post-411143

Thanks very much, I will give it a go and report back.

Cheers

 

[videojedi]

Sadly, it didn't work. But the re-install from the portal was pretty quick, so back up and running again on v18.

Just one word of caution. I had made a backup before trying the above. Somehow, the instance got totally screwed and wouldn't reboot. But then when I tried to upload the backup during the portal reinstall process, it would seem my config didn't have an email address assigned to the operator extension, so it wouldn't accept the backup. After a bit of searching I opened up the xml and changed the Operator number to an extension that did contain a valid email address. However, the process of opening and saving the zip file, corrupted it. The portal said 'invalid backup'.
Eventually I opened just the xml file in winzip, and saved it. This upload was sucessful and the re-install proceeded as expected.

To anyone reading this.... just make sure your config has an email address assigned to the operator extension, and you can avoid the heart stopping moment of seeing your backup fail to restore.


I'll be doing the same again tonight on a second install...