I am not sure how a tcpdump will help in any way. Since all the health
check requests are virtually the same. Since the varnish thread that probes
the backend dies every once in a while then it will never show anything
with tcpdump or I virtually have no way to know when it will die in order
to
That code hasn't moved in a while, so I'd be surprised to see a bug there,
but that's always possible.
Any chance you could get a tcpdump of a probe request (from connection to
disconnection) so we can see what's going on?
--
Guillaume Quintard
On Mon, Apr 17, 2023 at 9:12 AM George wrote:
>
Hi,
In our case the response body is few bytes (13), header+body is 170 bytes.
Can this be a bug related to something else perhaps?
Please let me know.
Thanks
În lun., 17 apr. 2023 la 18:47, Guillaume Quintard <
guillaume.quint...@gmail.com> a scris:
> Thanks, I looked at the code quickly and
Thanks, I looked at the code quickly and I'd venture that maybe the
/varnish_check is a bit too large and doesn't fit Varnish's probe buffer
(we only care about the status line of the response anyway), so Varnish
closes the connection while nginx isn't done yet.
If it's that, it's not very
Hi,
Below is the probe "health", I forgot to send it the first time:
probe health {
.url = "/varnish_check";
.timeout = 2s;
.interval = 5s;
.window = 3;
.threshold = 2;
}
Thanks
În lun., 17 apr. 2023 la
Hi George,
Just to be sure, how is the probe "health" defined in your VCL?
Cheers,
--
Guillaume Quintard
On Mon, Apr 17, 2023 at 1:23 AM George wrote:
> Hi,
>
> I have a Varnish/nginx cluster running with varnish-7.1.2-1.el7.x86_64 on
> CentOS 7.
>
> The issue I am having comes from the
Hi,
I have a Varnish/nginx cluster running with varnish-7.1.2-1.el7.x86_64 on
CentOS 7.
The issue I am having comes from the varnish health checks. I am getting a
"broken pipe" error in the nginx error log at random times like below:
Apr 10 17:32:46 VARNISH-MASTER nginx_varnish_error: 2023/04/10
