Upgrading to 6.6 can't reload
dridi at varni.sh
Fri Jun 18 13:13:28 UTC 2021
On Fri, Jun 18, 2021 at 12:24 PM Richard Chivers <r.chivers at zengenti.com> wrote:
> First post, hope this is the right place.
> I am doing some work at the moment moving our config from version 6 to 6.6, also moving from ubuntu bionic to focal.
> In the systemd configuration when we start varnish we pass the args (also many more not detailed):
> -T localhost:6082 \
> -S /etc/varnish/secret \
> We have generated an appropriate secret file etc.
> In bionic when we run a varnishadm, we don't need to pass the -T or -S args, it just reads the secret file ( I am assuming) and connects.
> In focal this is not the case, I need to pass the args. e.g. varnishadm -T localhost:6082 -S /etc/varnish/secret
> Because of this calling /usr/sbin/varnishreload fails because it calls varnishadm -n '' -- vcl.list and gets the response "No -T in shared memory"
> So my question is where does this default from, is there an ENV variable to set, or am I just missing something?
Did your system's hostname change between the moment when varnish was
started and when you attempted a reload?
Can you share the rest of your service file? (maybe redact sensitive
parts if any)
> Another strange issue is that varnishlog is not returning anything, it simply hangs and doen't show anything or an error for that matter.
> I Installed by adding the repo: deb https://packagecloud.io/varnishcache/varnish66/ubuntu/ focal main
> Any ideas or help appreciated.
> I have gone back through change logs, but can't spot anything.
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
More information about the varnish-misc