Re: Bind9 stopped after 34 days of uptime
On Wed, Dec 25, 2002 at 03:03:19PM +0100, InfoEmergencias - Luis Gomez wrote:
> Hi all
>
> I've been running my company's server with Linux in the same computer for
> about six months. Tonight, when I arrived home (my company is in my house) at
> about 6 a.m., I noticed I could not browse any website, and noticed that the
> DNS server (bind 9) was stopped. It was up when I left at 15.30h. I restarted
> the service and everything is OK now.
[snip]
> Well, if anyone has ever had a problem like this and can lend me a hand or
> give me some advice, I'll be very happy to hear you :-)
Apparently you can crash bind9 with a bad request. It happened to me
once so far:
Oct 31 06:29:14 polaris named[2450]: resolver.c:4030: REQUIRE((((query) != ((void *)0)) && (((const isc__magic_t *)(query))->magic == ( (('Q') << 24 | (
+'!') << 16 | ( '!') << 8 | ( '!')))))) failed
Oct 31 06:29:14 polaris named[2450]: exiting (due to assertion failure)
Oct 31 06:29:14 polaris named[2450]: resolver.c:4030: REQUIRE((((query) != ((void *)0)) && (((const isc__magic_t *)(query))->magic == ( (('Q') << 24 | (
+'!') << 16 | ( '!') << 8 | ( '!')))))) failed
Oct 31 06:29:14 polaris named[2450]: exiting (due to assertion failure)
IMHO, it should reject something like this and not quit!!!
- Adam
Reply to: