Date: Wed, 29 Apr 1998 15:48:10 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Gary Schrock <root@eyelab.psy.msu.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: "Unable to obtain socket...." from popper? Message-ID: <Pine.BSF.3.96.980429154715.13203p-100000@gdi.uoregon.edu> In-Reply-To: <199804261921.PAA00509@eyelab.psy.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Apr 1998, Gary Schrock wrote: > Ok, I went to sleep with popper working perfectly fine, and I wake up > today with it dying with the message: > Apr 26 15:11:04 eyelab popper[432]: Unable to obtain socket and address of > client, err = 57 > Apr 26 15:11:04 eyelab popper[428]: Unable to obtain socket and address of > client, err = 57 > Apr 26 15:11:04 eyelab popper[423]: Unable to obtain socket and address of > client, err = 57 > Apr 26 15:11:05 eyelab popper[431]: Unable to obtain socket and address of > client, err = 57 > Apr 26 15:11:05 eyelab popper[425]: Unable to obtain socket and address of > client, err = 57 > Apr 26 15:11:05 eyelab popper[419]: Unable to obtain socket and address of > client, err = 57 > (This is repeated a bunch of time for every connect attempt). > > Looking through the sources, this error is caused by a call to get > getpeername failing, so I assume that the problem lies there. Hmm, error > number 57 appears to be ENOTCONN, which is odd because I would have thought > popper wouldn't even start without a connection (since it's being run from > inetd). I'd check that there are no hung poppers laying around and that the client can connect, or what the cilent gets if it gets an error. ENOTCONN woud come up if the client is bailing just after the connection but before popper gets ahold of it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980429154715.13203p-100000>