freebsd-fetch ... none found question

H

hammer185

On some of my servers when I run freebsd-fetch and other similar tools if they pick update4.freebsd.org it appears the fetching metadata signature fails. In each instance with different servers, if I force update2.freebsd.org the problem does not occur. This has been a nagging problem for a while with only some of my servers. Any insight into configuration values I might need to look into would be helpful. I haven't troubleshot this much but it almost appears that there is a problem between some of my servers and update4.freebsd.org and I think also some of the other update mirrors that doesn't occur if I force update2.freebsd.org.

For example, see below.

----------
freebsd-update fetch
src component not installed, skipped
Looking up update4.freebsd.org mirrors... none found.
Fetching metadata signature for 13.3-RELEASE from update4.freebsd.org... failed.
No mirrors remaining, giving up.

This may be because upgrading from this platform (amd64)
or release (13.3-RELEASE) is unsupported by freebsd-update. Only
platforms with Tier 1 support can be upgraded by freebsd-update.
See https://www.freebsd.org/platforms/ for more info.

If unsupported, FreeBSD must be upgraded by source.
root@rafmt01:/usr/home/rroot # freebsd-update fetch -s update2.freebsd.org
src component not installed, skipped
Looking up update2.freebsd.org mirrors... none found.
Fetching metadata signature for 13.3-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
----------
 
adorno said:
% host update4.freebsd.org
Host update4.freebsd.org not found: 3(NXDOMAIN)

What's in your /etc/freebsd-update.conf ?
Click to expand...
SirDice said:
What does host -t srv _http._tcp.update.freebsd.org output?
Click to expand...
I'm cautious about sharing my entire freebsd-update-conf rashly but it's probably not changed much except the following entry with documentation in freebsd-update.conf which might be causing the problem. I haven't read the documentation on ServerName in that config file in a while and likely need to do that.
# Server or server pool from which to fetch updates. You can change
# this to point at a specific server if you want, but in most cases
# using a "nearby" server won't provide a measurable improvement in
# performance.
# Modified by Ryan Root 14 March 2019 do to poor performance to update1.freebsd.org
ServerName update4.freebsd.org

However, thus far with my FreeBSD servers, I am seeing two different results for host -t srv _http._tcp.update.freebsd.org at this point.

One set of results is
_http._tcp.update.freebsd.org has SRV record 1 50 80 update2.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 100 50 80 dualstack.aws.update.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 1 50 80 update1.freebsd.org.

The other is
_http._tcp.update.freebsd.org has SRV record 1 50 80 update1.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 1 50 80 update2.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 100 50 80 dualstack.aws.update.freebsd.org.
 
Thanks all, these interactions on these forums help me work through some of the oddness I have observed over the years but not all of it yet. I'm reviewing my notes and memory to see if all my servers that were having this problem had the update4.freebsd.org reference and so far it doesn't appear so. If I get more information if it continues where I can ask intelligent questions on this forum, I appreciate that it is available. My son asked me the other day what my favorite operating system is. I told him, FreeBSD!
 
You must log in or register to reply here.
Back
Top