Date: Sun, 5 May 2002 11:44:37 -0700 (PDT) From: Patrick Thomas <root@utility.clubscholarship.com> To: <freebsd-hackers@freebsd.org> Subject: what would cause a server to behave this way ? Message-ID: <20020505113831.K86733-100000@utility.clubscholarship.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020505113831.K86733-100000>