<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I had the same issue on one of my caching resolvers just yesterday for the first time. This is one of the lowest utilized servers out of 6 that are all on identical hardware and identical versions of BIND (9.4.3).<div><br></div><div><span class="Apple-style-span" style="font-family: -webkit-monospace; font-size: 10px; ">Jan 14 17:46:38 wdmdc-dns-dts2 named[1415]: [ID 873579 daemon.crit] name.c:1714: INSIST(nlabels == name->labels) failed<br>Jan 14 17:46:38 wdmdc-dns-dts2 named[1415]: [ID 873579 daemon.crit] exiting (due to assertion failure)</span></div><div><font class="Apple-style-span" face="-webkit-monospace" size="2"><span class="Apple-style-span" style="font-size: 10px;"><br></span></font></div><div>One thing I CAN tell you, however, is that I was testing a script on this box earlier in the day and ran</div><div><font class="Apple-style-span" face="-webkit-monospace" size="2"><span class="Apple-style-span" style="font-size: 10px;">rndc -cache dumpdb</span></font></div><div>probably around a dozen times during the two hours I was testing the script. This would have been between 3 and 5pm that I was doing my testing and the named process died at 5:46, as you can see from the log entries.</div><div><br></div><div> -rich</div><div><font class="Apple-style-span" face="-webkit-monospace" size="2"><span class="Apple-style-span" style="font-size: 10px;"><font class="Apple-style-span" face="Helvetica" size="3"><span class="Apple-style-span" style="font-size: 12px;"><br></span></font></span></font><div><div><div>On Jan 14, 2009, at 2:35 PM, JINMEI Tatuya / 神明達哉 wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>At Wed, 14 Jan 2009 09:16:53 -0600,<br>Timothy Holtzen <<a href="mailto:tah@NebrWesleyan.edu">tah@NebrWesleyan.edu</a>> wrote:<br><br><blockquote type="cite">Last night one of our name servers stopped unexpectedly. Looking in the<br></blockquote><blockquote type="cite">logs I found the following messages.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Jan 13 20:15:01 foo named[29625]: statschannel.c:696: INSIST(xmlrc >= 0)<br></blockquote><blockquote type="cite">failed<br></blockquote><blockquote type="cite">Jan 13 20:15:01 foo named[29625]: exiting (due to assertion failure)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Anyone have any idea why this would happen or how I can keep it from<br></blockquote><blockquote type="cite">happening again? I notice that the failure is happening in<br></blockquote><br>This assertion failure was triggered due to a failure of<br>xmlTextWriterEndElement(). In the current we naively assume this<br>library call always succeed, which is, of course, a bad practice.<br>We'll eventually have to update the code to catch the error and<br>recover from it.<br><br>On the other hand, this call should normally succeed, especially in<br>the way we use it. One of few possible causes of failure I can think<br>of is a memory allocation failure occurring in the libxml2 library.<br>So, I suggest you check memory footprint of your named process. If it<br>consumes much of available memory, one possible workaround is to<br>suppress the memory usage, e.g., by adjusting max-cache-size.<br><br>---<br>JINMEI, Tatuya<br>Internet Systems Consortium, Inc.<br>_______________________________________________<br>bind-users mailing list<br><a href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a><br>https://lists.isc.org/mailman/listinfo/bind-users<br><br></div></blockquote></div><br></div></div></body></html>