It looks like it's failing due to a source list file in sources.list.d:
Log snippet:
---------------------------------------------------------------------------------------------------------------------------------------------------
Code:
[33m====== [15:16:16] Preparation: Common list 3cxpbx.list found but it seems to be OK[39m
[33m====== [15:16:16] Preparation: Common list 3cxpbx-testing.list found but it seems to be OK[39m
[31m[15:16] Preparation: Found an uncommon source list in /etc/apt/sources.list.d/: zabbix.list - 0
[39m::FAIL::
[33m====== [15:16:16] Failed: Output of journalctl[39m
-- Logs begin at Tue 2021-06-29 12:38:24 CEST, end at Tue 2021-06-29 15:16:15 CEST. --
---------------------------------------------------------------------------------------------------------------------------------------------------
We can't guarantee that deleting or moving the file would get it resolved or cause other issues as it should not have been there in the first place.
Was this 3CX Instance deployed using the
3CX ISO? Have you perhaps installed 3rd party packages to this instance?
If this machine was not deployed using our guides, I recommend taking a backup and redeploying using the 3CX ISO rather than trying to "fix" whatever is preventing the upgrade now. This is mainly for future-proofing the deployment and making sure you are running a 3CX Supported configuration. Though you may manage to resolve this issue now, the 3CX configuration may carry over underlying configurations that are not meant to be there that may end up causing issues as has happened in this case.
Simply:
1. Take a backup
2. Move it away from the machine
3. If a VM or a different physical machine shut it down. (do not delete just yet)
4. Redeploy using the
3CX ISO and restore the backup during installation.
5. Make sure everything is in order and then attempt the upgrade again. (you may need to reconfigure your firewall if not using the same local IP)
6. If everything goes well and the instance upgrades successfully, you may proceed with deleting the old VM or wiping the installation. Do not boot it up while the new machine is running. If you do need to boot it up, make sure it does not have an internet connection.
Note: We'd of course recommend carrying out this task during out of office hours during which time downtime is tolerable.
Hope this helps!
