Can't update from 13.2-RELEASE-p5 to 13.2-RELEASE-p10

B

bsd_akuma

Dear amazing FreeBSD Community,

I have never encountered the following problem:

I wanted to update my testmachine which is running an older patchlevel of FreeBSD 13.2-RELEASE namely 13.2-RELEASE-p5 to the newest patchlevel which is currently 13.2-RELEASE-p10. When issuing the command sudo -E freebsd-update fetch different files are downloaded from the update1.freebsd.org server into the default working directory /var/db/freebsd-update/. After downloading and applying the patches my system wants to download additional 6 files of which the first three are downloaded but the last three aren't.

After some research I found the hidden --debug command for freebsd-update. It seems that after applying the patches and downloading the additional files the process behind freebsd-update fetch namely phttpget somehow can't download the last three files and ends up in an error stating phttpget: Connection failure.

I tried the following:

  • Deleting contents of /var/db/freebsd-update/
  • Restarting the VM
  • Using another Update-mirror
But everything fails so far.

I also tried fetching the last three missing files via fetch. This worked, but I don't know how to proceed from here. When moving the downloaded files to /var/db/freebsd-update/files/ and issuing freebsd-update install I get a message stating I should do a freebsd-update fetch before installing any updates. So this leads me to nowhere.

Here is some output of the freebsd-update debug:

Code: 
sudo -E freebsd-update fetch --debug

Looking up update.FreeBSD.org mirrors... 3 mirrors found.
pub.ssl                                                800  B 2861 kBps    00s
done.
Fetching metadata signature for 13.2-RELEASE from update1.freebsd.org...
latest.ssl                                             512  B 1908 kBps    00s
done.
Fetching metadata index...
97c00216aa300a28650987d78605254e93fb2907a6202b         225  B  862 kBps    00s
done.
Fetching 2 metadata files...
/usr/libexec/phttpget update1.freebsd.org 13.2-RELEASE/amd64/m/2b75724f373d87719daa5f638b5a5f3c676277bb04de7ca6982577c2cb0d6ad0.gz 13.2-RELEASE/amd64/m/e841e74449f50e4bdac39774b9ade935e6c344f4c153b1c3349c543b006f893d.gz
http://update1.freebsd.org/13.2-RELEASE/amd64/m/2b75724f373d87719daa5f638b5a5f3c676277bb04de7ca6982577c2cb0d6ad0.gz: 200 OK
http://update1.freebsd.org/13.2-RELEASE/amd64/m/e841e74449f50e4bdac39774b9ade935e6c344f4c153b1c3349c543b006f893d.gz: 200 OK
done.
Inspecting system... done.
Preparing to download files... done.
Fetching 98 patches...
<output omitted>
Applying patches... done.
Fetching 6 files...
/usr/libexec/phttpget update1.freebsd.org 13.2-RELEASE/amd64/f/014e9c8001b069b99662e4c9e86949c13f22aa98e9108084d996bfcc7b5880ec.gz 13.2-RELEASE/amd64/f/275b6a94af8ba6b13bb626307cd8934f5a3ce3578a4fed4980111a2d35880a27.gz 13.2-RELEASE/amd64/f/6283ddee1ba11ec2a526588e3be78c201139f9b1c12a96df8e448940502da3a2.gz 13.2-RELEASE/amd64/f/d18075d7c5d32209736734bfb422ac17a76bd69e2b4194ab6b29da6bb9e421d2.gz 13.2-RELEASE/amd64/f/fb7a3587dffa269b52165750bb08335a55ea28f42d7748ffeec19a9756f0e964.gz 13.2-RELEASE/amd64/f/fdf8e042b1b06bafb9450b0bbc40028bf46ea7ff3394900bb6ac9012adbc1f68.gz
http://update1.freebsd.org/13.2-RELEASE/amd64/f/014e9c8001b069b99662e4c9e86949c13f22aa98e9108084d996bfcc7b5880ec.gz: 200 OK
http://update1.freebsd.org/13.2-RELEASE/amd64/f/275b6a94af8ba6b13bb626307cd8934f5a3ce3578a4fed4980111a2d35880a27.gz: 200 OK
http://update1.freebsd.org/13.2-RELEASE/amd64/f/6283ddee1ba11ec2a526588e3be78c201139f9b1c12a96df8e448940502da3a2.gz: 200 OK
phttpget: Connection failure
 failed.

Curiously enough I also needed to update some production machines from 13.2-RELEASE-p9 to 13.2-RELEASE-p10. Those machines updated without any problems.

Solving this problem is pure curiosity. The VM is nothing special and can be recreated. But it would be interesting what your suggestions would be on solving this problem.

I've also looked at different forum entries mentioning that phttpget could be the culprit by wrongly using username:password credentials for proxy-use. But I don't think it has anything to do with that since phttpget can download all other files in my case. Only the last 3 are problematic.

The links to the topic discussing phttpget as the culprit are here:

Does anyone have some clues besides reinstalling FreeBSD entirely?
 
bsd_akuma said:
But I don't think it has anything to do with that since phttpget can download all other files in my case. Only the last 3 are problematic.
Click to expand...
Does the proxy have some sort of IPS feature? That seems to cause problems for some people.
 
SirDice said:
Does the proxy have some sort of IPS feature? That seems to cause problems for some people.
Click to expand...
Yes it has. I didn't think about it. But looking into the logs it doesn't look any different from the production systems.
Normally we would inspect the ssl certificate, but for some servers (this one included) we bypass that.

But I will investigate more on that behalf. Thank you!
 
Apparently there are some people that reported issues with some anti-malware proxies. Something to do with the number of connections and/or the size of the files. Definitely something to verify.
 
SirDice said:
Apparently there are some people that reported issues with some anti-malware proxies. Something to do with the number of connections and/or the size of the files. Definitely something to verify.
Click to expand...
I tried looking more into our logs but unfortuantely I don't get any more information on that. I am somewhat certain that this problem has to do with the VM itself.
I've spun up a new fresh VM with an unpatched FreeBSD 13.2-RELEASE and this one donwloaded all files and applied all patches for FreeBSD 13.2-RELEASE-p10. So in my opinion something needs to be wrong the VM itself.

Someone who might come across this topic should look at their IPS though. As you've stated it could be the culprit in this whole situation.
But in my case this is only a test-vm and nothing important is on it, it will be wiped and recreated. I don't think that the time digging into that problem worth it.

Still a big thank you for your help! It's always much appreciated!
 
You must log in or register to reply here.
Back
Top