Hi! [bob wrote]> [ck wrote] > > I have been trying to update several of my FreeBSD 10.1 amd64 > > VM to 10.2-RELEASE with freebsd-update and have been failing with > > an incorrect hash error.> FWIW I had the same issue yesterday on a couple of systems. > Repeating freebsd-update worked after two or three goes.I've seen the same problem on several hosts and discussed it by mail with gjb at . We assumed that I have a DNS problem because of this line:> Looking up update.FreeBSD.org mirrors... none found.This happens with this query inside the freebsd-update script, at line 950: host -t srv _http._tcp.update.FreeBSD.org If you prime your DNS cache with manual queries, then freebsd-update will sometimes find the hosts and will report that it found some hosts. But, I just tried to reproduce this and failed, the problem persists. So, yes, it looks like a real issue. -- pi at opsec.eu +49 171 3101372 5 years to go !
Hi, On Sun, 16 Aug 2015, Kurt Jaeger wrote: <snipp/>> We assumed that I have a DNS problem because of this line: > >> Looking up update.FreeBSD.org mirrors... none found. > > This happens with this query inside the freebsd-update script, at > line 950: > > host -t srv _http._tcp.update.FreeBSD.org > > If you prime your DNS cache with manual queries, then freebsd-update > will sometimes find the hosts and will report that it found some hosts. > > But, I just tried to reproduce this and failed, the problem persists. > > So, yes, it looks like a real issue.hmmm. Thanks for pointing me at the dns issue. I actually did not see that message as it seems to only appear on subsequent rounds of running freebsd-update. I always deleted /var/db/freebsd-update and thus always started clean. I was able to complete the freebsd-update upgrade when I manually specified on of the mirrors as in: freebsd-update -s update2.freebsd.org -r 10.2-RELEASE upgrade So this does seem to be a dns related issue. It could also be the related to parsing the results of the dns lookup. Anyway seems we have a workaround if we specify the mirrors manually. Greetings Christian -- Christian Kratzer CK Software GmbH Email: ck at cksoft.de Wildberger Weg 24/2 Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer Web: http://www.cksoft.de/
Am 16.08.2015 um 20:07 schrieb Kurt Jaeger:> Hi! > > [bob wrote] >> [ck wrote] >>> I have been trying to update several of my FreeBSD 10.1 amd64 >>> VM to 10.2-RELEASE with freebsd-update and have been failing with >>> an incorrect hash error. > >> FWIW I had the same issue yesterday on a couple of systems. >> Repeating freebsd-update worked after two or three goes. > > I've seen the same problem on several hosts and discussed it by mail > with gjb at . > > We assumed that I have a DNS problem because of this line: > >> Looking up update.FreeBSD.org mirrors... none found. > > This happens with this query inside the freebsd-update script, at > line 950: > > host -t srv _http._tcp.update.FreeBSD.orgI think there is also a problem with freebsd-update. [root at miraculix ~]# freebsd-update upgrade -r 10.2-RELEASE Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 10.1-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. ^C [root at miraculix ~]# host -t srv _http._tcp.update.FreeBSD.org _http._tcp.update.freebsd.org has SRV record 1 40 80 update6.freebsd.org. _http._tcp.update.freebsd.org has SRV record 1 35 80 update4.freebsd.org. _http._tcp.update.freebsd.org has SRV record 1 30 80 update2.freebsd.org. _http._tcp.update.freebsd.org has SRV record 1 5 80 update3.freebsd.org. _http._tcp.update.freebsd.org has SRV record 1 50 80 update5.freebsd.org. freebsd-update reporting no mirrors found but the host command returns mirrors. The problem seams to be the sed -nE "s/${MLIST} (has SRV record|server selection) //p" MLIST is _http._tcp.update.FreeBSD.org but sed doesn't match any of the lines from the host command. Replaceing the servername with the lowercase variant matches every line. There is not DNS Problem but a case sensitivity problem in freebsd-update Regards Estartu -- --------------------------------------------------------------------------- Gerhard Schmidt | http://www.augusta.de/~estartu | Fischbachweg 3 | | PGP Public Key 86856 Hiltenfingen | JabberID: estartu at augusta.de | on request Germany | |