ndc: error: ctl_client: evConnect(fd 3):

jayglate

Active Member
Aug 13, 2001
27
0
301
ndc: error: ctl_client: evConnect(fd 3): Connection refused ndc: error: cannot connect to command channel (/var/run/ndc)

How do we fix

I ran /scrips/fixndc
did what it said,. still no go.
 

Brownie

Well-Known Member
Aug 10, 2001
143
0
316
Well, at least I know we arent alone now ;)
 

Kiwi

Well-Known Member
Aug 11, 2001
75
0
306
ndc: error: ctl_client: evConnect(fd 3): Connection refused ndc: error: cannot connect to command channel (/var/run/ndc)

Same here :P:eek::(
 
B

bdraco

Guest
Where are you getting this error.. please make sure its a 7.1 machine.
 

DanielP

Registered
Aug 12, 2001
2
0
301
Add this to the top of your /etc/named.conf

key \"key\" {
algorithm hmac-md5;
secret \"XXXXXXXXXXXXXXXXXXXXXX\";
};

controls {
inet 127.0.0.1 allow { any; } keys { \"key\"; };
};

server 127.0.0.1
{
keys { \"key\"; };
};

In /etc/rndc.conf there will be a line similar to the secret line above

copy the secret line from it and replace the one above, restart bind and voila it works :)
 
B

bdraco

Guest
Just run /scripts/fixndc .. its updated to take care of everything now.
 

feanor

Well-Known Member
Aug 13, 2001
835
0
316
From the shell as root I\'d imagine...
SSH in, and with root access you can run anything from within /script

good luck.
 

nitromax

Well-Known Member
Feb 12, 2002
189
0
316
Same Problem Here.... /scripts/fixndc didn't work!

We are getting the same error message, but when we run /scripts/fixndc from SSH root it says this:

Found controls in named.conf ..
Found key in (include) named.conf ..
named.conf has already been fixed!

We restart bind and we still get the following error:

ndc: error: ctl_client: evConnect(fd 3): Connection refused ndc: error: cannot connect to command channel (/var/run/ndc)



Here is what the top of our file looks like:

// generated by named-bootconf.pl

options {
directory &/var/named&;
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};

//
// a caching only nameserver config
//
zone &.& IN {
type hint;
file &named.ca&;
};

zone &localhost& IN {
type master;
file &localhost.zone&;
allow-update { none; };
};


controls {
inet * allow { any; } keys { &rndc-key&; };
};

include &/etc/rndc.key&;


## Domains ##
zone &yourhostserver.com& IN {
type master;
file &yourhostserver.com.db&;
};

## Domains ##


There is nothing in the /etc/rndc.key file.