[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Any idea why chroot temporarily "cannot find name for group ID 0"?



Can you suggest why I'm seeing the following error when entering a debootstrap chroot on a Fedora host, and why it spontaneously disappears a few minutes later?

[root@XXXX svn]# chroot staging/www
id: cannot find name for group ID 0
id: cannot find name for group ID 1
id: cannot find name for group ID 2
id: cannot find name for group ID 3
id: cannot find name for group ID 4
id: cannot find name for group ID 6
id: cannot find name for group ID 10
I have no name!@XXXX:/#

More detail on the mystery problem is on linuxquestions.org [1], but in short: I created two chroots on a Fedora Core 4 box using debootstrap (hardy). The chroots work great, and one contains a webserver and the other contains a database. Everything is awesome except after some period of time (or some unknown activity), the www chroot temporarily "breaks" and spits out the error above when I try to enter it.

But the real mystery is it just spontaneously corrects itself a few minutes later, even though I make no changes to permissions or files. For example, here's a log of me exiting a broken chroot, and then immediately re-entering without having made any changes:

I have no name!@XXXX:/etc# exit
[root@XXXX svn]# chroot staging/www
root@XXXX:/#

Even stranger, I've experienced the 'www' chroot having this behavior (repeatably, for several minutes) even though I can chroot into a 'db' chroot just fine -- despite both being created with the exact same debootstrap command.

I'm at a total loss and posting this here because I'm not sure if it's a Debian or Fedora issue: it's happening inside a Debian chroot, but on a Fedora host.

Any suggestions?  Thanks!

-david

[1] http://www.linuxquestions.org/questions/linux-newbie-8/chroot-temporarily-cannot-find-name-for-group-id-0-651928/


Reply to: