[debbugs-tracker] bug#22209: closed (name resolution failures in installer image)

[GNU bug Tracking System]

Your message dated Tue, 03 May 2016 22:26:31 +0200
with message-id <address@hidden>
and subject line Re: bug#22209: name resolution failures in installer image
has caused the debbugs.gnu.org bug report #22209,
regarding name resolution failures in installer image
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
22209: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22209
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> name resolution failures in installer image
>
>
>
>
> Date: 
>
> Sat, 19 Dec 2015 09:04:41 +0100
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
>
>
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
> Hi,
>
> this occurs over and over to me and I saw other people's reports on
> IRC, too:
>
> After booting the installer image, doing the ifconfig/dhclient dance,
> preparing the target fs, mounting it and starting the guix system init
> invocation at some point in time, though not predictably so, but
> usually after a couple of minutes (about 10 or so) name resolution
> will start to fail causing guix system init to fail.
>
> killall dhclient; dhclient <your_interface_name_here>
>
> and a subsequent invocation to guix system init will make the
> installation continue and usually succeed.
>
> On the first few occasions it seemed to me that my local network could
> be at fault, but it's _almost_ reliably reproducable in qemu,
> virtualbox and even on bare metal and is not limited to myself (check
> the channel logs with some good search queries).
>
> So it might be worth looking into.
>
> The installed system does not have this problem after a reboot.
>
> Regards,
> Flo
>
> - -- 
> https://fps.io
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJWdQ+YAAoJEA5f4Coltk8ZgdoIAJ9rDLDhTztcfs4fHWBF+mcf
> U6SYAX36nc7R+TiT7FCWQVxcp38bG5LrTInmP4C/ojyPHEYZcMQLQg2CoT4/q6Ys
> kjMUKvBgFqMsjeZzvo9oXP1VDWygC9YeCg55BGPzpEW5x3oQHcVH0zw8acNrlZ6A
> I9sVoQnaEDKhsNECBwPDMNujqjik6TilvddEl0AS7HYCbyNgPy+dR97G5z+gRt8w
> Wrio0ua5QeyAW5kFCLX7LdDa44OBPoiAlLyWa9dXgFUOORgh88z/dtCPbV0vRNJc
> FKpVmAzcovximrPGgDXs9DzERaSkROM05GGRb/uYFfs5GdoGja5YwjXcoWaHUzo=
> =9+XX
> -----END PGP SIGNATURE-----
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#22209: name resolution failures in installer image
>
>
>
>
> Date: 
>
> Tue, 03 May 2016 22:26:31 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
>
>
>
>
> address@hidden (Ludovic Courtès) skribis:
>
> > address@hidden (Ludovic Courtès) skribis:
> >
> >> Ricardo Wurmus <address@hidden> skribis:
> >
> > [...]
> >
> >>> Could this be related to cached resolution failures in nscd?  Have you
> >>> tried restarting the nscd service?
> >>
> >> That sounds likely.
> >>
> >> Nscd caches negative lookups, but normally only for 20 seconds (see
> >> %nscd-minimal-caches in (gnu system install)).  So if you look up
> >> hydra.gnu.org before the network is set up, it’ll remember for 20s that
> >> this is a lookup failure, even if you’ve set up the network in the
> >> meantime.
> >
> > Commit c96ba2c disables caching of lookup failures altogether.
>
> 0.10.0 uses this fix and we haven’t heard from name resolution failures
> in the installer image, so I’m closing it.
>
> Ludo’.
>
>
> --- End Message ---