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 > 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]. The last line > doesn't appear to say it's a "localhost" source, and "localhost" > doesn't seem to be in the routing tables [Listing 4]. Could this be > the problem? If it is, could anyone consider adding a warning (or > maybe even failing if an override option isn't set)? > > Thanks very much, > Nicholas — ntung at ntung — https://ntung.com > > > > > === Listing 1 -- output of command, process waits after last line === >> rndc -V stop > create memory context > create socket manager > create task manager > create task > create logging context > setting log tag > creating log channel > enabling log channel > create parser > get key > decode base64 secret > stop > post event > using server 127.0.0.1 (127.0.0.1#953) > create socket > bind socket > connect > > === Listing 2 -- message after wait === > rndc: connect failed: 127.0.0.1#953: timed out > > === Listing 3 -- open files when rndc is frozen === >> lsof -p $(ps -C rndc -o pid=) +L > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME > rndc 19939 root cwd DIR 8,18 12288 108 8193 /etc > rndc 19939 root rtd DIR 8,18 4096 23 2 / > rndc 19939 root txt REG 8,18 31800 1 1055141 /usr/sbin/rndc > rndc 19939 root mem REG 8,18 346560 1 786938 > /lib64/libm-2.10.1.so > rndc 19939 root mem REG 8,18 88640 1 786849 > /lib64/libz.so.1.2.3 > rndc 19939 root mem REG 8,18 14872 1 786933 > /lib64/libdl-2.10.1.so > rndc 19939 root mem REG 8,18 1360392 1 7471871 > /usr/lib64/libxml2.so.2.7.3 > rndc 19939 root mem REG 8,18 1605840 1 7472655 > /usr/lib64/libcrypto.so.0.9.8 > rndc 19939 root mem REG 8,18 131260 1 786809 > /lib64/libpthread-2.10.1.so > rndc 19939 root mem REG 8,18 1408560 1 786838 > /lib64/libc-2.10.1.so > rndc 19939 root mem REG 8,18 354120 1 7471241 > /usr/lib64/libisc.so.50.1.1 > rndc 19939 root mem REG 8,18 1497256 1 7471310 > /usr/lib64/libdns.so.53.0.0 > rndc 19939 root mem REG 8,18 43680 1 7475078 > /usr/lib64/libbind9.so.50.0.3 > rndc 19939 root mem REG 8,18 35616 1 7471143 > /usr/lib64/libisccc.so.50.0.0 > rndc 19939 root mem REG 8,18 120168 1 7471234 > /usr/lib64/libisccfg.so.50.0.0 > rndc 19939 root mem REG 8,18 127680 1 786832 > /lib64/ld-2.10.1.so > rndc 19939 root 0u CHR 136,3 0t0 1 6 /dev/pts/3 > rndc 19939 root 1u CHR 136,3 0t0 1 6 /dev/pts/3 > rndc 19939 root 2u CHR 136,3 0t0 1 6 /dev/pts/3 > rndc 19939 root 3r FIFO 0,8 0t0 1 84973 pipe > rndc 19939 root 4w FIFO 0,8 0t0 1 84973 pipe > rndc 19939 root 5u 0000 0,9 0 1 679 anon_inode > rndc 19939 root 7r REG 0,3 0 1 10516 /proc/2283/status > rndc 19939 root 20u IPv4 84977 0t0 TCP > c-98-207-60-37.hsd1.ca.comcast.net:55316->localhost:953 (SYN_SENT) > > === Listing 4 -- route configuration === >> ip route show > 98.207.60.0/22 dev eth-inet proto kernel scope link src 98.207.60.37 > 169.254.0.0/16 dev eth0 scope link > 192.168.0.0/16 dev eth0 proto kernel scope link src 192.168.2.1 > 192.168.0.0/16 dev eth1 proto kernel scope link src 192.168.2.2 > default via 98.207.60.1 dev eth-inet > _______________________________________________ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users