[Ltsp-discuss] New installation with old config file.

Discussion:

relosrl

2014-10-13 08:40:15 UTC

I'm installing the server that will replace the old one. Installed
ubuntu 14.04 from scratch, set the network address.

apt-get install ltsp-server-standalone
I copied my old files dhcpd.conf in /etc/ltsp
ltsp-build-client --arch i386
I copied my old files lts.conf in /var/lib/tftpboot

I tried to start a remote computer and it can't connect.
What can I do to figure out what I did wrong?
Rodolfo

dhcpd.conf
#
# Default LTSP dhcpd.conf config file.
#

authoritative;

subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.11 192.168.0.20;
option domain-name "relo";
option domain-name-servers 192.168.0.10;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
server-name "192.168.0.10";
next-server 192.168.0.10;
# get-lease-hostnames true;
option subnet-mask 255.255.255.0;
option root-path "/opt/ltsp/i386";
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
} else {
filename "/ltsp/i386/nbi.img";
}

host ws001 {
hardware ethernet 00:00:00:00:00:00;
fixed-address 192.168.0.12;
}

host ws002 {
hardware ethernet 00:00:00:00:00:00;
fixed-address 192.168.0.11;
}

host ws003 {
hardware ethernet 00:00:00:00:00:00;
fixed-address 192.168.0.13;
}
}

lts.conf
# Global defaults for all clients
# if you refer to the local server, just use the
# "server" keyword as value
# see lts_parameters.txt for valid values
################
[default]
X_COLOR_DEPTH=16
LOCALDEV=True
SOUND=True
NBD_SWAP=True
SYSLOG_HOST=relosrl
XKBLAYOUT=it
LDM_DEBUG=no
LOCAL_APPS=True
LDM_DIRECTX=True

################
#[MAC ADDRESS]: Per thin client settings
################

Ivaylo Ganchev

2014-10-13 10:07:49 UTC

Permalink

Hello,

Post by relosrl
I'm installing the server that will replace the old one. Installed
ubuntu 14.04 from scratch, set the network address.
apt-get install ltsp-server-standalone
I copied my old files dhcpd.conf in /etc/ltsp
ltsp-build-client --arch i386
I copied my old files lts.conf in /var/lib/tftpboot
I tried to start a remote computer and it can't connect.
What can I do to figure out what I did wrong?
Rodolfo

Do you see in the dhcpd logs requests from the booting machine. Do you see in
the tftpd logs requests for the booting files?

What you mean by can't connect?

Regards,

--
Ivaylo Ganchev

Post by relosrl
dhcpd.conf
#
# Default LTSP dhcpd.conf config file.
#
authoritative;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.11 192.168.0.20;
option domain-name "relo";
option domain-name-servers 192.168.0.10;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
server-name "192.168.0.10";
next-server 192.168.0.10;
# get-lease-hostnames true;
option subnet-mask 255.255.255.0;
option root-path "/opt/ltsp/i386";
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
} else {
filename "/ltsp/i386/nbi.img";
}
host ws001 {
hardware ethernet 00:00:00:00:00:00;
fixed-address 192.168.0.12;
}
host ws002 {
hardware ethernet 00:00:00:00:00:00;
fixed-address 192.168.0.11;
}
host ws003 {
hardware ethernet 00:00:00:00:00:00;
fixed-address 192.168.0.13;
}
}
lts.conf
# Global defaults for all clients
# if you refer to the local server, just use the
# "server" keyword as value
# see lts_parameters.txt for valid values
################
[default]
X_COLOR_DEPTH=16
LOCALDEV=True
SOUND=True
NBD_SWAP=True
SYSLOG_HOST=relosrl
XKBLAYOUT=it
LDM_DEBUG=no
LOCAL_APPS=True
LDM_DIRECTX=True
################
#[MAC ADDRESS]: Per thin client settings
################
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_____________________________________________________________________
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

relosrl

2014-10-13 16:11:31 UTC

Permalink

Post by Ivaylo Ganchev
Hello,

Do you see in the dhcpd logs requests from the booting machine. Do you see in
the tftpd logs requests for the booting files?
What you mean by can't connect?

One problem solved, here's another one.
Your question got me thinking and I checked the dhcp service. With
version 10.04 when installed the package dhcp, it was started
automatically at boot. With 14.04 I must start by hand.

Started DHCP, booting the client, it connects to the server properly.
But I get an error:
TFTP open timeout

Where I can find tftpd logs?

Thanks.
Rodolfo

relosrl

2014-10-18 15:30:45 UTC

Permalink

Post by relosrl
One problem solved, here's another one.
Your question got me thinking and I checked the dhcp service. With
version 10.04 when installed the package dhcp, it was started
automatically at boot. With 14.04 I must start by hand.
Started DHCP, booting the client, it connects to the server properly.
TFTP open timeout
Where I can find tftpd logs?

I found a possible reason. There isn't file nbi.img in /var/lib/ltsp/i386/
It should have been created by the command ltsp-build-image --arch i386?

Rodolfo