Date: Mon, 4 Dec 2000 16:36:37 +0300 From: Ekaterina Ivannikova <kate@gutatelecom.ru> To: freebsd-questions@freebsd.org Subject: FreeBSD 3.4 lockup Message-ID: <20001204163637.B1297@hub.all.yans.ru>
next in thread | raw e-mail | index | archive | help
Hi All, I recently experienced a full lockup of a 3.4-RELEASE machine. The symptoms were as follows: the stack still answered pings, though no network services were available, the console driver allowed switching virtual consoles, but after typing "root" at "login:" prompt no "Password:" prompt appeared, no disk activity was observable. The logs showed nothing, except that the last syslog entry and the last squid log entry were separated by several seconds. It would seem that different procceses stopped or were killed at roughly the same time. No kernel messages were on the console. The machine is a 3.4-RELEASE + tcp-iss patch running named, postfix, squid. Ipfilter is installed. The time is kept by ntpdate which accidentally or not adjusted the time several seconds before the lockup. The box locked up solid at midnight and was no better nine hours later when it was reset. Ctrl-Alt-Del did not reboot it. Does anybody have any ideas as to what may have caused it ? I would very much like to avoid the repetition of the problem as many people are heavily dependant on this box. Regards, Ekaterina Ivannikova To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001204163637.B1297>