Hi Dridi, Thanks for the input. Looking over the panic I initially linked, the exact version info was:
version = varnish-4.1.4 revision 4529ff7 ident = Linux,2.6.32-642.6.2.el6.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit,epoll I had already upgraded to 4.1.5 before mentioning the error on the list, and it's been smooth since. It was just odd that there were no clock changes, yet it panicked due to a stepping, so I figured I'd bring it up. On Mon, Feb 20, 2017 at 5:02 AM, Dridi Boukelmoune <[email protected]> wrote: > On Mon, Feb 20, 2017 at 11:22 AM, Andrei <[email protected]> wrote: > > I'm running 4.1.5 using the official repo (Cent6) now: > > > > Name : varnish > > Arch : x86_64 > > Version : 4.1.5 > > Release : 1.el6 > > Size : 6.3 M > > > > 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. > > Sorry, I misread your email, it clearly says that you are currently > running 4.1.5... What was the version when the panic occurred? > > Regarding stepping clocks, I believe that we still haven't reached a > consensus regarding how to deal with them. So you may still get a > crash for this reason. At the very least, it now tells you the reason > in the panic message. > > Dridi >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
