named shuts down

[Mark.Andrews at nominum.com]

	BIND 8.2.3 fixes a problem where named sometimes sends SIGTERM 
	to itself.

	Mark

> 
> Hmm.  It's hard to say..
> 
> Seems something is actively sutting it down, rather than
> it crashing.
> 
> A few things you can do/tell:
> 
> a) What version of BIND are you running=20
> 	- 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 =
> messages
>    somewhere. You may be missing messages that are not logged due to =
> syslog
>    settings.
> 
> HTH HAND
> Mathias
> 
> > -----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
> >=20
> >=20
> > i -=20
> >=20
> > Any help with this appreciated -=20
> >=20
> > 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).
> >=20
> > 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.
> >=20
> > Here is an extract from the log:
> >=20
> > Jan 15 19:17:33 server named[22504]: XSTATS 979586253 978207452 =
> RR=3D11196
> > RNXD=3D70
> > 9 RFwdR=3D6330 RDupR=3D15 RFail=3D28 RFErr=3D0 RErr=3D2 RAXFR=3D0 =
> RLame=3D190 ROpts=3D0
> > SSysQ=3D38
> > 05 SAns=3D19345 SFwdQ=3D5765 SDupQ=3D817 SErr=3D28 RQ=3D25091 RIQ=3D16 =
> RFwdQ=3D0
> > RDupQ=3D28 RTCP
> > =3D1 SFwdR=3D6330 SFail=3D1 SFErr=3D0 SNaAns=3D13369 SNXD=3D2532
> > Jan 15 19:18:08 server named[22504]: named shutting down
> > Jan 15 19:18:08 server named[22504]: USAGE 979586288 978207452
> > CPU=3D8.78u/3.44s C
> > HILDCPU=3D0u/0s
> > Jan 15 19:18:08 server named[22504]: NSTATS 979586288 978207452 =
> A=3D6084
> > NS=3D4 CNAM
> > E=3D10 PTR=3D16918 MX=3D726 TXT=3D16 AAAA=3D61 ANY=3D1251
> > Jan 15 19:18:08 server named[22504]: XSTATS 979586288 978207452 =
> RR=3D11198
> > RNXD=3D71
> > 0 RFwdR=3D6332 RDupR=3D15 RFail=3D28 RFErr=3D0 RErr=3D2 RAXFR=3D0 =
> RLame=3D190 ROpts=3D0
> > SSysQ=3D38
> > 05 SAns=3D19345 SFwdQ=3D5767 SDupQ=3D817 SErr=3D28 RQ=3D25093 RIQ=3D16 =
> RFwdQ=3D0
> > RDupQ=3D28 RTCP
> > =3D1 SFwdR=3D6332 SFail=3D1 SFErr=3D0 SNaAns=3D13369 SNXD=3D2532
> >=20
> > How should I interpret this and should I be taking any special action =
> to
> > prevent a re-occurrence (other than a shell script to check =
> periodically
> > if named is running and restart if required)
> >=20
> > Help to a novice appreciated.
> >=20
> > Peter Rose
> > London UK
> >=20
> >=20
> > Cyberscreen Internet Services.
> > 25, Oak Hill,
> > Woodford Green,
> > Essex IG8 9NS
> > UK
> >=20
> > Tel/Fax: +44 (0)208 504 6316
> > Mobile: +44 (0)7771 987452
> > www.cyberscreen.com
> >=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