On Fri, 30 Nov 2007, 19:26+0900, Adrian Chadd wrote:
> On 30/11/2007, Jan Srzednicki <[EMAIL PROTECTED]> wrote:
>
> > Most of the relevant sockets (that is, between the two host
> > mentioned) are in the ESTABLISHED state (200-400 of those). Only
> > 20-40 are in TIME_WAIT state (these tend to be
On Tue, Dec 25, 2007 at 01:30:36PM +0300, Maxim Konovalov wrote:
> On Fri, 30 Nov 2007, 19:26+0900, Adrian Chadd wrote:
>
> > Finding out more about the socket thats been created and what its
> > clashing with might help. I'd do it myself but I'm not sure how to
> > duplicate the issue.
> >
> Have
On 30/11/2007, Jan Srzednicki <[EMAIL PROTECTED]> wrote:
> Most of the relevant sockets (that is, between the two host mentioned)
> are in the ESTABLISHED state (200-400 of those). Only 20-40 are in
> TIME_WAIT state (these tend to be from a more ephemeric POP3 service). Most
> of the EADDRINUSE h
On Wed, Nov 28, 2007 at 10:42:59AM -0800, Julian Elischer wrote:
> Jan Srzednicki wrote:
>> On Wed, Nov 28, 2007 at 10:22:08AM -0800, Julian Elischer wrote:
>> How can I get any usable information from netstat? It shows a bunch of
>> connections, of course, but since connect(2) failed, I have no id
Daniel Eischen wrote:
> On Wed, 28 Nov 2007, Ivan Voras wrote:
>> This looks like the old (and probably well known) problem "ab" has.
>> ("ab" is "apache benchmark", a utility which is bundled with apache and
>> which does repeated connections to the specified address, does
>> transactions and com
On Wed, 28 Nov 2007, Ivan Voras wrote:
Jan Srzednicki wrote:
Hello,
I have a pair of hosts. One of them performs a massive amount of
TCP connections to the other one, all to the same port. This setup
mostly works fine, but from time to time (that varies, from once a
minute to one a half an hou
Jan Srzednicki wrote:
On Wed, Nov 28, 2007 at 10:22:08AM -0800, Julian Elischer wrote:
Jan Srzednicki wrote:
Hello,
I have a pair of hosts. One of them performs a massive amount of
TCP connections to the other one, all to the same port. This setup
mostly works fine, but from time to time (that
Jan Srzednicki wrote:
> Hello,
>
> I have a pair of hosts. One of them performs a massive amount of
> TCP connections to the other one, all to the same port. This setup
> mostly works fine, but from time to time (that varies, from once a
> minute to one a half an hour), the connect(2) syscall fail
Jan Srzednicki wrote:
Hello,
I have a pair of hosts. One of them performs a massive amount of
TCP connections to the other one, all to the same port. This setup
mostly works fine, but from time to time (that varies, from once a
minute to one a half an hour), the connect(2) syscall fails with
EA
On Wed, Nov 28, 2007 at 10:22:08AM -0800, Julian Elischer wrote:
> Jan Srzednicki wrote:
>> Hello,
>> I have a pair of hosts. One of them performs a massive amount of
>> TCP connections to the other one, all to the same port. This setup
>> mostly works fine, but from time to time (that varies, from
On Tue, Nov 27, 2007 at 02:53:20PM +0100, Jan Srzednicki wrote:
> Hello,
>
> setting up the relevant fields, setting SO_REUSEADDR and SO_KEEPALIVE,
> setting O_NONBLOCK on the descriptor. No bind(2) is performed. The
> connection is initiated from inside a jail (not sure if that implies a
> intern
Hello,
I have a pair of hosts. One of them performs a massive amount of
TCP connections to the other one, all to the same port. This setup
mostly works fine, but from time to time (that varies, from once a
minute to one a half an hour), the connect(2) syscall fails with
EADDRINUSE. The connection
12 matches
Mail list logo