Apparently, though unproven, at 21:17 on Tuesday 16 November 2010, Jarry did opine thusly:
> Hi, > today I updated my bind from 9.4.3_p5 to 9.7.1_p2. I noticed > a few changes in configuration so first I did full backup, then > uninstalled 9.4.3_p5 first, removed all configuration files, > then emerged 9.7.1_p2, and configured it to run from chroot. > > named seems to start normally: > > # /etc/init.d/named start > * Starting chrooted named ... > * Mounting chroot dirs > * mounting /etc/bind to /chroot/dns/etc/bind > * mounting /var/bind to /chroot/dns/var/bind > * mounting /var/log/named to /chroot/dns/var/log/named [ ok ] > > The problem is, it runs forever, and does not want to stop: > > # /etc/init.d/named stop > * Stopping chrooted named ... > * Umounting chroot dirs > * Waiting until all named processes are stopped > > And there it hangs. I have been waiting for 15min, but nothing > happened and ps shows named is still running. I aborted with > ctrl+c and tried again, but still the same. I checked logs, > but did not find anything suspicious. So where is the problem? Do you absolutely *have* to run bind? Aside from it being a 100% RFC-compliant reference server, it's a pig to run in real life. For an auth server, powerdns is very good. For a cache, unbound. What you have here is common. Bind can't find, or can't deal with, it's PID file. Or it's just being stubborn. Check your config that the PID file is in the right place, usable and that it has the correct pid in it. Also check the init script for the same thing. Failing that, there's "kill -9", this won't break anything but might disconnect a client. -- alan dot mckinnon at gmail dot com
