<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">If this is a production setup, maybe you should consider other solutions before patching / upgrading to a potentially unstable version…<div>On top of the head:</div><div>- downgrade Varnish to 3.0.0 (which seemed to work for you)</div><div>- or prevent your backends from sending vary headers (assuming you can afford to do that, and assuming this is indeed the trigger in your case)<div> <br><div><div>Either way, you should be able to get a patch from the changeset linked in the ticket (and possibly others) from here:</div><div><a href="https://www.varnish-cache.org/trac/changeset/ec3097a5d70b54fffe594cea7f3267ae7c56063b">https://www.varnish-cache.org/trac/changeset/ec3097a5d70b54fffe594cea7f3267ae7c56063b</a></div><div><br></div><div><br></div><div>Best,</div><div><br></div><div>- Olivier</div><div><br></div><div><br></div><div>Le 27 sept. 2011 à 19:34, Roberto O. Fernández Crisial a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite">Olivier,<div><br></div><div>Thank you. I've tried to upgrade from GIT instead apply patch, but it does not compile (at make I found some errors).</div><div><br></div><div>Do you have the patch url?</div><div><br></div>
<div>Regards,</div><div>Roberto.<br><br><div class="gmail_quote">2011/9/27 Olivier G <span dir="ltr"><<a href="mailto:viapanda@gmail.com">viapanda@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div style="word-wrap:break-word">Might possibly be <a href="https://www.varnish-cache.org/trac/ticket/994" target="_blank">https://www.varnish-cache.org/trac/ticket/994</a><div>Triggers for me under load when a backend sends a "Vary".</div>
<div><br></div><div>I tried to apply the patch on the ticket with no luck, and ended-up running the latest development version (which solves this).</div><div><br></div><div>2 cents</div><div><br></div><div>- Olivier</div>
<div><br></div><div><br><div><div>Le 27 sept. 2011 à 17:38, Roberto O. Fernández Crisial a écrit :</div><br><blockquote type="cite"><div><div></div><div class="h5"><div>Hi guys,</div><div><br></div><div>I just updated my server from 3.0.0 to 3.0.1 and now my messages log shows that child process exited and started as a new one over and over:</div>
<div><br></div><div>Sep 27 12:33:32 calamar14 kernel: pid 99555 (varnishd), uid 1002: exited on signal 11</div>
<div>Sep 27 15:33:32 calamar14 varnishd[99057]: Child (99555) Panic message: Assert error in http_GetHdr(), cache_http.c line 266: Condition(l == strlen(hdr + 1)) not true. thread = (cache-worker) ident = FreeBSD,8.2-RELEASE,amd64,-smalloc,-smalloc,-hcritbit,kqueue</div>
<div>Sep 27 15:33:32 calamar14 varnishd[99057]: child (99833) Started</div><div>Sep 27 15:33:32 calamar14 varnishd[99057]: Child (99833) said Child starts</div><div><br></div><div>Do you have any idea what would be happen? Any suggestion?</div>
<div><br></div><div>Thank you!</div><div><br></div><div>Roberto O. Fernández Crisial</div><div>@rofc</div></div></div>
_______________________________________________<br>varnish-misc mailing list<br><a href="mailto:varnish-misc@varnish-cache.org" target="_blank">varnish-misc@varnish-cache.org</a><br><a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a></blockquote>
</div><br></div></div></blockquote></div><br></div>
</blockquote></div><br></div></div></body></html>