This page is specific to Ubuntu versions 8.04, 9.04
If you find this information applicable to additional versions/releases, please edit this page and modify this header to reflect that. Please also include any necessary modifications for this information to apply to the additional versions.
BIG FAT WARNING(tm): Enabling remote syslog with more than just a couple thin-clients on your network will cause unexpected results, such as not being able to get DHCP addresses upon thin-client boot, server instability, etc... Follow these directions with this in mind and at your own risk. See Limiting which thin-clients log remotely below.
Many LTSP administrators find it cumbersome to troubleshoot thin-clients in a default LTSP setup, as many times it requires Unlocking the chroot's 'root' account, logging in and viewing logfiles directly on the thin-client. With tens (possibly hundreds) of thin-clients distributed across a network, this can get quite time consuming.
Luckily, there's a way to enable remote syslog support for thin-clients to the LTSP (or other syslog) server on the network:
You will now need to enable remote logging support on your LTSP/syslog server. This is trivial - just edit your /etc/default/syslogd file to reflect the following (as it states in the comment section of the file itself):
- ...And then reload syslog:
sudo /etc/init.d/sysklogd restart
From the syslogd manpage:
-r This option will enable the facility to receive message from the network using an internet domain socket with the syslog service (see services(5)). The default is to not receive any messages from the network.
- By default, all thin-clients will log remotely to the LTSP server. If you would like to change this to another server, edit your lts.conf file to contain the following stanza:
SYSLOG_HOST = <IP Address of syslog server>
Alternatively, you can use the following stanza if your LTSP server handles everything, including XDM_SERVER, TELNET_HOST, XFS_SERVER and SYSLOG_HOST:
SERVER = <IP Address of LTSP server>
Limiting which thin-clients log remotely
To limit which thin-clients will log remotely to the selected syslog server, you can do something like this:
Locate in the start block of the script, where 'configure_syslog || true' is located, and comment out that statement. Replace it like this:
#configure_syslog || true if [ -f /etc/hosts2syslog.txt ]; then hostname="`cat /etc/hostname`" for x in `cat /etc/hosts2syslog.txt`; do if [ $hostname = $x ]; then configure_syslog fi done fi
With that you can:
And add/remove hostnames like this:
ltsp20 #ltsp21 #ltsp22 #ltsp23 #ltsp24 #ltsp25 #ltsp26 #ltsp27
To help ensure that you get "DHCP addresses upon thin-client boot," start all the other hosts first, before the one(s) you're debugging.