Varnish crash (SIGABRT) about every 10 mins

Gea-Suan Lin gslin at gslin.org
Fri Nov 9 01:02:36 CET 2007


On Fri, Nov 09, 2007 at 12:55:57AM +0100, Dag-Erling Sm鷨grav wrote:
> Gea-Suan Lin <gslin at gslin.org> writes:
> > gslin at testphp [~/tmp] (7:47) cat varnishd.sh
> > #!/bin/sh
> >
> > ulimit -c unlimited
> > /home/service/varnish/sbin/varnishd -a 60.199.247.118:80 -f /usr/local/etc/varnish/image.vcl -h classic,1048583 -P /var/run/varnishd.pid -s file,/home/service/varnish-cache.mmap,32G -T 127.0.0.1:11957 -t 604800 -w 32,4096 -d -d
> > gslin at testphp [~/tmp] (7:47)
> >
> > Run it and got SIGQUIT:
> >
> > Nov  9 07:43:26 testphp kernel: pid 76784 (varnishd), uid 65534: exited on signal 3
> > Nov  9 07:43:51 testphp kernel: pid 76793 (varnishd), uid 65534: exited on signal 3
> 
> Still no core file?  Try SIGABRT instead.  If that doesn't work, I'm
> out of ideas...  though you can still attach directly to the child
> with gdb.

okay I use SIGABRT now. If it still not able to generate, I'll try to
use gdb "generate-core-file" command to generate it.

-- 
* Gea-Suan Lin  (public key: Using https://keyserver.pgp.com/ to search)
* If you cannot convince them, confuse them.           -- Harry S Truman



More information about the varnish-misc mailing list