Hi,
while benchmarking my new web-server cluster I quickly hit the limit of
32.768 sockets in TIME_WAIT state.
I've been looking around on the internet but I'm a bit confused if this
limit can be tuned somehow or if it's an hard limit. I read about the
tcp_fin_timeout and tcp_tw_reuse/recycl
On 27.01.2012 16:01, Sebastian Fohler wrote:
Sorry just found out that I definitly do an active check.
But for some reason every second refresh of my stats shows the
servers down.
Any idea why that could be?
The servers are definitly up all that time.
Hmz, I don't know. It think it's helpful
Sorry just found out that I definitly do an active check.
But for some reason every second refresh of my stats shows the servers
down.
Any idea why that could be?
The servers are definitly up all that time.
Best regards
Sebastian
Sander Klein wrote:
Hi,
On 26.01.2012 18:45, Sebastian Fohler
Hello and thank you for your answer.
I thought it was something to do with monitor fail if but i didn't
understand that it's possible to count the number of server on a backend.
I will test this asap. and write back to the mailing list
Thanks to you for your help and thanks to the dev team of
On 27.01.2012 06:18, Sebastian Fohler wrote:
Thank you for your answer. I try the nginx part, hope it works out.
The real ip and nginx part should be fairly easy.
As far as I know I don't use active checks (at least no check
statement within my config). Should I?
Well, if you do not do any
5 matches
Mail list logo
