Hi,
We have a LTSP 4.2 server running on CentOS (free RedHat clone),
running bunch of kiosks. I'm trying to rebuild the LTSP server on
faster hardware but its being a bit of a pain, as the guy who built
the original server didn't document anything at all. I've set up ltsp,
dhcpd, nfs, ypserv, gdm, etc etc.
Its *almost* working now, but when a kiosk boots up and I log in at
the login screen, it dumps me back out to the login screen. If I
enable autologin in GDM it just auto logs in every so many seconds and
dumps me back to the login screen every time, same thing as if I log
in manually.
Not sure how to troubleshoot why this is happening. Not seeing
anything in the ltsp server's log files in /var/log when this is
happening, other than when the autologins are going I see pam is
accepting that ok. I tried to SSH into the kiosk but I don't know the
root password. Per the troubleshooting docs I tried doing sudo chroot
/opt/ltsp/i386 then tried running passwd to set the root password,
only there is no passwd binary in /usr/bin/ or anywhere else, the only
file named passwd is /opt/ltsp/i386/etc/passwd (well, /etc/passwd
after the chroot)... Maybe I need to copy the real /usr/bin/passwd
into /opt/ltsp/i386/usr/bin/ to be able to set the root password once
I chroot?
I don't have Sabayon installed. I commented out the lines we wanted to
auto-run in the .Xclients file for the user the kiosk is logging in as
(kiosk10 in this case)... I've used XWindows very little
unfortunately, mostly just good old SSH terminals. I copied over the
.Xauthority files we were using on the old working box and even tried
making new ones using the xauth command (though I've just been making
up the hex values, not sure where those are supposed to come from)...
but I have a feeling that's not what the problem is.
I have even tried tarballing up /opt/ltsp and /etc/X11 as well as
/home/kiosk10 from the old working server and replacing those folders
on this new server with those, but no luck, its still kicking the
kiosk out after each login.
The dhcpd.conf is working fine, its assigning the right fixed-address
and the PXE / tftp booting is working fine.
The only errors I notice while the kiosk is booting up is its unable
to find some lib/modules/2.6.20.9-ltsp-1/modules.dep file, I haven't
gone back and tested if the working system says this too or not but
/opt/ltsp is an exact copy from there so I'm assuming it does too and
isn't the showstopper. That reminds me though, main thing I've changed
is the old server is using a slightly older ltsp kernel,
vmlinuz-2.6.17.8-ltsp-1, I updated the dhcpd.conf to use
vmlinuz-2.6.20.9-ltsp-1 instead on this new server.
Here's the lts.conf which is working fine on the old server (this new
server is on a separate segmented network but using the same IPs so I
can do a drop-in replacement once its working):
[Default]
SERVER = 10.253.34.10
XSERVER = via
X_MOUSE_PROTOCOL = "PS/2"
X_MOUSE_DEVICE = "/dev/psaux"
X_MOUSE_RESOLUTION = 400
X4_MODULE_01 = glx
X_MOUSE_BUTTONS = 3
X_MODE_0 = 640x480
USE_XFS = N
SCREEN_01 = startx
SCREEN_02 = shell
SOUND = Y
SOUND_DAEMON = esd
VOLUME = 75
CD_VOLUME = 75
LOCAL_APPS = Y
# LOCAL_APPS = N
NIS_DOMAIN = ltsp
NIS_SERVER = 10.253.34.10
X_HORZSYNC = "31-80"
X_VERTREFRESH = "60-75"
X_DPMS = N
X_DPMS_STANDBYTIME = 0
DNS_SERVER = (our local dns cache server)
X_DPMS_SUSPENDTIME = 0
X_DPMS_OFFTIME = 0
ALLOW_SHUTDOWN = Y
ALLOW_PROCREAD = Y
Thanks, and have a great weekend!
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_____________________________________________________________________
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
