On Sun, Mar 14, 2010 at 11:39 AM, Kari Matthews <[email protected]> wrote: > I just had a guy call me and tell me they couldn't get on their (newly > installed, courtesy of me) Linux server. It was on, but had "locked up" I > guess. They rebooted and it's fine now. > So now I need to go down there and try to figure out what went wrong.
Any chance of setting up a remote connection? > I have never had a linux box do that. Any ideas? Can someone give me a log > tutorial? Where do I look to see what happened? Could be anything from hardware to software or some combination. What type of service(s) is the server providing: file, web, print, mail, ssh, auth, other? How did they know the machine "locked up"? How did they know to reboot the machine? How did they reboot the machine: soft or hard? Three things come to mind when a machine has really "locked up": 1) hardware failure, e.g. bad capacitors, overheated CPU, bad power supply, 2) insufficient disk space, 3) insufficient RAM leading to thrashing. Psuedo-lockups are usually caused by X11. The system stops responding to keyboard and mouse events, and the video is frozen. This can usually be resolved by ssh'ing in and restarting X11. Good luck and let us know how things go. Regards, - Robert -- You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup To unsubscribe, reply using "remove me" as the subject.
