Bind 9 on RH9 dying

[Mueller, Rex]

David,=20

Agreed, we'd tried to start the process since it was dead. Only
rebooting brings it back.=20

I've looked at the /var/log/messages and can't find any indication of
the process going south other then getting a bunch of "lame server" and
"NXRESET"  messages it appears to be running.=20


Oct 17 04:02:22 class named[1764]: client xxx.xxx.xxx.xxx#2808: update
'xxx.net/IN'
 denied
Oct 17 04:02:23 class named[1764]: lame server resolving
'dropyourdet.com' (in '
dropyourdet.com'?): 222.134.66.53#53
Oct 17 04:02:23 class named[1764]: lame server resolving
'dropyourdet.com' (in '
dropyourdet.com'?): 211.158.35.246#53
Oct 17 04:02:27 class named[1764]: client xxx.xxx.xxx.xxx#4852: updating
zone 'xxx.net/IN': update failed: 'RRset exists (value dependent)'
prerequisite not satisfied (NXRRSET)
Oct 17 04:02:27 class named[1764]: client xxx.xxx.xxx.xxx#4855: update
'xxx.net/I
N' denied
Oct 17 04:02:29 class cups: cupsd shutdown succeeded
Oct 17 04:02:29 class modprobe: modprobe: Can't locate module
char-major-188
Oct 17 04:02:29 class last message repeated 15 times
Oct 17 04:02:29 class cups: cupsd startup succeeded




=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Rex Mueller - Systems and Security Engineer
ESU#3=20
6949 S 110th Street
LaVista, Nebraska 68128=20
rmueller at esu3 dot org=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of David Botham
Sent: Thursday, October 21, 2004 9:20 AM
To: bind-users at isc.org
Subject: Re: Bind 9 on RH9 dying

bind-users-bounce at isc.org wrote on 10/21/2004 09:56:19 AM:
> I am curious about what to look at. We've been running BIND 9 for=20
> about a year without a hitch, within the past couple of weeks the=20
> daemon has been dying for no apparent reason, we attempt to HUP the=20
> process and

Sending a signal (HUP, TERM, KILL, or otherwise) to a process that is
not running is pointless.  In other words, the process has to be running
to deal with the signal.  It is sort of like talking to someone who is
not there.

What do your logs say?

Dave...

[clip...]