Upgrade Debian 8 to 9 failed

[MpDay20]

Hi, I want to upgrade to Debian 9 because we want 3CX 16. When I use de Upgrade botton from the 3CX Updates page, I get an email after some minutes telling me the upgrade failed:

--2019-04-14 13:56:32--  https://downloads.3cx.com/downloads/misc/debian8to9/update.sh
Resolving downloads.3cx.com (downloads.3cx.com)... 151.80.125.73
Connecting to downloads.3cx.com (downloads.3cx.com)|151.80.125.73|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5862 (5.7K) [application/x-sh]
Saving to: ‘/tmp/update.sh’

     0K .....                                                 100%  236M=0s

2019-04-14 13:56:33 (236 MB/s) - ‘/tmp/update.sh’ saved [5862/5862]

dpkg-query: package 'google-cloud-sdk' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
########## Upgrade start time: 2019-04-14T11:56:33Z
########## Execute apt command simulation on "clean"
Del /var/cache/apt/archives/* /var/cache/apt/archives/partial/*
Del /var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin
########## Execute apt command on "clean"
########## Initiate 3CX backup

Progress: ~99.421%, 1202/1209 items processed
Progress: ~94.720%, 1202/1269 items processed
Progress: ~25.883%, 1202/4644 items processed
Progress: ~25.872%, 1202/4646 items processed
Progress: ~25.866%, 1202/4647 items processed
Progress: ~25.882%, 1203/4648 items processed
Progress: ~26.097%, 1213/4648 items processed
Progress: ~26.743%, 1243/4648 items processed
Progress: ~33.455%, 1555/4648 items processed
Progress: ~47.978%, 2230/4648 items processed
Progress: ~63.447%, 2949/4648 items processed
Progress: ~76.485%, 3555/4648 items processed
Progress: ~93.782%, 4359/4648 items processed
Progress: 100.000%, 4648/4648 items processed
DONE.
########## Execute apt command simulation on "update"
########## Execute apt command on "update"
Hit http://downloads.3cx.com jessie-testing InRelease
Hit http://downloads.3cx.com jessie InRelease
Ign http://httpredir.debian.org jessie InRelease
Hit http://security.debian.org jessie/updates InRelease
Get:1 http://downloads.3cx.com jessie-testing/main amd64 Packages [1,292 B]
Get:2 http://security.debian.org jessie/updates/main Sources [305 kB]
Get:3 http://downloads.3cx.com jessie/main amd64 Packages [1,713 B]
Hit http://security.debian.org jessie/updates/contrib Sources
Get:4 http://security.debian.org jessie/updates/non-free Sources [1,631 B]
Hit http://httpredir.debian.org jessie-updates InRelease
Get:5 http://security.debian.org jessie/updates/main amd64 Packages [664 kB]
Hit http://httpredir.debian.org jessie Release.gpg
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://httpredir.debian.org jessie Release
Get:6 http://security.debian.org jessie/updates/non-free amd64 Packages [4,556 B]
Ign http://downloads.3cx.com jessie-testing/main Translation-en_US
Ign http://downloads.3cx.com jessie-testing/main Translation-en
Ign http://downloads.3cx.com jessie/main Translation-en_US
Hit http://security.debian.org jessie/updates/contrib Translation-en
Ign http://downloads.3cx.com jessie/main Translation-en
Get:7 http://security.debian.org jessie/updates/main Translation-en [335 kB]
Get:8 http://security.debian.org jessie/updates/non-free Translation-en [11.8 kB]
Get:9 http://httpredir.debian.org jessie/main Sources [7,063 kB]
Get:10 http://httpredir.debian.org jessie/main amd64 Packages [6,818 kB]
Get:11 http://httpredir.debian.org jessie/main Translation-en [4,581 kB]
[B]W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-updates/InRelease  Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file)[/B]

E: Some index files failed to download. They have been ignored, or old ones used instead.
########## Upgrade failed (update)
########## Rollback due to error with "update"
dpkg-query: package 'google-cloud-sdk' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
Hit http://downloads.3cx.com jessie-testing InRelease
Hit http://downloads.3cx.com jessie InRelease
Ign http://httpredir.debian.org jessie InRelease
Hit http://security.debian.org jessie/updates InRelease
Get:1 http://security.debian.org jessie/updates/main Sources [305 kB]
Hit http://security.debian.org jessie/updates/contrib Sources
Get:2 http://security.debian.org jessie/updates/non-free Sources [1,631 B]
Get:3 http://security.debian.org jessie/updates/main amd64 Packages [664 kB]
Get:4 http://security.debian.org jessie/updates/non-free amd64 Packages [4,556 B]
Get:5 http://downloads.3cx.com jessie-testing/main amd64 Packages [1,292 B]
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Get:6 http://security.debian.org jessie/updates/main Translation-en [335 kB]
Hit http://security.debian.org jessie/updates/contrib Translation-en
Get:7 http://downloads.3cx.com jessie/main amd64 Packages [1,713 B]
Get:8 http://security.debian.org jessie/updates/non-free Translation-en [11.8 kB]
Hit http://httpredir.debian.org jessie-updates InRelease
Hit http://httpredir.debian.org jessie Release.gpg
Ign http://downloads.3cx.com jessie-testing/main Translation-en_US
Ign http://downloads.3cx.com jessie-testing/main Translation-en
Ign http://downloads.3cx.com jessie/main Translation-en_US
Ign http://downloads.3cx.com jessie/main Translation-en
Hit http://httpredir.debian.org jessie Release
Get:9 http://httpredir.debian.org jessie/main Sources [7,063 kB]
Get:10 http://httpredir.debian.org jessie/main amd64 Packages [6,818 kB]
Get:11 http://httpredir.debian.org jessie/main Translation-en [4,581 kB]
[B]W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-updates/InRelease  Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file)[/B]

E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
3cxpbx is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 102 not upgraded.
/bin/mv: cannot stat ‘/root/UPDATE.log’: No such file or directory
########## Upgrade (FAILED) end time: 2019-04-14T11:57:09Z

I cannot find any specific threads about this problem on this forum. Can someone help me out?

 

[AWS2P]

you tried to upgrade directly from 3cx mc?
I think best way could be to backup 3cx running config and do a fresh DB9 install from scratch and restore during install

 

[StefanW]

the upgrade fails due to this line

W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/source/Sources' in Release file (Wrong sources.list entry or malformed file)


the message that we cannot find google-sdk is okey, as we check if the install runs in google cloud.
Where and how did you install the PBX? From iso? From PBXexpress in Azure, AWS (Google we know it is not)? Manual via APT-Get ?

 

[NickD_3CX]

@MpDay20
The reason you are getting some error for package updates is because some Debian mirrors have been removed. See the conversation here: https://www.3cx.com/community/threads/xxx-az-3cx-us-dns-is-offline.64763/post-275994

 

[MpDay20]

Where and how did you install the PBX? From iso? From PBXexpress in Azure, AWS (Google we know it is not)? Manual via APT-Get ?

ISO, based on 3CX 15.0, 2 years ago I guess.

 

[pitrickzul]

You should backup your 3CX and install Debian form scratch on Stretch and then upgrade to V16. You have outdated sources. Way safer to just stratch from scratch and it's gonna take like 30mins once you start.

 

[MpDay20]

Re-installed and restored backup. Worked great.
However, you 3CX developers really made a mess by not allowing port 7000, 7001 and 7090 anymore. Our instance was using these ports, and, well, someone at 3CX decided not to allow those ports anymore during the wizard. Back in the day, our first instance ran 5000/5001/5090, second instance 6000/6001/6090, and so on.

We had to re-provision all phones because we were forced to use port 5000/5001/5090. Thanks 3CX, you really made our night worth it.

 

[NickD_3CX]

However, you 3CX developers really made a mess by not allowing port 7000, 7001 and 7090 anymore. Our instance was using these ports, and, well, someone at 3CX decided not to allow those ports anymore during the wizard. Back in the day, our first instance ran 5000/5001/5090, second instance 6000/6001/6090, and so on.

Ports 7000-8999 are reserved, and were always used for RTP for Local Endpoints, that is why the wizard did not allow you to use them. Generally quite a few ports are used for RTP in the lower range for various services.
You should be safe choosing ports from 15000 and above though.