[tek.walk] Varnish sometimes fails but doesn’t tell
@ tekwalk.blogspot.in [22/Oct/2012]
http://tekwalk.blogspot.in/2012/10/varnish-sometimes-fails-but-dont-tell.html
… round-robin” configuration. It was creating names that way to avoid name collision for same service running on different nodes load-balanced by Varnish-Cache.
We checked for the configuration correctness
$ varnishd -C -f /my/varnish/config/file
It passed.
We started the Varnish service
$ /etc/init.d/varnish start
It started.
We tried accessing the services via Varnish.
It failed saying there no http service running at Varnish machine:port.
…..
So, the length of backend name there does effect but the VCL gives no error when starting Varnish-Cache.
BTW, from the checks performed… the maximum character backend name working for the configuration was 44 Character long.
