Skip to content
This repository has been archived by the owner on Aug 15, 2018. It is now read-only.

Troubleshooting 2

Jump to bottom
Dashamir Hoxha edited this page Jun 27, 2018 · 1 revision

Here is a testing plan with all the possible cases of testing for project Virtual LTSP Server. It also includes what are the possible values for the variables. What should be the scripts or commands to run, What configuration file to check if ltsp server is not working correctly.

Standalone

Server side

  • In this mode, ltsp server provides DHCP services. you can read about it here -
  • Open settings.sh with your favorite editor.
  • By default, ltsp server will be set up in standalone mode of operation. as you can see STANDALONE variable is set to yes
  • You can also change the network address and LAN_IP of the ltsp server to whatever address you want.
  • Then you should save and close the settings.sh config file.
  • Then you should run test.sh script with root permissions.
    • This script will create a virtual interface named ltsptest01 and add the interface name in settings.sh.
    • You can check it by opening the settings.sh configuration file.
    • You can also check whether the virtual interface is created or not by doing an ifconfig or ip addr.
    • You should see a virtual interface named ltsptest01.
  • After this, you can start the installation of ltsp on the vagrant box by doing a vagrant up
  • As soon as vagrant up command is complete you should check if everything is configured correctly.
  • You can do a vagrant ssh and check few configuration files.
  • Use sudo -i to get root privileges
  • First, we will check the dnsmasq
    • Open /etc/dnsmasq.d/ltsp-server-dnsmasq.conf.
    • Check for dhcp-range under the comment IP ranges to hand out. it should be in this format dhcp-range=<x.x.x>.20,<x.x.x>.250,8h. where x.x.x should be the network address from the settings.sh file.
    • Also you should check if dnsmasq service is running or not. by a service dnsmasq status. This is important because if there are any errors in the configuration file the dnsmasq service will not start.
  • Rest of the configuration files run with no errors at all.
  • Other problem may arise due to the network that you are connected
  • While using standalone mode you should make sure is no external dhcp server running.
  • If you extensively want that dhcp server then you should switch to the normal mode of operation by making changes in settings.sh

Client side

  • You can create ltsp client with running client.sh.
    • Make sure it has executable permission.
    • Also make sure it is being executed with root privileges
    • Then you can execute script with ./client.sh
  • It gets the interface name and network address from setting.sh
  • If it says could not read from the boot medium! system halted. check the net0 field.
  • If it is using an ip address other then the one defined in settings.sh then this is a network related problem
  • There is an external dhcp server providing dhcp services.
  • In this case, you can turn off the dhcp server or switch to normal mode of operation of ltsp server

Non-standalone

Server side

  • In this mode, ltsp server does not provide dhcp services. it is usually done by router or external dhcp server. you can read about it here -
  • Open settings.sh with your favorite editor.
  • By default, ltsp server is set up in standalone mode of operation. Change STANDALONE variable to no to enable non-standalone mode of operation
  • You can also change the network address and LAN_IP of the ltsp server to whatever address you want.
  • Then you should save and close the settings.sh config file.
  • Then you should run test.sh script with root permissions.
    • This script will create the virtual interface named ltsptest01 and add the interface name in settings.sh.
    • You can check it by opening the settings.sh configuration file.
    • You can also check whether the virtual interface is created or not by doing an ifconfig or ip addr.
    • You should see a virtual interface named ltsptest01.
  • After this, you can start the installation of ltsp on vagrant box by doing a vagrant up
  • As soon as vagrant up command is complete you should check if everything is configured correctly.
  • You can do a vagrant ssh and check few configuration files.
  • Use sudo -i to get root privileges
  • First we will check the dnsmasq
    • Open /etc/dnsmasq.d/ltsp-server-dnsmasq.conf.
    • Check for dhcp-range under the comment IP ranges to hand out. it should be in this format dhcp-range=x.x.x.20,x.x.x.250,8h. where x.x.x should be the network address from the settings.sh file.
    • Under that you should also see another dhcp-range. With format something like this dhcp-range=x.x.x.0,proxy where x.x.x is the network address. This makes dnsmasq provide boot information but not IP leases in the network.
    • Also you should check if dnsmasq service is running or not. by a service dnsmasq status. This is important because if there are any error in the configuration file the dnsmasq service will not start.
  • Rest of the configuration files run with no errors at all.
  • Other problem may arise due to the network that you are connected
  • While using normal mode of operation you should make sure that the external dhcp server running in the same network. Since ltsp server is not providing dhcp services. If there is no dhcp server in the network then the client will not get IP address
  • You can set up your own proxy dhcp server. open the dhcp/ directory and do a vagrant up
    • This vagrant box will provide network booting information to the client. but not provide IP address.
    • It also uses network address from the setting.sh so that it is in the same network as the ltsp-server and client.

Client side

  • You can create ltsp client with running client.sh.
    • Make sure it has executable permission.
    • Also make sure it is being executed with root privileges
    • Then you can execute script with ./client.sh
  • It gets the interface name and network address from setting.sh
  • If it does not even gets an IP address then it is then this is a network related problem
  • It is possible that dhcp server is running in a different network and ltsp server and client are in the same network
  • So one needs to run ltsp setup in the network in when dhcp server offers IP address.
Clone this wiki locally