I'm afraid I don't have any easy way to recreate it, other than throwing a lot of clients at it. It's perl 5.8.4 running under Linux 2.6.8. If I use the list form of accept, I get back the peer address correctly. Here's some debugging code: 

        foreach my $socket (@ready)
        {
                print STDERR "Start accept\n";
                my ($connect, $paddr) = $socket->accept();
                my ($port, $iaddr) = sockaddr_in($paddr);
                print STDERR "Peer: ", inet_ntoa($iaddr), ":$port\n";
                if ($connect)
                {
                        if (!$connect->peerhost())
                        {
                                cluck("NULL PEERHOST: " . join(" : ",
                                        $connect->sockhost(),
                                        $connect->sockport(),
                                        $connect->peerhost(),
                                        $connect->peerport(),
                                        $!
                                ));
                                close($connect);
                                print STDERR "End accept (no peerhost)
+\n";
                                next;
                        }
                        $CLIENTS->add($connect);
                        print STDERR "End accept (success)\n";
                        next;
                }
                print STDERR "End accept (no connect)\n";
        }

[download]

Output looks like this: 

Start accept
Peer: X.X.X.X:15627
NULL PEERHOST: Y.Y.Y.Y : 1235 :  :  : Transport endpoint is not connected at ./foo.pl line 115
End accept (no peerhost)
Where X.X.X.X is the client ip and Y.Y.Y.Y is my server ip. Perhaps this is an IO::Socket::INET bug?

On a related note, I'm also getting segfaults from perl under heavy load (~2500+ clients). The segfaults don't seem to be related to the null peerhosts. I believe they're occuring on syswrite() calls when I'm sending text back to the clients.

-Matt

In reply to Re^2: Transport endpoint not connected by DrManhattan
in thread Transport endpoint not connected by DrManhattan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.