Oh.... ☹
ps f -C varnishd -C cache-main
PID TTY STAT TIME COMMAND
355807 ? SLs 0:00 /usr/sbin/varnishd -j unix,user=vcache -F -a :80
-T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -p
thread_pool_min=500 -p thread_pool_max=5000 -p thread_pool_stack=4M -p
feature=+http2 -
355974 ? SLl 4:03 \_ /usr/sbin/varnishd -j unix,user=vcache -F -a
:80 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -p
thread_pool_min=500 -p thread_pool_max=5000 -p thread_pool_stack=4M -p
feature=+htt
I guess the reason is that a couple of months ago I copied system files using
rsync from another host (support), in an event of loss, so something messed up.
But this conflicts just showed it up now when I upgrade bash.
Best regards,
Hu
-----Original Message-----
From: Dridi Boukelmoune <[email protected]>
Sent: Monday, July 20, 2020 4:46 PM
To: Meken <[email protected]>
Cc: varnish-misc <[email protected]>
Subject: Re: VSM: Could not get hold of varnishd, is it running?
On Mon, Jul 20, 2020 at 8:12 AM Meken <[email protected]> wrote:
>
> Sorry!
>
> root@hosting:/var/lib/varnish# hostname hosting
So now the problem is that you removed the /var/lib/varnish/support directory
and we lost the opportunity to inspect it ¯\_(ツ)_/¯
Does the PID in /var/lib/varnish/hosting/_.pid match the root varnishd process
in the command output below?
ps f -C varnishd -C cache-main
Dridi
_______________________________________________
varnish-misc mailing list
[email protected]
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
