From owner-freebsd-hackers Sat Feb 17 14:13:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA02170 for hackers-outgoing; Sat, 17 Feb 1996 14:13:22 -0800 (PST) Received: from nieuws.IAEhv.nl (nieuws.IAEhv.nl [192.87.208.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA02165 for ; Sat, 17 Feb 1996 14:13:17 -0800 (PST) Received: by nieuws.IAEhv.nl (8.6.12/1.63) id XAA28397; Sat, 17 Feb 1996 23:13:03 +0100 X-Disclaimer: iaehv.nl is a public access UNIX system and cannot be held responsible for the opinions of its individual users. Received: by adv.IAEhv.nl (8.6.11/1.63) id XAA07502; Sat, 17 Feb 1996 23:08:58 +0100 Date: Sat, 17 Feb 1996 23:08:58 +0100 From: Arjan.deVet@adv.IAEhv.nl (Arjan de Vet) Message-Id: <199602172208.XAA07502@adv.IAEhv.nl> To: taob@io.org Subject: Re: Web server locks up... but not quite. (?) X-Newsgroups: list.freebsd.hackers In-Reply-To: Organization: Internet Access Eindhoven, the Netherlands Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org Precedence: bulk In article you write: > This sort of thing has happened before with other 2.1.0-R machines >here, but tonight was the first time I was able to get to the console >of one before someone else rebooted it. [...] > You could telnet to various ports on it (indicating that inetd was >still bound to those ports), but none of the services normally >attached to those ports would run, including internal ones like >chargen or daytime (indicating that inetd was blocked in some way). >It wasn't fielding RPC requests either. The login prompt was still >displayed on all the virtual consoles (I was still able to switch >between them), but there was no response from the keyboard, as if the >getty's had died off. The only sign of life was that it was returning >pings from another machine. [...] > Since there is no indication as to the source of the hang, is >there anything I can run periodically from cron to help track down the >problem? I can start tracking load averages, swap space usage, the >output of vmstat, netstat, iostat and nfsstat if that will help. Any >suggestions? We have seen exactly these symptoms too. At one moment our main ISP machine (2.0.5) hung almost every night between 2:06h and 2:07h. We had all kinds of programs running from cron like the ones you suggest but we could not find anything strange. But because it always happened around 2:07h when /etc/daily was running we moved /etc/daily from 02:00h to 10:00h (when there's always somebody near the machine to reboot it) and the nightly hangs disappeared. They happen once in while now, around 10:07 :-((. But the real problem has not been found yet... Arjan