Fair questions.
- Yes, the new hardware include different disks, and whole new OS installation;
- Yes, data was copied across. Documents and the .mozilla directory;
- Using standard IDE 40GB 7200rpm disks;
- The server ceases to respond completely. All clients lock down (can't use mouse or keyboard). Also the server locks down, no keyboard or mouse or blinking cursor on the prompt. No response to CTRL+ALT+DEL, must hard reset it to restore. No change in keyboard lights, they stay the way they were;
- Yes, the server runs X, but it is almost never used, it stays on the login screen (kdm);
- The server does not respond to ping.
Also, I had said it on a previous e-mail, another important thing is that it only locks down when there are clients connected. During weekend, when there is no one connected, the server runs smoothly. Moreover, there is no relation to the number of clients connected, it varies from one to 10 and the server locks down in every situation.
Thanks for your reponse.
[]s Ricardo.
On Sat, 18 Sep 2004 01:11:22 +0800, Craig Ringer <[EMAIL PROTECTED]> wrote:
On Fri, 2004-09-17 at 21:04, Ricardo Araújo wrote:
1) What could make a server lock that badly?
Hard to say. Some important facts you've omitted: Whether the completely new hardware included new disks (it has to be asked - I've had people tell me before "totally different server" but the moved the f***ing disks across) Whether any data was copied across, and if so what data What sort of disks you're using The way the server locks up. Does it just suddenly cease responding? Are there any flashing keyboard LEDs or not (ie is it panicing, or just locking hard)? Is there any response on the console? Does the server run X? Does the server respond to pings once it's crashed? (There are a number of cases I've encountered where a linux server will respond to ICMP and do the early SYN->SYN+ACK->ACK for TCP conns even though there is no response to keyboard input and it's otherwise unresponsive. Weird, eh?)
Tip: run 'setterm -blank 0' on a virtual console and leave that console active 24/7 with dmesg set to a very high value and syslog set to broadcast messages to that console. It can be very, very informative.
I also like to run something like 'vmstat 1 > /tmp/vmlog &' as it can get you an idea of if the server is doing anything odd before it crashes.
2) Can problems in some client cause this? If yes, could it be too old hardware (network card, maybe)?
I can't see how, but I've been in the computer industry long enough now to never, ever, ever say the "impossible" word.
3) Could it be some network problem (switches, cables)? Maybe some strange
packet that makes the server lock?
I'd be very surprised.
-- Craig Ringer
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
