Hi all,
The rndc tool, which is used for all BIND configuration (yast,
/etc/init.d/named stop), appears to stall on any command. See [Listing
1] for output before it stalls (freezes not in the DNS zone sense)
and [Listing 2] for afterwards.
I used lsof to show the open files [Listing 3].
Is lo up?
Is named actually listening on 127.0.0.1:953?
Is there a firewall?
On Sun, Jan 24, 2010 at 1:29 PM, Nicholas Tung nt...@ntung.com wrote:
Hi all,
The rndc tool, which is used for all BIND configuration (yast,
/etc/init.d/named stop), appears to stall on any command. See [Listing
Thanks very much! $(ifconfig lo up) fixed the first problem. I'm
curious why the init script relies on this socket connection, and that
it got a timeout instead of immediate failure because the interface
wasn't up.
[For anyone who has the same problem],
it's necessary to run $(killall rpcbind
3 matches
Mail list logo