Named stopped loging?
cathya at isc.org
Wed Jan 2 09:47:42 UTC 2013
On 28/12/12 15:54, Manson, John wrote:
> Good Day
> Running 9.9.2 for about a month now with no worries.
> Today I noticed only the reload message in the namedlog and not the zone messages that are usually there after stopping and restarting the named process.
> Worked fine on the 26th but not today.
> Logs sample:
> Dec 26 15:01:52 local at mercury named: [ID 873579 daemon.info] zone 231.143.in-addr.arpa/IN/outhouse: sending notifies (serial 1000579)
> Dec 26 15:01:52 local at mercury named: [ID 873579 daemon.info] zone jct.gov/IN/outhouse: sending notifies (serial 8000029)
> Named stopped and restarted @ Wed Dec 26 15:01:52 EST 2012.
> <No zone messages>
> Named stopped and restarted @ Fri Dec 28 10:14:31 EST 2012.
> 9.9.2 bug or what?
> No named.conf or syslog-ng changes recently.
> Using the default named logging and syslog-ng as always.
> John Manson
> US House of Representatives
> Senior Network Communications Specialist
> Desk: 202-226-4244
> TCC: 202-226-6430
I think I might be checking that there aren't two named daemons running
accidentally, or no named daemons running?
But I'm not aware of any logging problems specific to BIND 9.9.2 that
might cause this.
More information about the bind-users