Date: Thu, 30 Apr 1998 12:40:15 -0400 From: Gary Schrock <root@eyelab.psy.msu.edu> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: "Unable to obtain socket...." from popper? Message-ID: <199804301638.MAA07781@eyelab.psy.msu.edu> In-Reply-To: <Pine.BSF.3.96.980429154715.13203p-100000@gdi.uoregon.edu> References: <199804261921.PAA00509@eyelab.psy.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 03:48 PM 4/29/98 -0700, you 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 >> (This is repeated a bunch of time for every connect attempt). > >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. I'm wondering if this problem might be caused by being flooded by spammail that day. I hadn't disabled relaying on the machine because of the nuissance it can be with people using pop mail programs to read/send mail, and the machine was being absolutely inundated by some idiot spammer. I'm guessing this was causing sendmail to use up all the networking resources, and as a result popper couldn't make connections (admittadly, this is wild conjecture, I honestly don't know if it could happen). Needless to say, the anti-relay check went int. Gary Schrock root@eyelab.msu.edu 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?199804301638.MAA07781>