Hi all,
Yesterday we tried to get the backend probe feature of varnish to work
with zope. It failed, claiming that a response was not received.
Checking the Z2 log showed that the request was received but that zero
bytes was transferred. Using tcpdump shows that varnish closes the
connection
Hi again,
Izak Burger wrote:
I eventually distilled the check varnish uses into a small C program,
and an interesting problem shows up. When you call shutdown(fd, SHUT_WR)
on your socket connection, in effect telling zope that you're done
talking to it, it looks like zope responds in kind
Tres Seaver wrote:
You might also look at fixing varnish: I don't know of any valid
reason for it to be using the half-open connection model to test that
an HTTP-based backend is up -- certainly no browser in the world does
that; instead, modern browsers nearly always try to keep the
Leonardo Rochael Almeida wrote:
Going out on a limb here, but I think Varnish might be trying to save
on file-descriptors.
Interestingly, The Squid FAQ almost seems to imply that closing the
write-side can cause more file-descriptors to be used. Squid can
apparently not tell the difference
noticed this odd behaviour? SIGKILL seems like a very bad
idea as it does not give the process a chance to clean up, so I'm not
particularly happy about what I need to do at the moment, even if its just
development.
regards,
Izak Burger
___
Zope-Dev maillist
