statschannel assertion failure
tah at NebrWesleyan.edu
Thu Feb 26 13:58:29 UTC 2009
No it is a single processor on both production and test systems.
Production is an Opteron and the test system is an Athlon64 but both are
single core processors. Just to be sure I did a configured with a
--disable-threads on the test system and tried again. Testing still
triggers the exception with the same errors.
JINMEI Tatuya / 神明達哉 wrote:
> At Wed, 25 Feb 2009 14:17:27 -0600,
> Timothy Holtzen <tah at NebrWesleyan.edu> wrote:
>> I applied the patch on my test system and ran my little test using wget
>> and this is the output I got in the log
>> Feb 25 13:51:12 arthur named: libxml2 Error: Input is not proper
>> UTF-8, indicate encoding !
>> Feb 25 13:51:12 arthur named: libxml2 Error:
>> xmlTextWriterWriteDocCallback : XML error 9 !
>> Feb 25 13:51:12 arthur named: libxml2 Error: write error
>> Feb 25 13:51:12 arthur named: statschannel.c:744: INSIST(xmlrc >=
>> 0) failed
>> Feb 25 13:51:12 arthur named: exiting (due to assertion failure)
>> Since it failed with the full patch I figured removing xmlInitParser()
>> wouldn't make a difference. I decided to try anyway and got the same
> Okay, thanks for the confirmation. Are you running named with
> multiple threads on multiple processors? If so, does the situation
> change if you disable threads?
> JINMEI, Tatuya
> Internet Systems Consortium, Inc.
Timothy A. Holtzen
Campus Network Administrator
Nebraska Wesleyan University
More information about the bind-users