That is what I was talking about. Sorry for being unclear. Yes you have something messed up with that lo config. Check your /etc/sysconfig/network-scripts/ifcfg-lo Should like like this DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback Then restart your network > -----Original Message----- > From: Noah [mailto:admin2@xxxxxxxxxxx] > Sent: Saturday, June 19, 2004 1:54 PM > To: General Red Hat Linux discussion list > Subject: RE: restarting named - rndc: connect failed: > operation canceled > > > On Sat, 19 Jun 2004 12:44:10 -0500, Cowles, Steve wrote > > Noah wrote: > > > On Sat, 19 Jun 2004 08:48:42 -0400, Jason Staudenmayer wrote > > >> Do you have the local bound to your interface? I've seen > cases where > > >> it was not. > > >> > > > I dont quite understand. what do I check here please? > > > > > > > I don't quite understand what Jason is referring to either, but I > > think he's referring to your systems loopback device. > > > > Just to add to this thread - there are only a few things that I can > > think of that would cause bind/named NOT to be able to > "bind" to the > > loopback device. > > > > 1) Your system does not have a loopback device defined. i.e. > > > > [root@excelsior postfix]# ip -s link show lo > > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > RX: bytes packets errors dropped overrun mcast > > 88978146 135295 0 0 0 0 > > TX: bytes packets errors dropped carrier collsns > > 88978146 135295 0 0 0 0 > > > > > now it looks like we might be on to something. > > # ip -s link show lo > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > RX: bytes packets errors dropped overrun mcast > 10955835 113012 0 0 0 0 > TX: bytes packets errors dropped carrier collsns > 10955835 113012 0 0 0 0 > > > > > [root@excelsior postfix]# ip -s addr show lo > > > > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > inet 127.0.0.1/8 brd 127.255.255.255 scope host lo > > > > > but wait look at this - no addresses are mentioned here? > > # ip -s addr show lo > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > > is there something i have misconfigured somewhere else? on > the Loopback perhaps? > > - Noah > > > > > 2) There is another process already running that is bound to > > 127.0.0.1 port 953 > > > > 3) I don't even know if this is possible, but your system's kernel > > was not compiled with support for the loopback device. > > > > Maybe someone else on the list might have some other ideas. > > > > Steve Cowles > > > > -- > > redhat-list mailing list > > unsubscribe > mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > > https://www.redhat.com/mailman/listinfo/redhat-list > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
