[Linux-HA] HA Newbie

Ernest Byaruhanga ernest at afrinic.org
Tue Jun 29 12:54:56 MDT 2004


Hello Christof,

On Tuesday 29 June 2004 02:25, Christof Amelunxen wrote:
> Hi Ernest,
>
> Am Di, den 29.06.2004 schrieb Ernest Byaruhanga um 5:32:
> > [root at ns1 root]# /etc/rc.d/init.d/named start
> > Starting named:                                            [  OK  ]
> > [root at ns1 root]# /etc/rc.d/init.d/named status
> > rndc: connect failed: connection refused
> > [root at ns1 root]#
> >
> > this is my problem...
>
> That sounds as if named is either not listening on Port 953 for rndc
> connections or rndc and named do not share the same secrets in
> /etc/named.conf and /etc/rndc.conf.

i cross-checked the rndc.key file against the configuration of /etc/named.conf 
and everything seems ok. 

> Is named running after "/etc/rc.d/init.d/named start"? If it is, then
> check the Ports its listening to via "netstat -an". Most likely your
> named.conf or rndc.conf got screwed up somehow.

starting named gives OK. Polling afterwards to see status, or to stop it, or 
just doing rndc reload gives "rndc: connect failed: connection refused". 
netstat -an does not show show me named, or rndc. Ports 53 and 953 are also 
not open.

> Anyway, it doesnt seem to be a heartbeat issue at all.

i think it is a heartbeat issue as it exactly the same problem on both 
servers, yet they were working perfectly both before heartbeat, then with 
heartbeat for a few days.

I know a re-install of bind might solve the problem but i need to know what 
caused it too :)

cheers

ernest.


More information about the Linux-HA mailing list