Date: Sat, 13 Dec 2008 12:23:22 -0600 From: Steven Susbauer <stupendoussteve@hotmail.com> To: Manolis Kiagias <sonic2000gr@gmail.com> Cc: Renat <renat@maps.mi.ru>, freebsd-questions@FreeBSD.org Subject: Re: Upgrade from FreeBsd 6.3 to 6.4 freebsd-update Message-ID: <4943FD9A.4050308@hotmail.com> In-Reply-To: <4943B10E.50505@gmail.com> References: <1013558171.20081213113939@maps.mi.ru> <4943801E.1000306@gmail.com> <34816500.20081213130432@maps.mi.ru> <4943AB57.2060600@gmail.com> <1164220109.20081213154715@maps.mi.ru> <4943B10E.50505@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1625350413F44AEB1B39E2AB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Manolis Kiagias wrote: > Renat wrote: >> Yes. I try . But not worked!! >> >> ----- >> webarchive# freebsd-update -r 6.4-RELEASE upgrade >> Looking up update1.FreeBSD.org mirrors... none found. >> Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org..= =2E done. >> Fetching metadata index... done. >> Fetching 1 metadata files... failed. >> >> >> I probe you solution change change server from >> update.freebsd.org to update1.freebsd.org >> >> Not worked((( >> >> What's is is the Bug on the FreeBSD servers? >> >> >> =20 >=20 > Nothing wrong on the FreeBSD servers, AFAIK. > I remotely upgraded two 6.3 servers to 6.4 just yesterday > There must be something on your end or your ISP that causes this. Most likely something is blocking dns SRV requests (which is what FreeBSD-update uses to find the mirrors). I used to have this problem due to a misconfigured dnsmasq install. I fixed it but my problem is the reason that update.freebsd.org has an A record of its own now. Because of this it should not cause an impact on the update process, and you shouldn't need to change update to update1 anymore. It would not surprise me if your problems are related to using the addon freebsd-update rather than the built-in, which you apparently overwrote with the addon one (the original is in the sources, or on the CVS). It could be unrelated, but it is an easily identifiable misstep. If you cannot get freebsd-update working, you could update using a 6.4 cd= =2E Also, there is nothing wrong with the FreeBSD servers, as I just updated a few seconds ago: athlon# freebsd-update -r 6.4-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/smp world/base The following components of FreeBSD do not seem to be installed: kernel/generic src/base src/bin src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/catpages world/dict world/doc world/games world/info world/manpages world/proflibs Does this look reasonable (y/n)? --------------enig1625350413F44AEB1B39E2AB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklD/ZwACgkQ2i3YYzbDt08ZSACfRUwLyvG7VBpNttOxHhzoYf/+ 5WUAn0d8tyPF77E/d0aMy+EMWzMhvwRP =BKh3 -----END PGP SIGNATURE----- --------------enig1625350413F44AEB1B39E2AB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4943FD9A.4050308>