From owner-freebsd-questions@FreeBSD.ORG  Wed Apr 13 10:44:43 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C7B7116A4CE
	for <freebsd-questions@freebsd.org>;
	Wed, 13 Apr 2005 10:44:43 +0000 (GMT)
Received: from msr10.hinet.net (msr10.hinet.net [168.95.4.110])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 05DD943D2D
	for <freebsd-questions@freebsd.org>;
	Wed, 13 Apr 2005 10:44:43 +0000 (GMT)
	(envelope-from y2kbug@ms25.hinet.net)
Received: from sonic.utopia.com (61-225-170-253.dynamic.hinet.net
	[61.225.170.253])
	by msr10.hinet.net (8.9.3/8.9.3) with SMTP id SAA19284
	for <freebsd-questions@freebsd.org>;
	Wed, 13 Apr 2005 18:44:38 +0800 (CST)
Date: Wed, 13 Apr 2005 18:47:52 +0800
From: Robert Storey <y2kbug@ms25.hinet.net>
To: freebsd-questions@freebsd.org
Message-Id: <20050413184752.0a59b661.y2kbug@ms25.hinet.net>
X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: ssh dies
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2005 10:44:43 -0000

Dear All,

An interesting and disturbing problem recently appeared on our server
which is running FBSD 5.3. Rather suddenly, all users found themselves
locked out because ssh stopped working. We had to send an email to tech
support at our hosting service (Netsonic). They said this seems to be
happening frequently on many FreeBSD servers (something to do  with
reaching the limit of ssh connections). They didn't tell us how to solve
the problem, but they suggested rebooting, which should return the 
server under our control. We asked them to reboot and they did, problem
solved for now.

I'm wondering if anyone knows what is causing this, and if there is a
permanent solution? The server was running fine for four months without
issues - this just suddenly came out of the blue.

TIA,
Robert