Re: statschannel assertion failure

2009-02-27 Thread Timothy Holtzen
Ok, I think I've included what your looking for below. If it's not the right thing please let me know how to generate what your looking for from the core dump. I will readily admit this level of debugging isn't something I'm very familiar with. If you want to try to reproduce it I made a little

Re: statschannel assertion failure

2009-02-26 Thread JINMEI Tatuya / 神明達哉
At Thu, 26 Feb 2009 07:58:29 -0600, Timothy Holtzen wrote: > 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

Re: statschannel assertion failure

2009-02-26 Thread Timothy Holtzen
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 w

Re: statschannel assertion failure

2009-02-25 Thread JINMEI Tatuya / 神明達哉
At Wed, 25 Feb 2009 14:17:27 -0600, Timothy Holtzen 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[17030]: libxml2 Error: Input is not proper > UTF-8, indicate encoding ! > Feb 25 13:51:1

Re: statschannel assertion failure

2009-02-25 Thread Timothy Holtzen
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[17030]: libxml2 Error: Input is not proper UTF-8, indicate encoding ! Feb 25 13:51:12 arthur named[17030]: libxml2 Error: xmlTextWriterWriteDocCallback : XML

Re: statschannel assertion failure

2009-02-24 Thread JINMEI Tatuya / 神明達哉
At Tue, 24 Feb 2009 14:26:45 -0600, Timothy Holtzen wrote: > Hi guys I'm getting this assertion failure again under Bind 9.5.1-P1 on > RHEL 5.2. > > Feb 23 22:00:01 foo named[18476]: statschannel.c:696: INSIST(xmlrc >= 0) > failed > Feb 23 22:00:01 foo named[18476]: exiting (due to assertion fai

statschannel assertion failure

2009-02-24 Thread Timothy Holtzen
Hi guys I'm getting this assertion failure again under Bind 9.5.1-P1 on RHEL 5.2. Feb 23 22:00:01 foo named[18476]: statschannel.c:696: INSIST(xmlrc >= 0) failed Feb 23 22:00:01 foo named[18476]: exiting (due to assertion failure) I posted about it once before. I understand that this is caused b