Varnish Lurker is getting slower / Ban lists keeps increasing

Nils Goroll slink at
Thu Nov 30 12:30:54 UTC 2017

Hi Olivier

On 29/11/17 14:53, Olivier Hanesse wrote:
> Is is possible that the ban_lurker is locked or in an infinite loop (I know it
> is single threaded) ? What kind of dump can I provide to help understand this
> issue ? 

Basically we'd need the output of

	varnishadm ban.list

optionally a second run with

	varnishadm param.set debug +lurker

Trouble here is that, by default, the CLI interface will truncate the output
after 48k which is way too soon for any ban list of an order of magnitude as you
are seeing it.

The highest value currently accepted for the cli limit is just under 100MB,
which can be set using

	varnishadm param.set cli_limit 99999999b

As a precaution, I would advise to raise the ping timeout with such huge CLI

	varnishadm param.set cli_timeout 3600

This should be undone back to the default or whatever you had before after
gathering the data.

Feel free to send me the results via private email, bzip2 or xz compression
would probably be a good idea.


More information about the varnish-misc mailing list