Hello,
was it what the kernel change fixes ?
http://aleccolocco.blogspot.co.uk/2008/11/ephemeral-ports-problem-and-solution.html
Thomas
On 23 Feb 2014, at 11:45, Vincent Bernat ber...@luffy.cx wrote:
I am too lazy to find the first kernel which works. Looking at the
commits, I have found
❦ 22 février 2014 14:55 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port as long as they don't go to the same destination ip:ports
since a connection is
Hi Vincent,
On Sun, Feb 23, 2014 at 10:25:18AM +0100, Vincent Bernat wrote:
??? 22 février 2014 14:55 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port
❦ 23 février 2014 10:31 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port as long as they don't go to the same destination ip:ports
since a connection is
On Sun, Feb 23, 2014 at 12:09:11PM +0100, Vincent Bernat wrote:
??? 23 février 2014 10:31 CET, Willy Tarreau w...@1wt.eu :
It depends if you have some servers in common or not. The system will
always allow multiple outgoing connections to share the same local
source ip:port as long as
❦ 23 février 2014 12:25 CET, Willy Tarreau w...@1wt.eu :
I suppose this is in combination with SO_REUSEADDR (otherwise, bind()
would fail). It's good to know:
tcpESTAB 0 0 192.168.116.1:3754474.125.132.104:80
tcpESTAB 0 0
On Sat, Feb 22, 2014 at 07:54:00PM +0700, Denis Malyshkin wrote:
Hi Willy,
Thank you a lot for your help.
Alternately, you can use the source parameter either on each server
or in the backend to fix a port range. Haproxy will then use an explicit
bind. This is normally used when you want
Hi Willy,
Thank you a lot for detailed answers.
Sorry for so long delay, I have to check docs, configurations and logs.
1. There are no TIME_WAIT connections on our server. They may appear for
a very short time, but there are no long-waiting ones. So in that our
system works good.
OK.
Hello Willy,
Thank you for the explanation and suggestions.
I've re-checked logs and connections.
1. There are no TIME_WAIT connections on our server. They may appear for
a very short time, but there are no long-waiting ones. So in that our
system works good.
2. What is connection retry
Hi Denis,
On Thu, Feb 06, 2014 at 12:36:05PM +0700, Denis Malyshkin wrote:
Hello Willy,
Thank you for the explanation and suggestions.
I've re-checked logs and connections.
1. There are no TIME_WAIT connections on our server. They may appear for
a very short time, but there are no
Hello all,
We have used haproxy for several months. And periodically see the next
error messages in the log:
Sep 27 16:17:06 localhost haproxy[12874]: Connect() failed for backend
https: no free ports.
Hello Denis,
On Tue, Feb 04, 2014 at 12:10:05PM +0700, Denis Malyshkin wrote:
Hello all,
We have used haproxy for several months. And periodically see the next
error messages in the log:
Sep 27 16:17:06 localhost
12 matches
Mail list logo
