[Varnish] #373: Varnish fails to reload backend/directory

[Varnish]

#373: Varnish fails to reload backend/directory
----------------------+-----------------------------------------------------
 Reporter:  anders    |        Owner:  phk  
     Type:  defect    |       Status:  new  
 Priority:  normal    |    Milestone:       
Component:  varnishd  |      Version:  trunk
 Severity:  normal    |   Resolution:       
 Keywords:            |  
----------------------+-----------------------------------------------------
Comment (by anders):

 Folowing up on questions from Tollef:

 {{{
 * anordby is having problems getting Varnish to update backend/director
 +runtime. New ticket, 373.
  <Mithrandir> anordby: even if you vcl.discard the old config?
 * anordby thought vcl.use would do. I can check if discard makes any
 +difference.
 <Mithrandir> we continue checking all defined backends, since you might
 +reasonably want to switch to them and having them all be down then would
 be
 +bad.
 > Well. If I have two, and I remove one from the config and reload? Then I
 +expect Varnish to stop probing the one removed.
 <Mithrandir> reload as in, vcl.load foo /etc/varnish/foo.vcl ; vcl.use foo
 ;
 +vcl.discard boot?
 <Mithrandir> or reload as in vcl.load foo /etc/varnish/foo.vcl ; vcl.use
 foo?
 }}}

 Answer: yes, I reloaded config, and discarded the old one. Varnish keeps
 checking the backend that has been commented out. An example of how I
 reloaded:

 {{{
 # telnet localhost 8080
 Trying 127.0.0.1...
 Connected to localhost.
 Escape character is '^]'.
 vcl.list
 200 69
 available       0 boot
 discarded       6 run2
 active         15 run3

 vcl.load run4 /usr/local/etc/varnish.vcl
 200 13
 VCL compiled.
 vcl.use run4
 200 0

 vcl.discard run3
 200 0

 vcl.list
 200 92
 available       0 boot
 discarded       6 run2
 discarded       3 run3
 active         12 run4

 quit
 500 22
 Closing CLI connection
 Connection closed by foreign host.
 }}}

 What I said about the host header being updated in the probe definition
 seems wrong however, you can disregard that.

 By the way: it would be nice to be able to check the status of Varnish'
 load balancing: which host is in/out, etc.

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