Whenever an LTSP terminal logs into any terminal server but the primary one
(which the terminals get their kernel and root FS from), the terminal
server dies and the terminal gets the grey screen with the "X" shaped cursor.
The servers that die don't log anything, but disappear from the chooser
menu on all terminals and refuse to accept remote connections until X is
restarted.
-----
Now, currently we have about 35 old HP terminals which can all log in to
our Vax, Alpha, and x86 machines just fine. Hoping to switch to LTSP and a
faster terminal, I have so far put one LTSP system on the network. I have a
server setup exclusively for LTSP (Sheridan), using mostly default
settings, and the new terminal (and all existing HP terminals) can log into
it perfectly.
I cannot for the life of me figure out what the new terminals (which are
just standard Jammin 125's) are doing to kill the other terminal servers,
and have absolutely no idea why they cannot log into them.
Briefly, the network setup is this:
Several Linux servers of various architectures and a few VMS systems server
various applications to 35 or so users.
Sheridan (The dedicated LTSP server), all other terminal servers, and all
existing older terminals are all directly connected via a series of
switches and have nothing but those switches between them. No server does
any IP filtering. A traceroute between any terminal (including the Jammin
125) and the server shows exactly one hop.
When the Jammin 125's boot, they get their IP, etc, from the existing
Redhat 7.1 DHCP server, which tells the terminals to get their kernel and
config, etc, from the dedicated LTSP server (Sheridan). The terminals boot
up fine and run the GDM chooser, which lists Sheridan as well as the others
(Spock, XSRUID, etc. if it matters).
I double click on Sheridan, works perfectly.
I double click on anything else, I get the grey screen, the server stops
accepting logins, and after rebooting the LTSP system that server no longer
shows up in Chooser.
I am utterly baffled as to what is going on. There is no difference in
networking between the terminals that work fine and the J125, and the
servers all must work fine with the X protocol because other terminals (as
well as Windows systems with Xfree software) can log into them without
problems (Until an LTSP terminal tries, that is).
The LTSP terminal obviously works because it can log in to Sheridan
perfectly, and be used all day.
Configuration:
------------------
In /opt/ltsp/i386/etc/rc.local I changed:
echo "/usr/X11R6/bin/${XBINARY} ${XOPTS} ${ACC_CTRL} -indirect \
${XDM_SERVER} >/dev/tty3 2>&1" >/tmp/start_ws
echo "/usr/X11R6/bin/${XBINARY} ${XOPTS} ${ACC_CTRL} -indirect \
${XDM_SERVER}" >/tmp/start_ws
(changed -query to -indirect)
lts.conf
---------------------
[Default]
SERVER = xxx.xxx.xxx.xxx
XSERVER = auto
X_MOUSE_PROTOCOL = "PS/2"
X_MOUSE_DEVICE = "/dev/psaux"
X_MOUSE_RESOLUTION = 400
X_MOUSE_BUTTONS = 3
USE_XFS = N
LOCAL_APPS = N
RUNLEVEL = 5
[ws001]
XSERVER = auto
LOCAL_APPS = N
USE_NFS_SWAP = N
SWAPFILE_SIZE = 48m
RUNLEVEL = 5
I am using the standard download kernel, the latest version of everything,
we have top quality networking hardware, etc. All servers but the Vax are
using GDM for logins. I have no idea what the vax is using.
Does anyone have any ideas? Help! I have send this to Jim of
DisklessWorkstations.com as well, but was thinking that 2000 heads are
better than 2. :)
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_____________________________________________________________________
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.openprojects.net
