On Sat, Jul 18, 2020 at 8:50 PM Meken <[email protected]> wrote:
>
> I am running Ubuntu 20.04.
>
> Recently upgrade of bash (apt update && apt upgrade) causes
> varnishlog/varnishtop/varnishtop not working:
> http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 bash amd64
> 5.0-6ubuntu1.1
>
> varnishstat
> .....
> VSM: Could not get hold of varnishd, is it running?
>
> Change to" sudo varnishstat" no use
>
> (but varnish is running)
>
> Tested on Varnish 6.2.1 also 6.4 master.
>
> So it is a bug of Ubuntu or Varnish?
>
> The only fix is to roll back to cancel the upgrade.
>
> ps aux | grep varnish
>
> root 2042323 0.0 0.0 9032 736 pts/0 S+ 04:28 0:00 grep
> --color=auto varnish
>
> vcache 4055139 0.0 0.2 19148 5120 ? SLs Jul18 0:05
> /usr/sbin/varnishd -j unix,user=vcache -F -a :80 -T localhost:6082 -f
> /etc/varnish/default.vcl -S /etc/varnish/secret -t 120 -p thread_pool_min=500
> -p thread_pool_max=5000 -p thread_pool_stack=4M -p feature=+http2 -s
> malloc,20G -a [::1]:6086,PROXY
>
> vcache 4055284 0.0 4.1 4417784 84540 ? SLl Jul18 0:48
> /usr/sbin/varnishd -j unix,user=vcache -F -a :80 -T localhost:6082 -f
> /etc/varnish/default.vcl -S /etc/varnish/secret -t 120 -p thread_pool_min=500
> -p thread_pool_max=5000 -p thread_pool_stack=4M -p feature=+http2 -s
> malloc,20G -a [::1]:6086,PROXY
>
>
>
> Any idea? Thanks!
Can you share the output of the following commands?
find /var/lib/varnish -type f | sort
hostname
I suspect that your machine's hostname changed. If I'm correct, that
you can't rely on your machine's name for some reason, then it's your
job to consistently use a stable -n option across all varnish* programs.
Dridi
_______________________________________________
varnish-misc mailing list
[email protected]
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
