Update from 18 update 9 (31) to 20 Failed

[Sergey Yezhov]

Hello,
we want to upgrade our on-premise server to 20 version, but there is some troubles (Err:5 http://repo.3cx.com/debian/1809 bullseye Release
404 Not Found [IP: 172.64.147.129 80]) , please help if you can, there is log which i recieve on mail as error of update:

--2024-05-21 17:08:12--  https://downloads.3cx.com/downloads/misc/debian10to12/update.sh

Resolving downloads.3cx.com (downloads.3cx.com)... 172.64.147.129, 104.18.40.127, 2606:4700:4400::ac40:9381, ...

Connecting to downloads.3cx.com (downloads.3cx.com)|172.64.147.129|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 47260 (46K) [application/x-sh]

Saving to: ‘/tmp/update.sh’



     0K .......... .......... .......... .......... ......    100% 2.52M=0.02s



2024-05-21 17:08:16 (2.52 MB/s) - ‘/tmp/update.sh’ saved [47260/47260]



[33m====== [17:08:18] Preparation: Script path is /tmp/update.sh[39m

[33m====== [17:08:19] Starting: Backup script /tmp/update.sh[39m

[33m====== [17:08:19] Starting: Backup script version: 6129c6b15db886fbb9f9f47a58e7a046225005720255f565080145f34d802b33[39m

[33m====== [17:08:19] Starting: Current directory: /tmp[39m

[33m====== [17:08:19] Starting: Current user: root[39m

[33m====== [17:08:19] Starting: Current date: Tue 21 May 2024 05:08:19 PM +04[39m

[33m====== [17:08:19] Starting: Current version: 11[39m

[33m====== [17:08:19] Starting: Architecture: amd64[39m

[33m====== [17:08:19] Starting: Hostname: 3cx[39m

[33m====== [17:08:19] Starting: Hypervisor: vmware[39m

> Execute apt command simulation on "update"

> Execute apt command on "update"

Ign:1 http://repo.3cx.com/debian/1809 bullseye InRelease

Ign:2 http://repo.3cx.com/debian-security/1809 bullseye-security InRelease

Hit:3 http://repo.3cx.com/3cx buster-testing InRelease

Hit:4 http://repo.3cx.com/3cx buster InRelease

Err:5 http://repo.3cx.com/debian/1809 bullseye Release

  404  Not Found [IP: 172.64.147.129 80]

Err:6 http://repo.3cx.com/debian-security/1809 bullseye-security Release

  404  Not Found [IP: 172.64.147.129 80]

Reading package lists...

E: The repository 'http://repo.3cx.com/debian/1809 bullseye Release' does not have a Release file.

E: The repository 'http://repo.3cx.com/debian-security/1809 bullseye-security Release' does not have a Release file.

[33m====== [17:08:29] Upgrade Result: *******************************************[39m

{

  "result": "Upgrade",

  "time": "21-05-2024 17:08:29",

  "title": "Package Update Failed",

  "message": "An error occurred while upgrading package: update"

}

[31m[17:08] Upgrade: Package Update Failed - 0[39m

 

[Agathocles Prodromou]

Hi,

In the APT sources, replace bullseye with buster (also remove “-security”) and try upgrading again to see if that works (if you know how to do it that is). Make sure you take a backup/snapshot of your system before taking any action.

Otherwise, take a full 3CX backup, spawn a new machine from our Debian 12 ISO and restore it. It will probably take less time and you start fresh.

 

[Sergey Yezhov]

Hello again "buster" is helped but another issue:
[33m====== [22:43:45] Preparation: Fetch postgresql cluster: 13 main 5432 online postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log[39m
[33m====== [22:43:48] Preparation: Could not get postgresql cluster version from the settings database. Got: 13. Trying from pg_lsclusters result...[39m
[33m====== [22:43:48] Preparation: Unable to determine postgresql cluster version. Got: 13. Aborting...[39m
[33m====== [22:43:49] Upgrade Result: *******************************************[39m
{
"result": "aborted",
"time": "21-05-2024 22:43:48",
"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[22:43] aborted: Unable to determine the PostgreSQL cluster version - 0[39m


i think clean install with restore best practice... is there can be some troubles when restoring from 18 version to 20?

 

[Agathocles Prodromou]

Hi,

Yes the best option (and recommended way) is to start clean by deploying our Debian 12 ISO and restoring from a backup.

Prior upgrading, please go over this V20 Upgrade Checklist: https://www.3cx.com/blog/releases/v20-upgrade-checklist-faq/ (mostly Steps 1-7)

To add to that:
- If you have Scheduled reports they need to be re-done
- DTMF IVR is not available

 

[Sergey Yezhov]

hello,

last question DTMF IVR will NOT be available or will be available later in updates??

 

[Agathocles Prodromou]

It won't be available, however you can use the Call Processing Scripts feature of V20 as a replacement.