named shuts down

Tue Jan 16 05:13:19 UTC 2001

> 
> > 	BIND 8.2.3 fixes a problem where named sometimes sends SIGTERM=20
> > 	to itself.
> 
> But the fact that it receives a SIGTERM is logged at debug 1 or higher?

	No.  The signal handlers don't log anything.  They just set a flags
	and return.

	There are only two ways we have a graceful shutdown, as indicated
	by the message.  They are SIGTERM and "ndc stop",  "ndc restart"
	issues a "ndc stop".

> That should point out whether this is the case here, or something else
> is sending these...
> 
> 
> One more reason why I like running named out of inittab on
> production machines.. :-) (others may disagree, I know)
> 
> >=20
> > 	Mark
> >=20
> > >=20
> > > Hmm.  It's hard to say..
> > >=20
> > > Seems something is actively sutting it down, rather than
> > > it crashing.
> > >=20
> > > A few things you can do/tell:
> > >=20
> > > a) What version of BIND are you running=3D20
> > > 	- post the log messages at startup
> > > b) What environment? (O/S)
> > > c) Turn on at least debug level 1 and watch the logs
> > > d) Could any process be sending named a signal to make it shut down?
> > >    Are you running named in foreground mode attached to a shell and
> > >    it goes down when you exit?
> > > e) checkyour other logfiles, and make sure syslog logs all levels of =
> =3D
> > > messages
> > >    somewhere. You may be missing messages that are not logged due to =
> =3D
> > > syslog
> > >    settings.
> > >=20
> > > HTH HAND
> > > Mathias
> > >=20
> > > > -----Original Message-----
> > > > From: bind-users-bounce at isc.org =
> [mailto:bind-users-bounce at isc.org]On
> > > > Behalf Of Peter Rose
> > > > Sent: Tuesday, January 16, 2001 05:30
> > > > To: bind-users at isc.org
> > > > Subject: named shuts down
> > > >=3D20
> > > >=3D20
> > > > i -=3D20
> > > >=3D20
> > > > Any help with this appreciated -=3D20
> > > >=3D20
> > > > I just noticed that my named process shut down for no reason I can
> > > > discern. (Although maybe I don't run a high enough logging level).
> > > >=3D20
> > > > My log shows the usual NSTATS output up to the shutdown message,
> > > > followed by a couple of lines of stats thereafter, then the =
> process
> > > > died.
> > > >=3D20
> > > > Here is an extract from the log:
> > > >=3D20
> > > > Jan 15 19:17:33 server named[22504]: XSTATS 979586253 978207452 =
> =3D
> > > RR=3D3D11196
> > > > RNXD=3D3D70
> > > > 9 RFwdR=3D3D6330 RDupR=3D3D15 RFail=3D3D28 RFErr=3D3D0 RErr=3D3D2 =
> RAXFR=3D3D0 =3D
> > > RLame=3D3D190 ROpts=3D3D0
> > > > SSysQ=3D3D38
> > > > 05 SAns=3D3D19345 SFwdQ=3D3D5765 SDupQ=3D3D817 SErr=3D3D28 =
> RQ=3D3D25091=20
> > RIQ=3D3D16 =3D
> > > RFwdQ=3D3D0
> > > > RDupQ=3D3D28 RTCP
> > > > =3D3D1 SFwdR=3D3D6330 SFail=3D3D1 SFErr=3D3D0 SNaAns=3D3D13369 =
> SNXD=3D3D2532
> > > > Jan 15 19:18:08 server named[22504]: named shutting down
> > > > Jan 15 19:18:08 server named[22504]: USAGE 979586288 978207452
> > > > CPU=3D3D8.78u/3.44s C
> > > > HILDCPU=3D3D0u/0s
> > > > Jan 15 19:18:08 server named[22504]: NSTATS 979586288 978207452 =
> =3D
> > > A=3D3D6084
> > > > NS=3D3D4 CNAM
> > > > E=3D3D10 PTR=3D3D16918 MX=3D3D726 TXT=3D3D16 AAAA=3D3D61 =
> ANY=3D3D1251
> > > > Jan 15 19:18:08 server named[22504]: XSTATS 979586288 978207452 =
> =3D
> > > RR=3D3D11198
> > > > RNXD=3D3D71
> > > > 0 RFwdR=3D3D6332 RDupR=3D3D15 RFail=3D3D28 RFErr=3D3D0 RErr=3D3D2 =
> RAXFR=3D3D0 =3D
> > > RLame=3D3D190 ROpts=3D3D0
> > > > SSysQ=3D3D38
> > > > 05 SAns=3D3D19345 SFwdQ=3D3D5767 SDupQ=3D3D817 SErr=3D3D28 =
> RQ=3D3D25093=20
> > RIQ=3D3D16 =3D
> > > RFwdQ=3D3D0
> > > > RDupQ=3D3D28 RTCP
> > > > =3D3D1 SFwdR=3D3D6332 SFail=3D3D1 SFErr=3D3D0 SNaAns=3D3D13369 =
> SNXD=3D3D2532
> > > >=3D20
> > > > How should I interpret this and should I be taking any=20
> > special action =3D
> > > to
> > > > prevent a re-occurrence (other than a shell script to check =3D
> > > periodically
> > > > if named is running and restart if required)
> > > >=3D20
> > > > Help to a novice appreciated.
> > > >=3D20
> > > > Peter Rose
> > > > London UK
> > > >=3D20
> > > >=3D20
> > > > Cyberscreen Internet Services.
> > > > 25, Oak Hill,
> > > > Woodford Green,
> > > > Essex IG8 9NS
> > > > UK
> > > >=3D20
> > > > Tel/Fax: +44 (0)208 504 6316
> > > > Mobile: +44 (0)7771 987452
> > > > www.cyberscreen.com
> > > >=3D20
> > > >=3D20
> > >=20
> > >=20
> > >=20
> > --
> > Mark Andrews, Nominum Inc.
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: =
> Mark.Andrews at nominum.com
> >=20
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com