[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: getpeername error
- To: Hanno Foest <hurga@xxxxxxxxxxx>
- Subject: Re: getpeername error
- From: Kurt Roeckx <Q@xxxxxxx>
- Date: Sun, 14 Oct 2001 16:52:50 +0200
- Cc: ircd-users@xxxxxxx
- Delivered-to: ircd-users-out@irc.org
- Delivered-to: ircd-users@irc.org
- In-reply-to: <20011014150405.Y2303@tigress.com>; from hurga@tigress.com on Sun, Oct 14, 2001 at 03:04:05PM +0200
- References: <20011014150405.Y2303@tigress.com>
- User-agent: Mutt/1.2.5i
On Sun, Oct 14, 2001 at 03:04:05PM +0200, Hanno Foest wrote:
> Hi,
>
> I'm running ircd 2.10.3p1 on a small special interest network.
> Today my ISP has routing problems which affect only single
> IPs (defective router or something), but anyway I keep getting:
>
> getpeername for auth request netmonger.yiff.net:No route to host
>
> on &ERRORS and I can't link to that server. Well, I know that there
> are routing problems, but they shouldn't affect the IP ircd uses -
> at least traceroute says everything is fine, and the resolver seems
> to work, too.
>
> What exactly does this error indicate?
This is after a call to getpeername() to know what the remote
hosts is. This happens either after a client connects to you, or
when you connect to an other server.
I assume in your case it's the latest? The problem is that we do
a non-blocking connect(), so the connect() itself doesn't always
fail, but an other call like getpeername() might, and then
reports the error.
Kurt