On Fri, Jun 08, 2001 at 01:51:04PM -0500, Petr [Dingo] Dvorak wrote: > I'm at loss here, the log from messages file looks like it had something to do > with the drives and the one that was on console looked like it was null > pointer, beside that i have no idea how to find out which process it was or > anything,
The errors you posted really look like hardware problems. Hopefully they'll be easy to isolate. Check the CPU fan and see if it's spinning and not making noises (once you've heard a dying fan, you'll know exactly what to look for). That's what bit me most recently. Grab a copy of memtest86 (any search engine will find it for you...IIRC it's hosted at sgi.com). The machine is probably dying during the nightly cron jobs because they work it relatively hard. updatedb, for example, will thrash the disk pretty hard and use a bit of CPU as it updates the locate database. It also uses quite a bit of memory, so faulty memory could cause the kernel to die when it tries paging. If that doesn't help, then you're in for a bit of work, because further problems tend to be tough to isolate. Make sure all the cables are plugged in firmly (internal cables, I mean). If you have spare parts, try swapping things like disks, CPUs, and power supplies. It's also possible that you've got a bad motherboard. Good luck. noah -- _______________________________________________________ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html
pgpozRCmJdML9.pgp
Description: PGP signature
