From owner-freebsd-questions  Fri Jun 12 08:55:19 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA05757
          for freebsd-questions-outgoing; Fri, 12 Jun 1998 08:55:19 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05538
          for <freebsd-questions@FreeBSD.ORG>; Fri, 12 Jun 1998 08:54:25 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242])
	by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id QAA05667;
	Fri, 12 Jun 1998 16:54:04 +0100 (BST)
	(envelope-from kpielorz@tdx.co.uk)
Message-ID: <35814F1D.88F66409@tdx.co.uk>
Date: Fri, 12 Jun 1998 16:54:05 +0100
From: Karl Pielorz <kpielorz@tdx.co.uk>
Organization: TDX
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: Mike Grommet <mgrommet@insolwwb.net>
CC: freebsd-questions@FreeBSD.ORG
Subject: Re: Problems with server, stops responding to incoming traffic.
References: <001401bd95a9$ac4bc3a0$0cf896d0@work2.insolwwb.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Grommet wrote:
 
> /var/log/messages
> 
> messages:Jun 11 02:02:43 ns /kernel: pid 757 (inetd), uid 0: exited on
> signal 11
> 
> at approximately the same time every night, but happens at other times too.
> 
> I can ping the machine, telnet into port 25 and apache still respoinds.  I'm
> pretty sure this is related to our router difficulties but I'm not sure how,
> or what to change.

Hi,

Signal 11's are notoriously caused by bad memory... If 'inetd' dies - you
won't be able to telnet / pop3 to the box, as inetd is the program that is
usually responsible for starting things like 'telnetd' etc. (inetd sits
around waiting for connects to these services, and spawns them accordingly).

I'd doubt it was a router problem causing this... Try reseating the RAM, or
different RAM if you have any spare...

Regards,

Karl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message