On Tue, Feb 26, 2008 at 01:46:03PM +0000, Fabien COUTANT wrote: > Package: nscd > Version: 2.3.6.ds1-13etch5 > Severity: grave > Justification: renders package unusable > > This looks a lot like #451552, except the bug *still* occurs on more > recent versions. I expect this grave bug would have been fixed > _in_etch_ by the time... > > Setting debug-level to 16383 in /etc/nscd.conf, and running nscd -d in > a terminal gives the following crash before a few minutes to hours (even > when nscd was started after invalidating the caches with nscd -i): > > [...cut...] > > 10152: add new entry "adtech.panthercustomer.com" of type GETHOSTBYNAME for hosts to cache (first) > > 10152: Reloading "adtech.panthercustomer.com" in hosts cache! > > 10152: add new entry "adtech.panthercustomer.com" of type GETHOSTBYNAME for hosts to cache (first) > > 10152: Reloading "adtech.panthercustomer.com" in hosts cache! > > 10152: add new entry "adtech.panthercustomer.com" of type GETHOSTBYNAME for hosts to cache (first) > > 10152: Reloading "adtech.panthercustomer.com" in hosts cache! > > 10152: add new entry "adtech.panthercustomer.com" of type GETHOSTBYNAME for hosts to cache (first) > > 10152: Reloading "ecx.images-amazon.com" in hosts cache! > > nscd: hstcache.c:364: cache_addhst: Assertion `hst->h_addr_list[1] == ((void *)0)' failed. > > Aborted > > Of course, after the crash all networking is slowed to a pain since > name lookups aren't cached any more... and the lack of cache also has > impacts on other tables :( > > Since the process isn't rock solid, it has become unusable... one > can't go restart it every time it crashes, it would be far too often. Please don't use the hosts cache, it's documented in lenny, not in etch sadly, but it has way too many issues. If you need a lightweight *working* DNS cache, use pdnsd. Cheers, -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org
Attachment:
pgpWJWib8oeCP.pgp
Description: PGP signature