health check path doesn't change after VCL reload (2.0.6)

John Norman john at
Wed Feb 24 22:25:41 CET 2010

No, only the former / old path.

I'm not super-troubled right now because a Varnish restart did pick up the
new path (but at the cost of my cache) -- but I'm a bit worried about the
next time I have to change it.

I will be changing the probe interval soon, so that will give me a chance to
reproduce the problem, if it even exists.

As a bit of background:

I automate the VCL update to multiple servers, when/if the VCL file has

Before the update, I also remove all of the inactive/old VCL's that are
sitting there.

Then I add the new one and "use" it.

When I observed in my backend logs the probes going to the old URLs, I did
check the "active" VCL on all systems, and they all showed the new path.

In any case, I will try to reproduce and will send the results.

One last thing: During the restart on one system, I observed the issue
reported here:


On Wed, Feb 24, 2010 at 4:18 PM, Poul-Henning Kamp <phk at>wrote:

> In message <b6b8b6b71002241315w1c62022t1bf941d6f2cac0c7 at>,
> John N
> orman writes:
> >Still, the VCL indicated as "active" had a different path for the health
> >check.
> Hopefully both got probed ?
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the varnish-misc mailing list