BIND 4.9.5 named loops on error "write failed 32", squid to blame?

From: Gerben Wierda <>
Date: Fri, 28 Mar 97 15:30:27 +0100

Sometimes, my named starts eating a lot of CPU time. When I start it
debugging with SIGUSR1, it starts writing messages "write failed 32" to the file as fast as it can (this implies that when debugging is
default on I have the risk that my file system will be filled up....".

It looks like there is only one place where this message originates from BIND:

named/db_glue.c, line 456

The message means that there is a broken pipe and it goes on and on.

BTW, I though 4.9.5 had solved this problem (from 4.8.3), but now it seems
this is not the case.

This problem has started appearing after I have started to run squid.

--- (Gerben Wierda) NEXTSTEP RD242
"If you don't know where you're going, any road will take you there"
Paraphrased in Alice in Wonderland, originally from the Talmud.
Renee: "Met veel koper maakt men hoempa." (After hearing a Nielsen symphony)
Received on Fri Mar 28 1997 - 06:55:26 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:34:47 MST