SDB:KIWI-LTSP troubleshooting

Jump to: navigation, search

Note: This page needs proper formating with tips here subdivided into sections, if you like to contribute to this project here is the place to start :)

  • To access the client terminal to debug add LDM_DEBUG_TERMINAL = True to /srv/tftpboot/KIWI/lts.conf
  • If it takes ages to get to LDM screen, disable "floppy" from your client bios
  • Post the output of ltsp-info command on and attach the resulting link to #kiwi-ltsp IRC channel or on mailing list when asking for help.
  • Post full kiwi log if failing to build images (only if you are not using -prebuilt images)
  • Make sure firewall is turned off on the network device facing the LTSP network by running yast2 firewall and marking the device as Internal Zone. Symptom of wrong firewall settings are usually TFTP timeouts.
  • Errors "Could not find /usr/share/kiwi/image/ltsp/suse-11.1/../include/" is caused by wrong SUSE_VERSION in /etc/sysconfig/kiwi-ltsp
  • Check if the IP address of the server, DHCP range and other network information is entered correctly in /etc/sysconfig/kiwi-ltsp, run kiwi-ltsp-setup -c after making sure everything in there is in order.
  • If you're having trouble creating images with kiwi-ltsp-setup, make sure you're using openSUSE i586 GM DVD. LiveCD/DVD WILL NOT WORK!
  • If the image building fails with a complaint about "package not found" add the correct installation sources, especially the one containing package you added to LOCALAPPS section.
  • Test with another client hardware if one does not boot. Try PXE booting a real desktop PC or a laptop with at least 256M RAM.
  • If things still do not work attach the full output you get on the terminal when running kiwi-ltsp-setup -c if using prebuilt image or kiwi-ltsp-setup -s if building your own image.
  • For live help you can drop into IRC Freenode #kiwi-ltsp or #ltsp, quicker solution if someone is awake.
  • Email for support on kiwi-ltsp-users
  • AUTOLOGIN - After enabling autologin your client screen will just blink when trying to start X. One possible cause of this is that you have enabled NDS/eDir logins and a second password is requested during ssh login. To see if this is the case try to ssh into the server from another machine with the user you are trying to autologin with. If, after you enter your password, you get a second "NDS Password:" request then this is the case. Solution: Edit /etc/pam.d/sshd and comment or remove the lines that end with then save the file and restart the client.
  • Server not found: tftp. Some, but not all, clients fail with this error. May be caused by a rogue (hidden, forgotten...) extra DHCP server somewhere in the network. Hint: stop the real dhcp server (as root) give: rcdhcpd stop. Then coldboot some ordinary dhcp client enabled machine and check that it does NOT receive an IP. If it does, you have an extra dhcp server somewhere, go searching. Remember to restart your original dhcp server (as root) give rcdhpd restart. If you are intentionally using an alternate DHCP server, parameters must be given to specify the TFTP server as noted on the kiwi-ltsp-user mailing list. The parameters are added to /srv/tftpboot/pxelinux.cfg/default:
  append initrd=boot/initrd-ltsp vga=791 splash=silent showopts kiwiserver= kiwiservertype=tftp
  • To see the logs in the client, do ctrl+alt+F1 on the client, scp them to the server if you want to attach with the bug report.
  • To remotely log in to the client, ssh into it, username is root, password is linux.

Testing internet connection from the client localapps:

Launch local xterm:

 ltsp-localapps xterm

Ping the server:

 ping "server ip address"

Check the route, it should show server IP address:

 ip route show

Ping some internet address to check if the ping goes through and DNS resolving works:


If it returns "Unknown host" the DNS is not working correctly, check /etc/resolv.conf to make sure "nameserver" points to the server. Alternatively you can specify DNS server of your choice by adding the following in /srv/tftpboot/KIWI/lts.conf :

  • To fix the following message when running kiwi-ltsp-setup -c:
 The following tasks need to be done manually:
 ===> No dsa key found for / , please configure the ssh server correctly and ensure that the secondary server is up.

If the sshd is not running on the server or the firewall is preventing access or sshd is not configured to use the default port 22, you may get the login screen on the client but will get a message like "No response from server". Configuration for sshd is in /etc/ssh/sshd_config.

To solve this issue, run the following as root

 insserv sshd
 rcsshd start
 kiwi-ltsp-setup -c
  • Notification for new USB stick plugged in fails due to some bug in python-notify, add the following line in /usr/lib/python2.6/site-packages/gtk-2.0/pynotify/ to workaround.
import ctypes
import sys
sys.setdlopenflags(sys.getdlopenflags() | ctypes.RTLD_GLOBAL)
import gtk
from _pynotify import *

  • If you are unable to log in to the server, i.e. you get LDM screen again after entering password, and "error: Failed to allocate internet-domain X11 display socket" on the server /var/log/messages
 Disable ipv6 on the network
 Edit /etc/ssh/sshd_config and change "AddressFamily any" to "AddressFamily inet"

See also

  • In case of slow KDE applications on the thinclients (Qt apps like Dolphin, Kate, etc...), you have to modify the rendering of the Qt graphics system. One way to do this is create a file /etc/profile.local with following in it
 export QT_GRAPHICSSYSTEM=native

Restart the thinclient and enjoy a fast ride :-) More info -> Qt Graphics System