Re: connect() returns EADDRINUSE during massive host->host conn rate



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
EADDRINUSE. The connection rate tops to 50 connection
initiations/second.

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 computes some statistics). AFAIK this behaviour was
present since at least 5.2, maybe earlier. No known fixes.

Attachment: signature.asc
Description: OpenPGP digital signature



Relevant Pages

  • Re: Very slow SMB performance on one interface of a multi-homed server
    ... Seven multi-homed hosts are connected to a fast ethernet office LAN on ... one interface and a private gigabit network on the other. ... Of the seven hosts, four are Windows 2000 server and three are XP. ... Connections using the office LAN and, ...
    (microsoft.public.windows.server.networking)
  • Problem with IP Masquerade and MTUs
    ... A month or so ago I started having a problem with TCP connections that just ... when connecting to hosts on the other side of my VPN ... large packets don't go through. ... which is precisely the MTU for my IPSEC interface. ...
    (comp.os.linux.networking)
  • Re: sendmail gateway overrunning my internal mailhost
    ... > internal SMTP and POP hosts. ... The sendmail server is opening connections ... have more than one gateway host. ...
    (comp.mail.sendmail)
  • Re: no RD connection, despite XP Pro on both
    ... You normally can not "browse" for RD hosts in a work group environment. ... > understand that Terminal servers were the old, ... > desktop connections. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: pix question
    ... > know PIX and IPSec well, your posting asks about 3 completely different ... > - Is 68.68.68.68 the outside interface IP of your PIX, ... > 68.68.68.68 could be a host with other hosts behind it, ... > - Are there connections that the hosts within 11.11.12.0/24 should be ...
    (comp.dcom.sys.cisco)