Getting useful information from a varnishd crash
varnish+Steven.Murdoch at cl.cam.ac.uk
Mon Apr 2 18:42:38 CEST 2007
On Mon, Apr 02, 2007 at 03:15:51PM +0000, Poul-Henning Kamp wrote:
> If you can reproduce the problem, try running varnishd in the foreground
> with -d -d options (yes, twice).
I don't know how to reproduce it. It last happened at a fairly quiet
time, so I don't think it is load related. Perhaps it was some odd
HTTP request or unlikely race condition.
It could be several weeks before the next crash, so I'm not sure what
the performance hit would be if I left it in debug mode permanently.
> >What is the best way I could use to find out what the problem is, so I
> >can either fix it or submit a useful bug report?
> Do you have a core dump ?
Unfortunately core dumps appear to have been disabled by default. I've
just enabled them for varnishd and they do seem to be generated on
SIGQUIT. Hopefully that will catch it next time around.
More information about the varnish-dev