Varnish crash (SIGABRT) about every 10 mins
Gea-Suan Lin
gslin at gslin.org
Thu Nov 8 23:32:50 CET 2007
On Thu, Nov 08, 2007 at 10:21:22PM +0100, Dag-Erling Sm鷨grav wrote:
> Gea-Suan Lin <gslin at gslin.org> writes:
> > It crash again:
>
> Actually, it doesn't crash; the child get stuck somewhere and the
> parent kills it.
>
> I'd like to see an 'svn diff' of your tree.
>
> Also, if you change SIGKILL in bin/varnishd/mgt_child.c to either
> SIGABRT or SIGQUIT, you should get a core dump of the child process
> when the parent kills it. If you don't, 'ulimit -c unlimited' and try
> again.
I can see signal 3 (QUIT) from dmesg:
pid 76061 (varnishd), uid 65534: exited on signal 3
pid 76187 (varnishd), uid 65534: exited on signal 3
but I cannot find coredump. I run the following command in /tmp with
mode 1777:
sudo /usr/bin/env -i /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
And the default coredumpsize is unlimited now.
gslin at testphp [~] (6:29) limits
Resource limits (current):
cputime infinity secs
filesize infinity kB
datasize 33554432 kB
stacksize 524288 kB
coredumpsize infinity kB
memoryuse infinity kB
memorylocked infinity kB
maxprocesses 5547
openfiles 524288
sbsize infinity bytes
vmemoryuse infinity kB
gslin at testphp [~] (6:29) sudo env -i /usr/bin/limits
Resource limits (current):
cputime infinity secs
filesize infinity kB
datasize 33554432 kB
stacksize 524288 kB
coredumpsize infinity kB
memoryuse infinity kB
memorylocked infinity kB
maxprocesses 5547
openfiles 524288
sbsize infinity bytes
vmemoryuse infinity kB
Suggestion ?
--
* 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