Solved New V16 Update 6 Final release

[Phil Sbrana-Browning]

We do not have any specific need of any new functions in this update, but have a policy of updating to latest version, to ensure we have full security and patches in place.

Today I took snapshot and ran upgrade from V16.0.5.622 but the update failed.
Log file contained.

E: Failed to fetch http://security.debian.org/dists/st...ea56a181b12406313eceb82a8fa33aa33dd910510a08a Hash Sum mismatch
Hashes of expected file:
- Filesize:557848 [weak]
- SHA256:77c591ff4195eef3d47ea56a181b12406313eceb82a8fa33aa33dd910510a08a
- SHA1:4d30d632737d8565cda62cb0686502830bd5e7d1 [weak]
- MD5Sum:a138e460d83401e8be8c50fe2aa72131 [weak]
Hashes of received file:
- SHA256:6adae361c629fa3e56abd3db5572e70dfc572f1bdf790887a79ce9c7de117613
- SHA1:4a582ddceae4473dbe7be2b81e95b7fa70da1aa6 [weak]
- MD5Sum:af62cc88903446a9025832ab1af13f5a [weak]
- Filesize:3162 [weak]
Last modification reported: Thu, 27 Aug 2020 08:06:08 +0000
Release file created at: Wed, 26 Aug 2020 16:57:06 +0000
E: Failed to fetch http://security.debian.org/dists/st...205c9531b7992c70e61af7cfaaf507cc1385df3e0b49c
E: Some index files failed to download. They have been ignored, or old ones used instead.

As the update failed it rolled back, anyone else seeing this issue? I did not have to recover via snapshot, but would like to understand the nature of the failure. and how to fix resolve

 

[AWS2P]

got done last night all my pbxs updated ,windows, debian, on premise and cloud without any problems.
Only one Win 10 on premise got Nginx service failed after update.

 

[AWS2P]

Update .622 fails mostly. You will notice a newer update appear .641 ( Final Update) eventually and that will upgrade successfully.

It's exactly what OP was trying to do do, an update from .622 to .641 wasn't it?

 

[Phil Sbrana-Browning]

yes it was 622 to 641 - interesting some of my other PBX's worked no problem. maybe it is just a transitory issue will try again tomorrow when that PBX not in use. Just wondered if anyone else had seen that error, but I always do updates when users are not active. So now I will have to wait until tomorrow try again. But I always do a snapshot prior to update so that if the worst happens I can get it back in shor order

 

[AWS2P]

Is it on premise PBX or cloud ?

 

[Phil Sbrana-Browning]

On Premise

 

[AWS2P]

is it the first time you got update problems on this location?
could it be some firewall restrictions or URL filtering cutting update process to have proper access the online files?

 

[JohnS_3CX]

Give it another shot, perhaps it was an incomplete transfer or caught in the middle of the repo replication.

Let us know how it goes

 

[Phil Sbrana-Browning]

Yes this is the first failure for this location, funny enough the only location that passes the firewall check, all other locations work fine, but fail the firewall check.
But yes, I think I will try again tomorrow when users are tucked in their beds, and the system is quiet the good thing about having 3cx servers on five continents you always have a few available, and having them on VM platform "on prem" means easy to snapshot.
Will update this page with result

 

[Phil Sbrana-Browning]

Okay today it worked fine, looks like it was just a transient issue, many thanks for your feedback.

Regards Phil

 

[JohnS_3CX]

Great news, will mark this one as solved then