[Varnish] #1697: Discard a configuration with bad character is impossible

Varnish varnish-bugs at varnish-cache.org
Tue Mar 31 14:35:20 CEST 2015


#1697: Discard a configuration with bad character is impossible
---------------------------------+------------------------
 Reporter:  vrobert              |       Type:  defect
   Status:  new                  |   Priority:  low
Milestone:  Varnish 4.0 release  |  Component:  varnishadm
  Version:  4.0.3                |   Severity:  normal
 Keywords:  discard              |
---------------------------------+------------------------
 Hi,

 we have regularly a problem with some configurations that we can not
 discard.

 These configurations have a bad char (we don't know why) and they are not
 retrieved by the discard command.

 varnishadm -T localhost:6082 -S /etc/varnish/secret vcl.list
 available       0 20150311_ofaDrupal▒2
 available       0 20150327▒_maville360_3
 active        127 20150331_devicedetect

 varnishadm -T localhost:6082 -S /etc/varnish/secret vcl.discard
 20150311_ofaDrupal▒2
 No configuration named 20150311_ofaDrupal▒2 known.
 Command failed with error code 106

 varnishadm -T localhost:6082 -S /etc/varnish/secret vcl.discard
 20150311_ofaDrupal
 No configuration named 20150311_ofaDrupal known.
 Command failed with error code 106

 The big problem is that the health check of old configurations are still
 running, putting unnecessary load on the backends.

 Do you have a workaround ?

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1697>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator



More information about the varnish-bugs mailing list