I recently started using a workstation with 128RAM and it happened again just yesterday.
I can't see a pattern except that all but one crash have occured on my ws.
c
[EMAIL PROTECTED] wrote:
I've been seeing alot of people lately with workstations crashing.
In the past, it's almost always been related to the workstation running out of ram, and adding more ram, or enabling nfs-swap would take care of the problem.
But, i'm wondering if there is something else going on now.
One thought is some recent modifications in GDM. Since around May of
2003, there has been a feature in GDM to constantly monitor the connection between GDM and the client X server. In fact, by default,
every 15 seconds, an X Request is sent from GDM to the Xserver.
If a reply isn't received, the connection is assumed to be dead,
and GDM will terminate it. This will have the effect that I've
been hearing about lately.
Some things that could cause the X ping to fail could be:
1) Very heavy network performance. 2) Hub or switch problems 3) cable problems
I'm not saying this is definately the cause. just that it "might" be.
The pinging that GDM is doing is there for a good reason. This solved
the problem of GDM not killing the session, if you turned off the workstation. Maybe the implementation isn't so good.
You can tune the length of the timeout, by editing /etc/X11/gdm/gdm.conf
Look for the setting 'PingIntervalSeconds'. This setting actually existed in earlier versions of GDM, but it was number of minutes, instead of number of seconds. The default is now 15 seconds, where
I think the old default value was 1 minute.
I'm unclear on whether it pings every 15 seconds and dies if it doesn't get a reply, or if it will allow upto 15 seconds of no replies, before
calling it quits.
You could try changing the value to 60, which might give the same behaviour as the old version when set to 1.
I'm not sure how to completely disable this. Maybe setting it to 0.
If I get a few free minutes, I'll take a look at the source for GDM, and see what it is really doing.
Another thought might be to switch to KDM or XDM, and see if the problem persists. At least we could rule out GDM that way.
It is also quite possible that the problems that people are seeing has nothing to do with GDM, but at least it's something to play with, to see if there is something there.
Jim McQuillan [EMAIL PROTECTED]
On Tue, 15 Jun 2004, Immanuel Derks wrote:
-----Doorgestuurd Bericht----- From: Immanuel Derks <[EMAIL PROTECTED]> To: Fraser Campbell <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] LTSP 4 and Fatal X Error- Help Please!!! Date: Tue, 15 Jun 2004 17:37:04 +0200
Jun 14 07:49:15 lts gdm[24803]: gdm_slave_xioerror_handler: Fatal X error - Restarting ws147.ltsp:0
Perhaps you can check my message at http://marc.theaimsgroup.com/?l=ltsp-discuss&m=108730513516287&w=2
and see if we have any commonality in our setups.
We have the same errors and haven't figured out yet what the cause is. Some people say this happens when the terminal runs out of memory and the remedy could be to activate swapping over nfs. It didn't help us b.t.w., but some people reported it as a working solution on the list.
We got swapping on for terminal with 64 MB ram on board and still we have the problem. Annoyingly there seems to be no regularity in when or with what client this happens.
Jim?
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _____________________________________________________________________ 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
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _____________________________________________________________________ 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
