3CX update failed - Debian - New 16.0 Update 5 Rollup

[IAN MCNAIR]

Hi, has anyone else had this error when updating? and if so, whats the solution?

A problem occurred and 3CX Phone System was not updated successfully.

Your installation at ??????????.3cx.co.uk encountered a problem and the update was not successful. The system was rolled back to the previous version.

Hit:1 http://downloads-global.3cx.com/downloads/debian stretch-testing InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://deb.debian.org/debian stretch-updates InRelease
Hit:4 http://security.debian.org stretch/updates InRelease
Hit:5 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Ign:6 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch InRelease
Hit:7 http://deb.debian.org/debian stretch Release
Err:8 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP: 99.86.109.96 80]
Reading package lists...
E: The repository 'http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release' does no longer have a Release file.

 

[Saqqara]

A quick search would have found you this - https://www.3cx.com/community/threads/update-failing-saltstack-issue.74217/#post-333876

 

[JohnS_3CX]

Hi,

We noticed some cases that reported this error, we are looking into it so we can provide a solution

 

[JohnS_3CX]

You may run this command on your machine and the proceed to update from the managment console

wget -O - https://downloads.3cx.com/downloads/misc/debianpatches/9/16/0/5/20200619-os-update.sh | bash

 

[Mercuris]

Hi,
this command doesn't work for my instance
BR

 

[JohnS_3CX]

@Mercuris Can you provide some more details (error messages)? Did you elevate to root before running?

 

[Mercuris]

@JohnS_3CX it works now
I followed the answer from 3CX support:

Please try the following:

Modify the following file: /etc/apt/sources.list.d/busylight.list

You can do this using nano as so: nano /etc/apt/sources.list.d/busylight.list

Then, comment out the one line by adding a # symbol in front of it. You should end up with the following contents in the file:
#deb http://kbl.bilisim.me/debian ./

Save it and then use cat /etc/apt/sources.list.d/busylight.list to confirm that the contents is still commented out(with the # symbol). If yes, please try to update 3CX again and let me know what happens.

 

[JohnS_3CX]

Hi

I'm glad to hear it was resolved. This means you had some 3rd party source that was not longer updatable or the repo was dead, and the update command was failing. This lead to case where the system was forced to halt all the updates (including 3CX and Debian updates).

I believe the first time it failed you should have received an email that was showing you the repo that caused the failure. From there, you can go and remove that repo or comment it out and the updater can proceed when your next run it.

It sounds like someone tried to install a Kuando Busylight script at some point in the past, and forgot about it so the repo was left orphaned after it died.

 

[KFACTA]

Hi

I'm glad to hear it was resolved. This means you had some 3rd party source that was not longer updatable or the repo was dead, and the update command was failing. This lead to case where the system was forced to halt all the updates (including 3CX and Debian updates).

I believe the first time it failed you should have received an email that was showing you the repo that caused the failure. From there, you can go and remove that repo or comment it out and the updater can proceed when your next run it.

It sounds like someone tried to install a Kuando Busylight script at some point in the past, and forgot about it so the repo was left orphaned after it died.

We need this fixed from 3CX to roll out, im not looking at having to do this for 40+ instances

 

[vitalcomm_jw]

Unfortunately the update script provided by JohnS did not solve this issue in my case.

After running the script the repository is still pointed to "http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0"

When I browse to this repo URL it does not exist.
v2.0 has been removed.
The only versions available at this moment via the 'archive' directory are '2019.2.4' and '2019.2.5'.

To resolve, I edited the repo file under "/etc/apt/sources.list.d/saltstack.list"
Changed from--
"http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release"
Changed to--
"http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.5 stretch Release"

Saved, then ran...
apt-get update
apt-get upgrade

Solved.

KFACTA,

As JohnS pointed out, your issue and the fix you mentioned seems to be something special with your instances that does not apply across the board to everyone. My 3CX instance does not have a repo file for "/etc/apt/sources.list.d/busylight.list"
busylight does not appear to be a 3CX related dependency
(i.e. I suspect this is something you will be responsible for resolving, not 3CX)

What platform are your instances installed to?
Physical server? vm? hosted vps? (which hosted platform?)

 

[KFACTA]

Unfortunately the update script provided by JohnS did not solve this issue in my case.

After running the script the repository is still pointed to "http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0"

When I browse to this repo URL it does not exist.
v2.0 has been removed.
The only versions available at this moment via the 'archive' directory are '2019.2.4' and '2019.2.5'.

To resolve, I edited the repo file under "/etc/apt/sources.list.d/saltstack.list"
Changed from--
"http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release"
Changed to--
"http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.5 stretch Release"

Saved, then ran...
apt-get update
apt-get upgrade

Solved.

KFACTA,

As JohnS pointed out, your issue and the fix you mentioned seems to be something special with your instances that does not apply across the board to everyone. My 3CX instance does not have a repo file for "/etc/apt/sources.list.d/busylight.list"
busylight does not appear to be a 3CX related dependency
(i.e. I suspect this is something you will be responsible for resolving, not 3CX)

What platform are your instances installed to?
Physical server? vm? hosted vps? (which hosted platform?)

All our instances are PBXExpress on Azure and have not been modified. OOBE via the PBXExpress route.

 

[JohnS_3CX]

We need this fixed from 3CX to roll out, im not looking at having to do this for 40+ instances

We apologise for the inconvenience, but if this issue with the repo affected you, you will have to run the command

wget -O - https://downloads.3cx.com/downloads/misc/debianpatches/9/16/0/5/20200619-os-update.sh | bash