bind issues

[jtmcadams]

anybody know why I get this error when I try to restart bind in WHM? rndc: connect failed: connection refused

 

[jtmcadams]

if bind wasn't working then wouldn't it show as being down in service status? the status of bind shows it's up and running and when I try to restart bind in WHM it says bind restarted, Here is what shows completely when I try to restart Bind in WHM.

Attempting to restart bind

rndc: connect failed: connection refused

bind status bind did not return a status report


bind started ok

here are the results from the tail /var/log/messages

Feb 17 07:11:22 ns2 named[2121]: no IPv6 interfaces found
Feb 17 07:11:22 ns2 named[2121]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 17 07:11:22 ns2 named[2121]: listening on IPv4 interface eth0, 192.xxx.x.xxx#53
Feb 17 07:11:22 ns2 named[2121]: /etc/named.conf:19: couldn't install keys for command channel 127.0.0.1#953: not found
Feb 17 07:11:22 ns2 named[2121]: /etc/named.conf:19: couldn't add command channel 127.0.0.1#953: not found
Feb 17 07:11:22 ns2 named[2121]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Feb 17 07:11:22 ns2 named[2121]: zone ns2.namechanged.com/IN: loaded serial 1045439984
Feb 17 07:11:22 ns2 named[2121]: running
Feb 17 07:11:22 ns2 named: named startup succeeded
Feb 17 07:13:16 ns2 sshd(pam_unix)[2149]: session opened for user root by (uid=0)
[email protected] [~]# Feb 17 07:11:22 ns2 named[2121]: no IPv6 interfaces found
bash: Feb: command not found
[email protected] [~]# Feb 17 07:11:22 ns2 named[2121]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 17 07:11:22 ns2 named[2121]: listening on IPv4 interface eth0, 192.xxx.x.xxx#53
bash: Feb: command not found
[email protected] [~]# Feb 17 07:11:22 ns2 named[2121]: listening on IPv4 interface eth0, 192.xxx.x.xxx#53
bash: Feb: command not found
Feb 17 07:11:22 ns2 named[2121]: /etc/named.conf:19: couldn't add command channel 127.0.0.1#953: not found
[email protected] [~]# Feb 17 07:11:22 ns2 named[2121]: /etc/named.conf:19: couldn't install keys for command channel 127.0.0.1#953: not found
& Feb 17 07:11:22 ns2 named[2121]: /etc/named.conf:19: couldn't add command channel 127.0.0.1#953: not found
Feb 17 07:11:22 ns2 named[2121]: zone ns2.namechanged.com/IN: loaded serial 1045439984
bash: Feb: command not found
[email protected] [~]# Feb 17 07:11:22 ns2 named[2121]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
bash: Feb: command not found
Feb 17 07:11:22 ns2 named: named startup succeeded
[email protected] [~]# Feb 17 07:11:22 ns2 named[2121]: zone ns2.namechanged.com/IN: loaded serial 1045439984
Feb 17 07:13:16 ns2 sshd(pam_unix)[2149]: session opened for user root by (uid=0)
bash: Feb: command not found
[email protected] [~]# Feb 17 07:11:22 ns2 named[2121]: running
bash: Feb: command not found
[email protected] [~]# Feb 17 07:11:22 ns2 named: named startup succeeded
bash: Feb: command not found
[email protected] [~]# Feb 17 07:13:16 ns2 sshd(pam_unix)[2149]: session opened for user root by (uid=0)
bash: syntax error near unexpected token `sshd(p'

 

[dgbaker]

Run /scripts/fixndc

That should fix it.

 

[jtmcadams]

lol, i'm going to lose my mind over this. did what you last suggested and it didn't work. said found controls in named.conf, adding key, restarting bind, stopping bind, starting named, done, all fixed. tried it and got the same error, tried to run the /script/fixndc again and got named.conf has already been fixed. I also installed the ipv6 module and added alias net-pf-10 ipv6 # automatically load IPv6 module on demand
in the configuration file of the kernel module loader and that didn't help either.

I ran tail /etc/log/messages again and this is the new results

[email protected] [~]# tail /var/log/messages
Feb 17 07:47:09 ns2 named[1885]: loading configuration from '/etc/named.conf'
Feb 17 07:47:09 ns2 named[1885]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 17 07:47:09 ns2 named[1885]: listening on IPv4 interface eth0, 192.xxx.x.xxx#53
Feb 17 07:47:09 ns2 named[1885]: command channel listening on 127.0.0.1#953
Feb 17 07:47:09 ns2 named[1885]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Feb 17 07:47:09 ns2 named[1885]: zone ns2.namechanged.com/IN: loaded serial 1045439984
Feb 17 07:47:09 ns2 named[1885]: running
Feb 17 07:47:09 ns2 named: named startup succeeded
Feb 17 07:53:14 ns2 sshd(pam_unix)[1955]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=fe-0-0-nat-in.scr1.hostnoc.net user=root
Feb 17 07:53:23 ns2 sshd(pam_unix)[1955]: session opened for user root by (uid=0)
[email protected] [~]#

 

[mattschinkel]

did you ever get it fixed? I'm haveing the same problem.

# /scripts/fixndc
Found key in named.conf ..
Found controls in named.conf ..
named.conf has already been fixed!