Varnish crash (SIGABRT) about every 10 mins

[Dag-Erling Smørgrav]

Gea-Suan Lin <gslin at gslin.org> writes:
> Program received signal SIGKILL, Killed.

Killed by the parent again.

> [Switching to Thread 0xbb4e200 (LWP 101321)]
> 0x0000000800c1716f in brk () from /lib/libc.so.6
> (gdb) bt
> #0  0x0000000800c1716f in brk () from /lib/libc.so.6
> #1  0x000000000c2f1000 in ?? ()
> #2  0x0000000800c165ba in _UTF8_init () from /lib/libc.so.6
> #3  0x0000000800c167e8 in _UTF8_init () from /lib/libc.so.6
> #4  0x0000000800c170e6 in _UTF8_init () from /lib/libc.so.6
> #5  0x0000000800c7966b in calloc () from /lib/libc.so.6
> #6  0x0000000000411262 in HSH_Prealloc (sp=0xa6dd008) at cache_hash.c:80
> #7  0x0000000000411875 in HSH_Lookup (sp=0xa6dd008) at cache_hash.c:185
> #8  0x000000000040e890 in CNT_Session (sp=0xa6dd008) at cache_center.c:534
> #9  0x0000000000416209 in wrk_thread (priv=0x53e5e0) at cache_pool.c:193
> #10 0x000000080098729e in pthread_create () from /usr/lib/libthr.so.2
> #11 0x0000000000000000 in ?? ()
> Error accessing memory address 0x7ffffd1ea000: Bad address.

This stack frame is of no interest, it is just the thread that
happened to be running when the SIGKILL was delivered.  What would be
helpful at this point is "i thr".

As previously mentioned, this will be a lot easier if you modify
mgt_child.c to send SIGQUIT instead of SIGKILL so you get a core dump.

BTW, I assume this is all on FreeBSD?  Which version?

DES
-- 
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no