Update from 16.0.5.619 to 16.0.5.622 (Update 5 Hotfix 2) fails

[AlexanderReichert]

the just released update fails in my environment (hosted on Amazon)
Anything I did?

Hit:1 http://downloads-global.3cx.com/downloads/debian stretch-testing InRelease
Hit:2 http://security.debian.org/debian-security stretch/updates InRelease
Hit:3 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Ign:4 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch InRelease
Err:5 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP: 13.32.202.3 80]
Ign:6 http://cdn-aws.deb.debian.org/debian stretch InRelease
Hit:7 http://cdn-aws.deb.debian.org/debian stretch-updates InRelease
Hit:8 http://cdn-aws.deb.debian.org/debian stretch Release
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.

 

[dredd0606]

Can confirm. I have replicated this error on several systems.

 

[jed]

Hi
Have a look in this thread: https://www.3cx.com/community/threads/update-failing-saltstack-issue.74217/

 

[Saqqara]

A quick search would have found you this post on the issue https://www.3cx.com/community/threa...-u5-hotfix-2-and-u6-beta-2.75270/#post-340435

 

[dredd0606]

Hi
Have a look in this thread: https://www.3cx.com/community/threads/update-failing-saltstack-issue.74217/

Thanks Jed, but I don't think I'll be rushing off to ssh into all the instances we support. Hopefully, 3cx can fix the update from their end with a couple keystrokes.

 

[Alphabetic]

Try again tomorrow, it only came out today. could be server related or anything really.

 

[AlexanderReichert]

A quick search would have found you this post on the issue https://www.3cx.com/community/threa...-u5-hotfix-2-and-u6-beta-2.75270/#post-340435

Thanks Karen ...

 

[Alphabetic]

Thanks Karen ...

(╯°□°）╯︵ ┻━┻

 

[johnvam]

Any official answer from 3CX ???

It's very difficult to log in to more than 100 PBXs and make manual configuration...

 

[AWS2P]

I got on OVH instance some with no problem and some with same as encountered
Atteint:1 http://downloads-global.3cx.com/downloads/debian stretch-testing InRelease
Atteint:2 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Ign:3 http://deb.debian.org/debian stretch InRelease
Atteint:4 http://security.debian.org stretch/updates InRelease
Atteint:5 http://deb.debian.org/debian stretch-updates InRelease
Atteint:6 http://deb.debian.org/debian stretch Release
Ign:7 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch InRelease
Err:8 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP : 99.86.116.37 80]
Lecture des listes de paquets…
E: The repository 'http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release' does no longer have a Release file.

manually made the change in SSH and this solved update failure but I agree this is not an industrial fix with lots of pbxs having same problem

 

[Rolteus]

the just released update fails in my environment (hosted on Amazon)
Anything I did?

Hit:1 http://downloads-global.3cx.com/downloads/debian stretch-testing InRelease
Hit:2 http://security.debian.org/debian-security stretch/updates InRelease
Hit:3 http://downloads-global.3cx.com/downloads/debian stretch InRelease
Ign:4 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch InRelease
Err:5 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP: 13.32.202.3 80]
Ign:6 http://cdn-aws.deb.debian.org/debian stretch InRelease
Hit:7 http://cdn-aws.deb.debian.org/debian stretch-updates InRelease
Hit:8 http://cdn-aws.deb.debian.org/debian stretch Release
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.

Having same problem. Was notified by email that update was available 2 days ago. I let my scheduled update handle it and it failed. The error log my system sent me says the repository is unavailable. This is their problem it would be nice if they could communicate has anyone updated you on this issue?

 

[PeterJL]

Good morning!

Has this issue been resolved yet?

 

[A.Takacs]

Well it is somewhat a grey area between debian, the repo maintainer and 3cx (ie who should fix the non existant repo and how...).
I'd say 3cx should implement some way to fix this "in batch".

 

[JohnS_3CX]

Hi everyone,

The short version is that some Debian machines had this repository, and the repository was moved/taken down by its owner which is not something we control, but we understand that it still affects our customers. The updater sees this missing repo as an error and stops the upgrade, so you will need to manually intervene on machines that were affected using the below command:

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

This downloads and runs a 3CX script that will address the issue, and allow you to resume updates normally as before, as well as ensure that this condition (if it were to re-occur) would not be able to stop you from updating in the future.

 

[A.Takacs]

any suggestion as how to deploy this on dozen if not hundreds of instances ?

 

[tron]

The instances I have running on Google GCP are having the update issue described above. I only have a few, so I can SSH into them, but this does seem like a very widespread issue. And would be a pain if you had tons.

 

[tron]

Hi everyone,

The short version is that some Debian machines had this repository, and the repository was moved/taken down by its owner which is not something we control...

The installs I am seeing this on were created from the 3CX PBX Express, and I have not modified them at all.

 

[JohnS_3CX]

@tron not all instances will have that repository, you will have to update your machines and only SSH into the ones that failed with the message about the saltstack repository

 

[Rolteus]

Hi everyone,

The short version is that some Debian machines had this repository, and the repository was moved/taken down by its owner which is not something we control, but we understand that it still affects our customers. The updater sees this missing repo as an error and stops the upgrade, so you will need to manually intervene on machines that were affected using the below command:

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

This downloads and runs a 3CX script that will address the issue, and allow you to resume updates normally as before, as well as ensure that this condition (if it were to re-occur) would not be able to stop you from updating in the future.

I tried "wget -O - https://downloads.3cx.com/downloads/misc/debianpatches/9/16/0/5/20200619-os-update.sh | bash" without quotes and i get invalid command. is there a certain directory i need to be in to successfully execute this command. i have to say this really isn't any way to manage critical updates. im really stressed out i don't need these hassles. i was notified two days prior to this update and it was removed before i could run it. ive had this problem before and it seems like it could be avoided. not sure what to think just want to get my system updated and move on with my life. can you give proper instructions for running this update please? thank you.

 

[Rolteus]

Thanks Jed, but I don't think I'll be rushing off to ssh into all the instances we support. Hopefully, 3cx can fix the update from their end with a couple keystrokes.

This fix isn't working. My update logfile says: "Try and perform the update one more time. Chances are that the update will succeed. If not contact support and send the log files".

How would I "contact support" if I don't have any tickets? Am I supposed to purchase a support ticked for this problem this is your issue with missing files and an invalid command. Not sure what to do here. Any assistance would be greatly appreciated.