[Varnish] #275: Varnish child stops responding

[Varnish]

#275: Varnish child  stops responding
---------------------------------+------------------------------------------
 Reporter:  chenxy               |        Owner:  phk                      
     Type:  defect               |       Status:  new                      
 Priority:  high                 |    Milestone:  Varnish 2.0 code complete
Component:  varnishd             |      Version:  trunk                    
 Severity:  normal               |   Resolution:                           
 Keywords:  Varnish child stuck  |  
---------------------------------+------------------------------------------
Comment (by chenxy):

 thank you very much.

 I use the latest version (rev 3029) , But it stop responding again, but no
 error, no assert. Sometimes a few days, sometimes a few hours.

 please download core file link : http://211.144.155.13/varnishd-
 cores.tar.gz. (57.94M)

 I will try the latest version . please wait the report again.

 run environment:
  FreeBSD/amd64 7.0-RELEASE.

  kernel: GENERIC 4BSD scheduler with softupdate by default,Not SCHED_ULE
  ( I can't reboot the server now )

  work threads: use default setting

  command:
 {{{
     varnishd -F -a 0.0.0.0:80 -f /usr/local/etc/vcl.conf \
               -u nobody -g nobody \
               -T 10.71.5.25:8080 \
               -s file,/data0/varnish/v,16G \
               -s file,/data1/varnish/v,16G \
               -s file,/data2/varnish/v,16G \
               -s file,/data3/varnish/v,16G \
               -h classic,500009 \
               -p sess_workspace=16384 -p listen_depth=4096 \
               -p lru_interval=3600 \
               -p ping_interval=10 >> $logdir/varnish.out 2>&1
 }}}

 work log:

 {{{
 Jul 28 09:54:52 236-25 varnishd[90761]: child (90766) Started
 Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said Closed fds: 7 8
 11 12 14 15
 Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said Child starts
 Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said managed to mmap
 17179869184 bytes of 17179869184
 Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said Ready
 Jul 28 13:21:07 236-25 varnishd[90761]: Child (90766) not responding to
 ping, killing it.
 Jul 28 21:21:14 236-25 kernel: pid 90766 (varnishd), uid 65534: exited on
 signal 3 (core dumped)
 Jul 28 13:21:14 236-25 varnishd[90761]: child (92810) Started
 Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said Closed fds: 7 8
 11 12 14 15
 Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said Child starts
 Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said managed to mmap
 17179869184 bytes of 17179869184
 Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said Ready
 }}}

 Varnish is not conflict with the system configuration ？ Or because http
 header（eg: cookies) ？

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/275#comment:5>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator