Bind 9.2.2

[Derek Yarger]

I installed Bind 9.2.2 yesterday on my dns master server. The named daemon quit running this morning with the following error, "exiting (due to assertion failure)". I have had bind 9.2.2 running on several other systems for nearly a month with no problems. Any ideas?????

[Geoff Wild]

Not too sure exactly - could be an issue with your "controls" statement in named.conf?

Can you post that?

Also, what's the output of:

named-checkconf

And run named-checkzone on your zone files...



Rgds...Geoff

[Mark Greene_1]

A quick peek at comp.protocols.dns.bind shows a bit of a history of this error. Evidentally a bug which induced a race condition was introduced somewhere in 9.1.X. It appears to be triggered by tcp clients, nmap, and a few other programs of the sniffer variety.

What other error messages do you have in your syslog around that time that named died? Are you running any other software on that system that you are not on any of your others?

If you go here:

http://www2.itrc.hp.com/service/patch/mainPage.do?admit=-1335382922+1054129173090+28353475

Select hp-ux, and do a keyword search on "assertion failure", you'll get a list of patches against which you can check your system's patchlevel via swinstall -v and perhaps you'll find a fix.

HTH
mark

[Steven E. Protter]

/sbin/init.d/named start > /tmp/named.txt post the text file.

What release of BIND was installed is a mystery as well.

This is the latest release from HP in depot form is this.

http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=BIND9.2

Obviously if you are using something else, you know what you are doing and have suceeded before. The error message should be apparent in syslog.log or the output from the command above.


There is a solution in these two threads.

http://forums.itrc.hp.com/cm/QuestionAnswer/0,,0x45a43fa720f3d5118ff40090279cd0f9,00.html

http://search.hp.com/redirect.html?url=http%3A//forums.itrc.hp.com/cm/QuestionAnswer/1,,0x9f0931ec5e34d711abdc0090277a778c,00.html&qt=BIND+due+to+assertion+failure&hit=3

SEP

[Derek Yarger]

thank you for the responses, I wasn't sure I would get many on this one.

I also found that this "assertion failure" is a "known" issue. The following is my controls statement:

controls {
inet 127.0.0.1 allow { 127.0.0.1; }
keys { "rndc-key"; };
};

named-checkconf and named-checkzone return no output.

I am checking on what else was running at this same time and on possible patch fixes. If I come up with anything I will definitely post it.

[Derek Yarger]

Mark/Steven,

here are errors from syslog, do these make any sense to you guys?????

May 28 06:06:27 named[14780]: resolver.c:4092: REQUIRE((((query) != 0L) && (((const isc__magic_t *)(quer
y))->magic == ((('Q') << 24 | ('!') << 16 | ('!') << 8 | ('!')))))) failed
May 28 06:06:27 named[14780]: resolver.c:4092: REQUIRE((((query) != 0L) && (((const isc__magic_t *)(quer
y))->magic == ((('Q') << 24 | ('!') << 16 | ('!') << 8 | ('!')))))) failed
May 28 06:06:27 named[14780]: exiting (due to assertion failure)
May 28 06:06:27 named[14780]: exiting (due to assertion failure)

[Geoff Wild]

Don't know if will help, but try changing your controls to this:

controls {
inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
};


As far as the syslog error - I have seen some posts about bad requests causing this to happen in Bind 9.2....

Rgds...Geoff

[Derek Yarger]

thanks Geoff,

most of what I have found on this involves errors with library files and suggested modifications. I'm going to continue to research and see what I find.

This has only happened once, definitely not a major issue.