From owner-freebsd-questions Sun Apr 26 12:41:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08447 for freebsd-questions-outgoing; Sun, 26 Apr 1998 12:37:44 -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 MAA06730 for ; Sun, 26 Apr 1998 12:22:35 -0700 (PDT) (envelope-from root@eyelab.psy.msu.edu) Received: from default (pntcmi137178.voyager.net [209.153.137.178]) by eyelab.psy.msu.edu (8.8.8/8.8.7) with SMTP id PAA00509 for ; Sun, 26 Apr 1998 15:21:06 -0400 (EDT) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <199804261921.PAA00509@eyelab.psy.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1.329 (Beta) Date: Sun, 26 Apr 1998 15:14:39 -0400 To: freebsd-questions@FreeBSD.ORG From: Gary Schrock Subject: "Unable to obtain socket...." from popper? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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). The really odd thing about this is nothing about the system has changed from last night when it was working fine. So far I've tried disabling named on the system, recompiling the same version of popper, and installing a more recent version of popper. As far as I can recall I haven't changed anything on this system before this for the last few weeks, so it seems really odd taht this problem would crop up mysteriously overnight. If anyone has any suggestions I'd really appreciate them, also if you could please cc it to gschrock@voyager.net, the volume of mail I get at my main email address makes it tough to look for responses with things like elm :). Thanks, Gary Schrock root@eyelab.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message