From owner-freebsd-hackers Thu Jul 24 05:42:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA25843 for hackers-outgoing; Thu, 24 Jul 1997 05:42:03 -0700 (PDT) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA25838 for ; Thu, 24 Jul 1997 05:41:53 -0700 (PDT) Received: (from archer@localhost) by burka.carrier.kiev.ua (8.8.5/8.who.cares.1) id OAA10007; Thu, 24 Jul 1997 14:18:09 +0300 (EEST) Message-ID: <19970724141808.22497@burka.carrier.kiev.ua> Date: Thu, 24 Jul 1997 14:18:08 +0300 From: Alexander Litvin To: hackers@freebsd.org Subject: inetd hanging Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, all! We have a problem here with FBSD2.2.2. May be, a wrong place to ask for clarification, but nevertheless... Well, sometimes -- it seems under some heavy load -- our access server ceases to accept telnets, rlogins, etc -- all stuff listed in inetd.conf. It happens not very often, but it happens. After, say, telnet, box answers "Connected to ..." -- and that's all. Sometimes kill -1 helps, sometimes not -- then it is necessary to restart inetd. It seems that kernel rather then inetd is responsible for that -- inetd -d in such a case shows nothing, that is connection is not handed to inetd (though may be I'm wrong here). netstat -rn showns a lot of sockets in FIN_WAIT state. To get more information: the box is access server, and it handles not only calls local to it, but also calls to other access servers, which hand their calls via rlogin to the central box (which I'm talking about). Other access servers are remote, and sometimes may go offline due to problems with links. I ask only for the proper direction to start searching the reason of the problem. -- Alexander Litvin Duty Postmaster, Lucky Net Ltd.