From owner-freebsd-hackers Sun May 5 12:17:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by hub.freebsd.org (Postfix) with ESMTP id 2ADB237B406 for ; Sun, 5 May 2002 12:17:23 -0700 (PDT) Received: from stormspe.outloud.org (ISSA.cm.gscyclone.com [24.206.5.44]) by mail.webjockey.net (8.12.3/8.12.3) with ESMTP id g45JHEMN078218; Sun, 5 May 2002 15:17:16 -0400 (EDT) (envelope-from gary@outloud.org) Message-Id: <5.1.1.2.2.20020505151528.02f8c798@208.141.46.254> X-Sender: ancient@208.141.46.3 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1.1.3 (Beta) Date: Sun, 05 May 2002 15:17:46 -0400 To: Patrick Thomas From: Gary Stanley Subject: Re: what would cause a server to behave this way ? Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <20020505113831.K86733-100000@utility.clubscholarship.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I had that EXACT problem. I do not know the cause. 1.) Email Server 2.) Qpopper, Sendmail, the normal crap for a email server ;-) 3.) 2 times a day, or more, the server would be unresponsive. Only solution I found, was a hard reboot. I can -not- track this problem down, after going crazy over it, I moved my lusers back over to my 4.2-STABLE machine. At 11:44 AM 5/5/2002 -0700, you wrote: >We have a FreeBSD 4.5-RELEASE server, it is a SMP system, and four days >ago the following happened: > >- console became unresponsive - caps lock key no longer toggled the caps >lock button > >- you _could_ still ping the server > >- you could still establish connections to running services, but NONE of >those services would actually talk to you. They would just establish >connection and then sit there. > >Here is an example, trying to ssh into the machine: > ># ssh -v joe@example.com >SSH Version OpenSSH-2.1, protocol versions 1.5/2.0. >Compiled with SSL (0x0090581f). >debug: Reading configuration data /etc/ssh/ssh_config >debug: ssh_connect: getuid 0 geteuid 0 anon 0 >debug: Connecting to example.com [1.2.3.4] port 22. >debug: Allocated local port 890. >debug: Connection established. > > >and that is as far as it would go - just sat there forever. Same is >true with telneting to port 25 or port 110 or 53 - you would establish a >connection, but you would get no response or output from the server. > >We eventually just had to power cycle. > >--- > >So anyway, we are confused - we could still ping it, we could see that >processes (sshd server, mail server, etc.) were still running, and it even >looks like cron jobs continued to run - however, from the console it >looked like a classic hard lock (no caps light LED toggle). > >This is a fairly heavily loaded system - in `top` idle CPU usually hovers >around 60%. But we have never had any trouble in the past... > >any comments/suggestions appreciated. > >--PT > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message