Your backend is returning a 400, most probably because there's no host header in your probe.
-- Guillaume Quintard On Fri, Feb 19, 2021 at 8:53 PM Hamidreza Hosseini <[email protected]> wrote: > I correct the wrong name (It couldn't resolve from dns server), But now I > have this error: > > 0 Backend_health - boot.varnish_1 Still sick 4---X-R- 0 3 5 0.007800 > 0.000000 HTTP/1.1 400 Bad Request > > My probe: > > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 3s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > Should I change the probe request "HEAD /" to something else? > Is there any way to define special port and whenever it is accessable even > with authentication erro (error 400) it consider backend healthy? > ------------------------------ > *From:* Hamidreza Hosseini > *Sent:* Thursday, February 18, 2021 4:49 AM > *To:* [email protected] <[email protected]> > *Subject:* Varnish Health check > > Hi, > I want to adjust health check on my varnish backends, But I dont know how > can I know they are healthy or not > because the nodes are up and running and even service is up but varnish > does'nt work for all requests (just third of them are responding till I > restart it (It happens sometimes)). > How can I check this? > ``` > backend server1 { > .host = "server1.example.com"; > .probe = { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > } > ``` > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
