On Thu, 14 Apr 2005, Eric Harrison wrote:
Julius Szelagiewicz wrote:
Apr 13 10:12:45 solinden gdm: Ping to ws078.turtle.com:0 failed, whacking display!
The workstation where user jszoke was forcibly logged out is ws078.
There is the guilty party right there. If the server cannot ping a terminal, after a period of time it assumes the terminal is dead and kills off the session. The default for this is 15 seconds.
You can change this value in /etc/X11/gdm/gdm.conf:
This forces me to ask some questions: 1. why it can not be pinged - when I ping it it is always fine. 2. why when this happens -nobody- can log in. Of course the answer to those question is "network problem", but I had no changes to the network from before the upgrade. julius
The first thing that jumps to my mind is an ethernet driver problem. Or maybe the RJ45 cable got kinked as you were moving the system around. Etc, etc.
I'd run dmesg, ifconfig, and scan /var/log/messages looking for anything related to the ethernet. If it is connected into a managed switch, I'd check the logs there & stats on the port. Etc, etc.
I actually had this happen to me about an hour ago! I have an old junk Netgear hub shoved under my desk that started spontaneously rebooting. I fixed mine by plugging the terminal directly into the wall ;-)
Description: OpenPGP digital signature