From owner-freebsd-questions Thu Apr 30 09:39:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05095 for freebsd-questions-outgoing; Thu, 30 Apr 1998 09:39:37 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05077 for ; Thu, 30 Apr 1998 09:39:32 -0700 (PDT) (envelope-from root@eyelab.psy.msu.edu) Received: from iso221.psy.msu.edu (iso221.psy.msu.edu [35.8.110.61]) by eyelab.psy.msu.edu (8.8.8/8.8.7) with SMTP id MAA07781; Thu, 30 Apr 1998 12:38:06 -0400 (EDT) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <199804301638.MAA07781@eyelab.psy.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1.329 (Beta) Date: Thu, 30 Apr 1998 12:40:15 -0400 To: Doug White From: Gary Schrock Subject: Re: "Unable to obtain socket...." from popper? Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: References: <199804261921.PAA00509@eyelab.psy.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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