[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:  phk
     Type:  defect         |       Status:  new
 Priority:  normal         |    Milestone:     
Component:  varnishd       |      Version:  2.0
 Severity:  normal         |   Resolution:     
 Keywords:  varnish 2.0.4  |  
---------------------------+------------------------------------------------
Changes (by phk):

  * owner:  kristian => phk
  * status:  assigned => new

Comment:

 Kristian did some investigation, and we are pretty certain that the
 problem is that the old child process is not dead, and still writes to the
 shared memory segment.

 In general, it is a bad idea to kill the varnish master process because
 the child does not do what you want, the master is there to restart the
 child if it dies, so if you killed the child process instead, you would
 get exactly the behaviour you want.

 I will look into trying to detect and spit out a sensible error message in
 this case.

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