all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Florian Paul Schmidt <mista.tapas@gmx.net>,
	Leo Famulari <leo@famulari.name>
Cc: 22209@debbugs.gnu.org
Subject: bug#22209: name resolution failures in installer image
Date: Wed, 10 Feb 2016 21:54:40 +0100	[thread overview]
Message-ID: <87wpqcjnfz.fsf@gnu.org> (raw)
In-Reply-To: <87a8p6xqcj.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 19 Dec 2015 19:09:32 +0100")

ludo@gnu.org (Ludovic Courtès) skribis:

> Ricardo Wurmus <rekado@elephly.net> 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.

Could you try again to reproduce it?  (I think Florian wrote in the
initial bug report that this was reproducible in QEMU, so using
‘guix system vm gnu/system/install.scm’ might suffice.)

Alternately we could remove nscd altogether, but I think it’s still
somewhat useful to cache successful lookups.

TIA,
Ludo’.

  parent reply	other threads:[~2016-02-10 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19  8:04 bug#22209: name resolution failures in installer image Florian Paul Schmidt
2015-12-19  8:45 ` Leo Famulari
2015-12-19 10:25   ` Ricardo Wurmus
2015-12-19 18:09     ` Ludovic Courtès
2015-12-20 10:12       ` Florian Paul Schmidt
2016-02-10 20:54       ` Ludovic Courtès [this message]
2016-05-03 20:26         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wpqcjnfz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=22209@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=mista.tapas@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.