<div dir="ltr">I'm running 4.1.5 using the official repo (Cent6) now:<div><br></div><div><div>Name : varnish</div><div>Arch : x86_64</div><div>Version : 4.1.5</div><div>Release : 1.el6</div><div>Size : 6.3 M</div></div><div><br></div><div>There haven't been any issues since the upgrade, and that was honestly the first panic I've had with Varnish in 3yrs+. I did notice the "Clock step detected" mentioned in the panic log, and have seen some reports of clock stepping causing issues, but there were no ntp/hwclock changes recorded at the time.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 20, 2017 at 4:09 AM, Dridi Boukelmoune <span dir="ltr"><<a href="mailto:dridi@varni.sh" target="_blank">dridi@varni.sh</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Feb 13, 2017 at 6:22 AM, Andrei <<a href="mailto:lagged@gmail.com">lagged@gmail.com</a>> wrote:<br>
> Hello all,<br>
><br>
> I woke up to numerous site timeouts, and when I went to check the backend<br>
> list, this is what was returned:<br>
><br>
> root@aviator [~]# varnishadm backend.list<br>
> Unknown request in manager process (child not running).<br>
> Type 'help' for more info.<br>
> Command failed with error code 101<br>
> root@aviator [~]#<br>
<br>
</span>This is because the child process is not running as indicated. This<br>
can be the case when you start varnish in debug mode, run something<br>
like `varnishadm stop` or hit a bug where the child doesn't restart<br>
after a panic.<br>
<span class=""><br>
> I believe it was likely related to this panic:<br>
> <a href="https://zerobin.net/?448b15259bc80551#Geo0NImD4HLpGWVZWk9raD7Qhl11VkNZEmh21J2S9mE=" rel="noreferrer" target="_blank">https://zerobin.net/?<wbr>448b15259bc80551#<wbr>Geo0NImD4HLpGWVZWk9raD7Qhl11Vk<wbr>NZEmh21J2S9mE=</a><br>
<br>
</span>It could be the panic after which the manager process failed to spawn<br>
a new child.<br>
<span class=""><br>
> Varnish has since been upgraded to 4.1.5. Should I still be worried?<br>
<br>
</span>Which version are you currently running?<br>
<span class="HOEnZb"><font color="#888888"><br>
Dridi<br>
</font></span></blockquote></div><br></div>