Prepare for New Chrome and Edge Releases with U5 Hotfix 2 and U6 BETA 2

[ochapple]

When attempting to run the update, I'm getting the following error on a number of servers:

Ign:8 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch InRelease
Err:9 http://repo.saltstack.com/apt/debian/9/amd64/archive/2019.2.0 stretch Release
404 Not Found [IP: 13.227.73.82 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.

All servers are based in Australia, some hosted in the cloud and some on local VM/Servers.

I am getting this too and i'm in the UK. It maybe the Debian OS but its a 3CX error we are receiving! What's the solution?

 

[ochapple]

Hello @Liam Pool ,

Those errors are related to the Operating System and are not connected with the PBX Update.

Please check with your provider.

Hi Liam, I get the same error message, failed update, and my OS is Debian 9 hosted on GCP in Europe. I'm not comfortable with using the shell, probably like many as we use PBX Express, code-free install. Are you going to roll a fix for this to the update installation files?

 

[ochapple]

Thanks guys. I am most decidedly not an IT guy; my shell adventures are largely dictated by the maxim "man who hack at root soon kill tree." It was the sudo su I hadn't added. Four updates and hotfixes later and I'm up to date.

Hi Seth, did you get yours sorted in the end or are you waiting like me for an update fix, like you I don't like the idea of hacking the OS to make what should be a code-free install work! What happens next time and it's far worse?!

 

[JohnS_3CX]

Hi @ochapple

If you are getting the error which references the saltstack repo, you have to manually SSH into the machine and run the aforementioned command. There is no automatic update or workaround unfortunately - this is the only way to achieve the desired effect

The fix literally is the below command. You have to SSH into your machine as root, or alternatively elevate your privilege level by running sudo su and then then below

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

The rest of your questions are answered here in the below post, and it includes a detailed description of what caused it and what we will change to prevent this from happening in the future
https://www.3cx.com/community/threads/saltstack-repo-issue.75315/

 

[ochapple]

Many thanks for that, I did run that successfully thank goodness as if it had errored I would have been stuck! much appreciated. I ran the SSH shell tool 'in Browser' inside GCP's Compute app, it looks like i already had the right permissions and didn't require the 'sudo su' command first.

 

[JohnS_3CX]

Glad to hear, thanks for confirming the fix worked.

In case you use Instance manager, you can re-enable it it now, if not then ignore this message.

As for future releases, our next stable update should address the issue so this can be prevented in the future.

 

[Mike77339]

I’m having the same issues with a few of mine, they are runing on lightsail PBX express

I feel that 3cx's process to provide these hotfixes/updates needs improvement. They should have as priority to update their express installations with Lightsail with no complications.

 

[JohnS_3CX]

Hi @Mike77339

Indeed it is our priority and your concerns have been addressed with the next release. If you want some more details, on how this occurred and what has been done to address it, take a look here:
https://www.3cx.com/community/threads/saltstack-repo-issue.75315/

 

[Mike77339]

Hi @Mike77339

Indeed it is our priority and your concerns have been addressed with the next release. If you want some more details, on how this occurred and what has been done to address it, take a look here:
https://www.3cx.com/community/threads/saltstack-repo-issue.75315/

I'm glad it will be addressed, but I can't access that thread..

 

[JohnS_3CX]

Just to quickly reiterate that post:

We changed the logic of the updater in the next 3CX version to prevent this from happening in the future and in U7 we also will add OS Patch scripts besides the service packs for the PBX. Those will run like the security updates on daily basis and would correct such things in case they happened again.

 

[Myprovider]

Hi Liam,

I might be able to help you with this, since these are clearly Debian servers.
You can run the following command and afterwards you should be able to update normally again.

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

Hi John,

Thank you very much, this worked for me also.
Only 1 out of 8 debian 3CX servers had this issue, i am extremely glad it is resolved for us now, still i bit curious though what went wrong that got us in this situation?

 

[JohnS_3CX]

A Debian repository was removed by the owner, and the updater was stopped when it encountered this error.

From Update 7 onwards this has been addressed so that it should not re-occur in the future.