ndc problem

[Joseph S D Yao]

On Sun, Jan 16, 2000 at 03:42:23PM -0800, Jim Tinlin wrote:
> Ever since I upgraded to the latest version of BIND, I've had this
> problem...
...
> **********
> Jan 16 15:32:25 cachecow named[28906]: unix control "/var/run/ndc" connect
> failed: Invalid argument
> Jan 16 15:32:25 cachecow named[28906]: ctl_server: setsockopt(REUSEADDR):
> Operation not supported on transport endpoint
> Jan 16 15:32:25 cachecow named[28906]: ctl_server: bind: Address already in
> use
> **********
> 
> This even happens when I re-boot the server.  Now here's the funny (?)
> part...I took a look at the file that ndc creates in /var/run:
> 
> srw-------   1 root     root            0 Nov 12 08:10 ndc=
> 
> The date is the last date that I restarted BIND *before* I updated it...  I
> compiled BIND on my server on 11/15...the above date is 11/12!  Now this is
> probably the root of the problem, and how would I go about getting rid of
> this file (I've tried a number of things...nothing 'simple' seems to do the
> trick)???  ...

I know of some people who thought that the name of this file is "ndc=".
If that was your problem, then you should know that it is "ndc".  What
error message - if any - do you get if, as the super-user, you try to:

	rm /var/run/ndc
	ls -l /var/run/ndc

?

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.