[Varnish] #620: error message from varnish "died signal=6<131>Jan 11 03:50:17 varnishd[8785]: Child (8786) Panic message: Assert error in WSL_Flush()"

[Varnish]

#620: error message from varnish "died signal=6<131>Jan 11 03:50:17
varnishd[8785]: Child (8786) Panic message: Assert error in WSL_Flush()"
---------------------------+------------------------------------------------
 Reporter:  sprasad        |        Owner:  kristian
     Type:  defect         |       Status:  assigned
 Priority:  normal         |    Milestone:          
Component:  varnishd       |      Version:  2.0     
 Severity:  normal         |   Resolution:          
 Keywords:  varnish 2.0.4  |  
---------------------------+------------------------------------------------
Old description:

> Something happened with the varnish instance and it went down with the
> following error message, but it seems from the error message that it
> started back again. It was failing to proxy to Apache and resulting on a
> 404 till it was restarted. unfortunately no coredumps.
>
> I am running varnishd (varnish-2.0.4). compiled.
>
> uname -a
> 2.6.18-128.7.1.el5 #1 SMP Mon Aug 24 08:21:56 EDT 2009 x86_64 x86_64
> x86_64 GNU/Linux
> CentOS release 5.3 (Final)
>
> Jan 11 03:50:17 web2 varnishd[8785]: Child (8786) died signal=6<131>Jan
> 11 03:50:17 varnishd[8785]: Child (8786) Panic message: Assert error in
> WSL_Flush(), shmlog.c line 196: Condition(loghead->ptr < loghead->size)
> not true. thread = (cache-worker)sp = 0x2aaaeb317008 { fd = 10, id = 10,
> xid = 0, client = 10.4.4.5:60313, step = STP_DONE, handling = deliver, ws
> = 0x2aaaeb317078 { id = "sess", {s,f,r,e} =
> {0x2aaaeb317808,,+256,(nil),+16384}, }, worker = 0x40adcbe0 { }, },
>
> Jan 11 03:50:17 web2 varnishd[8785]: child (24840) Started
> Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said Closed fds: 4 5 6
> 11 12 14 15
> Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said Child starts
> Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said managed to mmap
> 1073741824 bytes of 1073741824
> Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said Ready
>

> Please help!

New description:

 Something happened with the varnish instance and it went down with the
 following error message, but it seems from the error message that it
 started back again. It was failing to proxy to Apache and resulting on a
 404 till it was restarted. unfortunately no coredumps.

 I am running varnishd (varnish-2.0.4). compiled.
 {{{
 uname -a
 2.6.18-128.7.1.el5 #1 SMP Mon Aug 24 08:21:56 EDT 2009 x86_64 x86_64
 x86_64 GNU/Linux
 CentOS release 5.3 (Final)

 Jan 11 03:50:17 web2 varnishd[8785]: Child (8786) died signal=6<131>Jan 11
 03:50:17 varnishd[8785]: Child (8786) Panic message: Assert error in
 WSL_Flush(), shmlog.c line 196: Condition(loghead->ptr < loghead->size)
 not true. thread = (cache-worker)sp = 0x2aaaeb317008 { fd = 10, id = 10,
 xid = 0, client = 10.4.4.5:60313, step = STP_DONE, handling = deliver, ws
 = 0x2aaaeb317078 { id = "sess", {s,f,r,e} =
 {0x2aaaeb317808,,+256,(nil),+16384}, }, worker = 0x40adcbe0 { }, },

 Jan 11 03:50:17 web2 varnishd[8785]: child (24840) Started
 Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said Closed fds: 4 5 6
 11 12 14 15
 Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said Child starts
 Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said managed to mmap
 1073741824 bytes of 1073741824
 Jan 11 03:50:17 web2 varnishd[8785]: Child (24840) said Ready
 }}}

 Please help!

Comment (by phk):

 fixed formatting

-- 
Ticket URL: <http://www.varnish-cache.org/ticket/620#comment:7>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator