[Varnish] #87: Main varnish child gets spawned again and again

[Varnish]

#87: Main varnish child gets spawned again and again
----------------------+-----------------------------------------------------
 Reporter:  Thias     |       Owner:  phk  
     Type:  defect    |      Status:  new  
 Priority:  normal    |   Milestone:       
Component:  varnishd  |     Version:  trunk
 Severity:  normal    |    Keywords:       
----------------------+-----------------------------------------------------
 Hi,

 After all the hassles on a 32bit server (found in bug #85), I've installed
 varnish on the 64bit backend server I was using. Quick details :
  * RHEL4 x86_64 w/ Linux 2.6.9-42.0.2.ELsmp
  * Same varnish package, but recompiled for x86_64
  * Varnish listening on 0.0.0.0:80
  * Lighttpd listening on 0.0.0.0:81

 Everything is "running", but the main varnish child seems to exit after a
 few seconds (less than 10), and a new one is immediately spawned. So
 things are working, but nearly no cache is kept. I can see the counter on
 the top line of varnishstart start over after 2 to 10 seconds :
 {{{
 00:00:02
 Hitrate ratio:       10      100      991
 Hitrate avg:     0.3979   0.4211   0.4395

          491       139.54       245.50 Client connections accepted
         1472       714.65       736.00 Client requests received
          501       295.03       250.50 Cache hits
            0         0.00         0.00 Cache hits for pass
          971       419.62       485.50 Cache misses
 }}}
 As you can see, it reports varnishd running for 2s, while the hitrate has
 the proper value since the start. All other values below can be seen
 "negative" during one refresh, then start increasing again from zero,
 until the next "reset".

 I can clearly see a different varnish child each time this happens :
 {{{
   742 ?        Ss     0:00 /usr/sbin/varnishd
  4254 ?        Sl     0:00  \_ /usr/sbin/varnishd
 }}}
 {{{
   742 ?        Ss     0:00 /usr/sbin/varnishd
  4330 ?        Sl     0:00  \_ /usr/sbin/varnishd
 }}}

 I don't see anything special from "varnishlog -i Debug". What should I run
 to find the cause of this problem?

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/87>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator