Hi, here is the progress report for the experts, and thank you for your pointers.
Since the LTSP server uses only one physical NIC card, eth0, which has a DHCP IP address of 192.168.10.155, I ventured and set the following in the /etc/ltsp/ltsp-server.conf file: BASE="/opt/ltsp" <=== this is the default setup TFTP_BOOT_DIR="ltsp" <=== this is default LTSP_DEV=eth0 <=== changed from default eth1 to eth0 (NIC card of LTSP server using DHCP) LTSP_DEFAULTIP="192.168.10.155" <=== DHCP IP address of eth0 (netmask is 255.255.255.0) I then ran the command ltsp-build-client --release epel-6-x86_64 --debug --noprogress The installation completed this time. But it still displayed the error during the installation: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot: line 83: /opt/ltsp/x86_64/etc/sysconfig/firsboot:No such file or directory (BTW, I also looked at http://www.thefanclub.co.za/how-to/how-create-virtualbox-ubuntu-ltsp-thin-client but this only talks about the Oracle VirtualBox, but not how to install and configure LTSP on the CentOS 6.x side to make it work. Can someone please provide some pointers? I can copy+paste various config files here if needed.) I also looked at https://fedorahosted.org/k12linux/wiki/MixedNetworkSetup Here is the /etc/ltsp/dhcpd.conf file. I imagine I'll need to change various values in it. The LTSP server running CentOS 6.4 has DHCP address 192.168.10.155 and the client is coming from an Oracle VirtualBox on some laptop. [root@localhost2 ltsp]# ll /etc/ltsp/dhcpd.conf -rw-r--r--. 1 root root 944 Jun 20 09:28 /etc/ltsp/dhcpd.conf [root@localhost2 ltsp]# cat /etc/ltsp/dhcpd.conf # # Default LTSP dhcpd.conf config file. # ddns-update-style interim; ignore client-updates; allow booting; allow bootp; option option-128 code 128 = string; option option-129 code 129 = string; use-host-decl-names on; next-server 192.168.67.1; authoritative; subnet 192.168.67.0 netmask 255.255.255.0 { range 192.168.67.20 192.168.67.250; option domain-name "ltsp"; option domain-name-servers 192.168.67.1; option broadcast-address 192.168.67.255; option routers 192.168.67.1; get-lease-hostnames true; option subnet-mask 255.255.255.0; option root-path "nfs:/opt/ltsp/i386"; # Use this root-path line instead for NBD clients. Dont forget to run # ltsp-update-image! # option root-path "nbd:192.168.67.1:2000:squashfs:ro"; if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" { filename "/ltsp/i386/pxelinux.0"; } else { filename "/ltsp/i386/nbi.img"; } } FYI, this is the output of the ltsp-build-client command above: The client has been installed successfully. Now we must update the server to boot the thin client image. After that is complete have a look at /var/lib/tftpboot/ltsp/i386/lts.conf and verify everything is setup the way you want. [root@localhost2 result]# grep -in error root.log 302:DEBUG util.py:264: libgpg-error x86_64 1.7-4.el6 base 59 k 664:DEBUG util.py:264: libgpg-error.x86_64 0:1.7-4.el6 1072:DEBUG util.py:264: libgpg-error-1.7-4.el6.x86_64 [root@localhost2 result]# grep -in fail root.log [root@localhost2 result]# [root@localhost2 result]# grep -in fatal root.log [root@localhost2 result]# [root@localhost2 result]# grep -in cannot root.log [root@localhost2 result]# [root@localhost2 result]# grep -in unable root.log [root@localhost2 result]# [root@localhost2 result]# grep -in warn root.log 437:DEBUG util.py:264: warning: /etc/hosts created as /etc/hosts.rpmnew 438:DEBUG util.py:264: warning: /etc/yum.conf created as /etc/yum.conf.rpmnew [root@localhost2 result]# [root@localhost2 result]# grep -in 'return code' root.log 56:DEBUG util.py:354: Child return code was: 0 58:DEBUG util.py:354: Child return code was: 0 60:DEBUG util.py:354: Child return code was: 0 ... All zero return codes -------------------------------------------- On Tue, 6/25/13, Km - <km3...@yahoo.com> wrote: Subject: Re: [Ltsp-discuss] Fw: Re: ltsp-build-client failed after 78% completion To: ltsp-discuss@lists.sourceforge.net Date: Tuesday, June 25, 2013, 7:13 AM Hi all, it would be a great help to everybody if we can come up with some working procedures, or something that pioneers like us can run some tests and report back the issues encountered so we can figure out how to proceed or to reach the conclusion that the endeavor is not feasible. In the case of the Oracle Virtualbox or some other similar software, the Virtualbox does not have a physical NIC card, and I am not sure if it uses the same NIC card as the Windows 7 laptop NIC card or some other virtual, non-static IP address NIC with a different IP address from the laptop NIC card. Thank you for the pointers. -------------------------------------------- On Tue, 6/25/13, Radek Bursztynowski <ra...@bursztynowski.waw.pl> wrote: Subject: Re: [Ltsp-discuss] Fw: Re: ltsp-build-client failed after 78% completion To: ltsp-discuss@lists.sourceforge.net Date: Tuesday, June 25, 2013, 3:12 AM Good question! I am interested in the answer too. In general in my opinion documentation related to network configuration documentation is not clear. https://fedorahosted.org/k12linux/wiki/NetworkSetup https://fedorahosted.org/k12linux/wiki/MixedNetworkSetup I look for network solution in four cases: A. LTSP server is equipped in one NIC, and (1) physical NIC only, (2) physical NIC configured as a bridge; B. LTSP server i equipped in two NICs (3) with no bridges (one NIC dedicated to Internet connection, the second one destinated to LTSP privet network), (4) with one bridge for Internet connection and the second NIC for LTSP private network. Best regards, Radek --- Hi, I was tasked to use the Oracle Virtualbox running on windows 7 with LTSP on the server side, and download the CentOS from the LTSP server to the Oracle Virtualbox. So there will not be a private hardwired network with just the LTSP server and the thin clients only. And we can assume that the LTSP server has only one network card, which for the test environment is currently a DHCP IP address. In this case what are the appropriate values to use for the two parameters: LTSP_DEV= LTSP_DEFAULT= Thank you! -------------------------------------------- On Fri, 6/21/13, Joshua Trimm <ensla...@enslaver.com> wrote: Subject: Re: [Ltsp-discuss] Fw: Re: ltsp-build-client failed after 78% completion To: ltsp-discuss@lists.sourceforge.net Date: Friday, June 21, 2013, 7:49 AM I recommend these steps: - Clean the yum cache # yum clean all - Remove any half made and non working chroot's along with mock cache. # rm -rf /opt/ltsp/i386 /opt/ltsp/x86_64 /opt/ltsp/mock/epel-* /var/cache/mock/epel-* - Update LTSP server # yum update ltsp-server nbd ltspfs ldm ldminfod - edit /etc/ltsp/ltsp-server.conf and make sure your LTSP_DEV and LTSP_DEFAULTIP are correct # nano /etc/ltsp/ltsp-server.conf - Build the client # ltsp-build-client --debug --noprogress --release epel-6-i386 Follow any additional steps listed in the README.rpminstall Hope everything goes smooth from here on, let me know if you have any other issues. -Joshua ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _____________________________________________________________________ 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 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _____________________________________________________________________ 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 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _____________________________________________________________________ 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 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _____________________________________________________________________ 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
