Re: further help on debugging a hang
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 12, 2006, at 7:57 PM, Giuliano Gavazzi wrote: A recap: - -chris zubrzycki - - -- PGP public key: http://homepage.mac.com/beren/publickey.txt ID: 0xA2ABC070 Fingerprint: 26B0 BA6B A409 FA83 42B3 1688 FBF9 8232 A2AB C070 ======================================================== "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Please sign reply-http://www.gnupg.org iEYEARECAAYFAkV/VA8ACgkQ+/mCMqKrwHDaSQCgx97a7tUTO8n8N2pWsJWgAEcO xjkAn0U7QNh+i+TuYRZZliIe/H1QK48l =/rLX -----END PGP SIGNATURE----- _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... sorry to disturb again, but the machine I am debugging cannot be left off-line too long as it is a production server (and is at a remote location), so I am looking for some advice. PowerMacG4 DP400 10.4.8 + security update 007 + ACARD 6890M SATA RAID configured for mirroring. Symptoms: every few days the machine hangs (it looks like the old "rainbow of death") remaining responsive to pings but otherwise inaccessible from both the console and ssh. Even telnet to an open tcp port (say 80) will establish the connection but the process on the other side will not respond any further (in this example a GET / HTTP/1.0 <cr> <cr> will not give anything). I have two prime suspects: the ACARD (driver or card) and lookupd. The ACARD is suspect because this is the only machine running 10.4.8 I have mounting this card and the only one suffering from these hangs. lookupd is suspect simply because the symptoms are so similar to what one would get when lookupd stops working. I would try to rule out lookupd. Maybe have it log the most verbose (but it'll spam syslog too unless you block it) and log it to a separate file, to examine after a hang. man lookupd will show the way. Also, you could kill and restart lookupd maybe every 24 hours or so. That might be enough to keep it alive, if indeed it is lookupd dying. Those are some troubleshooting methods I would use. This email sent to site_archiver@lists.apple.com
participants (1)
-
Chris Zubrzycki