<div dir="ltr"><div>Hey, thanks for coming back to me, I have done some more work, but haven't got any further at this stage.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 21, 2021 at 9:01 AM Dridi Boukelmoune <dridi@varni.sh> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Jun 21, 2021 at 6:45 AM Richard Chivers <<a href="mailto:r.chivers@zengenti.com" target="_blank">r.chivers@zengenti.com</a>> wrote:<br>
><br>
> Hi, thanks for coming back. No, the hostname didn't change. Here is the rest of the file:<br>
><br>
> [Unit]<br>
<snip><br>
> -S /etc/varnish/secret \<br>
<br>
Can you try removing the -S option from varnishd?<br>
<br>
Since you only listen to the CLI on localhost, there's likely no<br>
remote access, so leaving the secret out will make varnishd generate a<br>
random one. Basically, if you want to use varnishadm you need local<br>
root privileges, same as your current setup.<br></blockquote><div><br></div><div>I tried this and it makes no difference, I think the fundamental issue is that calling varnishadm without args seems (regardless the args I pass to varnishd) to end in the message "No -T in shared memory" if run from root.</div><div><br></div><div>If I run from another user, I do get the message "could not get hold of varnishd, is it running?"</div><div><br></div><div>I guess I could update the reload script to pass the -T and -S args, but this seems wrong, just concerned there is a general issue on focal, Is anyone else running 6.6 on focal?</div><div><br></div><div>Looking at the source code in 6 and 6.6 I can't see anywhere that the -T would default from and yet on 6 under bionic varnishadm as a root user just works without any -T or -S flags.</div><div><br></div><div><a href="https://github.com/varnishcache/varnish-cache/blob/6.0/bin/varnishadm/varnishadm.c">https://github.com/varnishcache/varnish-cache/blob/6.0/bin/varnishadm/varnishadm.c</a> <br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<snip><br>
>> > 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.<br>
>> ><br>
>> > In focal this is not the case, I need to pass the args. e.g. varnishadm -T localhost:6082 -S /etc/varnish/secret<br>
<br>
The main entry point is the -n option, and then options (or lack<br>
thereof) like -T and -S can be found from the working directory.<br>
<br>
>> > Because of this calling /usr/sbin/varnishreload fails because it calls varnishadm -n '' -- vcl.list and gets the response "No -T in shared memory"<br>
>> ><br>
>> > So my question is where does this default from, is there an ENV variable to set, or am I just missing something?<br>
>><br>
>> Did your system's hostname change between the moment when varnish was<br>
>> started and when you attempted a reload?<br>
>><br>
>> Can you share the rest of your service file? (maybe redact sensitive<br>
>> parts if any)<br>
<br>
I didn't have time to give more details, but the default value for -n<br>
is the system's hostname, that's why I asked initially about the<br>
hostname changing.<br>
<br>
>> > Another strange issue is that varnishlog is not returning anything, it simply hangs and doen't show anything or an error for that matter.<br>
<br>
Are you running varnishlog with enough privileges? (most likely<br>
belonging at least to the varnish group.)<br>
<br>
If you omit the -d option, varnishlog will print transactions as they<br>
complete, so if by any chance you are inspecting a test system with no<br>
traffic that's not surprising.<br>
<br>
A surefire way to see whether varnishlog connects to a running varnish<br>
instance is to try:<br>
<br>
varnishlog -d -g raw<br></blockquote><div><br></div><div>I am running as root. If I execute this it connects but I get no output, I know it is connected because when I restart the varnish process I get the message, "Log abandoned (vsm)" which you always see when a new varbnishd process starts. I am definitely hitting the varnish server, as I am executing curl requests to localhost:80, but there is no output from varnishlog.</div><div><br></div><div>I am about to spin up some more boxes, so will check to see wheter this is just specific to this box or not, I did initially install 6.2 on this server and varnishlog was working as expected with that.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
>> > I Installed by adding the repo: deb <a href="https://packagecloud.io/varnishcache/varnish66/ubuntu/" rel="noreferrer" target="_blank">https://packagecloud.io/varnishcache/varnish66/ubuntu/</a> focal main<br>
>> ><br>
>> > Any ideas or help appreciated.<br>
>> ><br>
>> > I have gone back through change logs, but can't spot anything.<br>
>> ><br>
>> > Thanks<br>
>> ><br>
>> > Richard<br>
<br>
Please keep the mailing list CC'd.<br>
<br>
Dridi<br>
</blockquote></div></div>