[K12OSN] k12ltsp as next-server - solved

Johan Vermeulen jvermeulen at cawdekempen.be
Fri Feb 3 13:46:41 UTC 2012


hello William,

actualy, I didn't know that.

I'll have to do some more reading on the difference between the two methods.

It worked yesterday in my test environment, but today on the actual 
site, it's less successfull.
The thinclients boot ok, but no matter what I try, users or root cannot 
log in on the thinclients. LDAP auth does work on the server...
It keeps coming back with : no response from server.

grt, Johan

Op 02-02-12 18:41, William Fragakis schreef:
> Johan,
> Glad it worked out for you. You probably want to comment out
> the root-path you aren't using as it is redundant and will confuse
> things if someone is trying
> debug/change things in the future.
>
> I don't know enough about how dhcpd.conf is read to say if the first or
> last one is respected. iirc,
> nbd works better for larger installations. So maybe something like
>
> option root-path "nbd:192.168.66.150:2000:squashfs:ro";
> # option root-path "192.168.66.150:/opt/ltsp/i386";
>
> You probably already know that if you make any changes to the chroot
> like yum update or installing local apps, you'll need to run
> ltsp-update-kernels for the nbd image to be updated. You don't need to
> do that if you are booting from /opt/ltsp/i386
>
> Good luck,
> William
>
>
>
>> ontent-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>>
>> William,
>>
>> this solved my problem.
>>
>> My dhcpd.conf on the first server now is:
>>
>> *group {
>> next-server 192.168.66.150;
>> filename "ltsp/i386/pxelinux.0";
>> option root-path "nbd:192.168.66.150:2000:squashfs:ro";
>> option root-path "192.168.66.150:/opt/ltsp/i386";
>>
>> host testtc {
>> hardware ethernet 00:22:64:29:a9:4e;
>> fixed-address 192.168.66.156;
>> }
>> }
>>
>> *this did the trick.
>>
>> Thank you Wiliam !
>>
>> greetings, J
>>
>>
>> Op 31-01-12 18:41, William Fragakis schreef:
>>> Johan,
>>> Hopefully, the following is correct and helpful.
>>>
>>> Have you set the correct option-path for the kernel in dhcpd.conf?
>>>
>>> It will probably look like this for you, if *.66.150 is where the ltsp
>>> kernels are
>>>
>>>    option root-path "192.168.66.150:/opt/ltsp/i386";
>>> or if you are using nbd
>>> option root-path "nbd:192.168.66.150:2000:squashfs:ro";
>>>
>>> filename "/ltsp/i386/pxelinux.0"; only is for the pxe image. From there,
>>> it needs to find its full kernel to finish booting
>>>
>>> also, you will have to edit
>>> /opt/ltsp/i386/usr/sbin/ltsp-client-launch
>>> if you want your clients to connect to *.66.150 or anything other than
>>> the default ip from install for the ldm session.
>>> look for the server variable on line 46.
>>>
>>> Regards,
>>> William
>>>
>>>> Message: 1
>>>> Date: Mon, 30 Jan 2012 19:29:35 +0100
>>>> From: Johan Vermeulen<jvermeulen at cawdekempen.be>
>>>> To: "Support list for open source software in schools."
>>>> 	<k12osn at redhat.com>
>>>> Subject: [K12OSN] k12ltsp as next-server
>>>> Message-ID:<4F26E18F.4070907 at cawdekempen.be>
>>>> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>>>>
>>>> dear All,
>>>>
>>>> I'm trying to set up a K12Ltsp server on Centos6.2 as next-server behind
>>>> an OpenSuse11.1 Kiwi-ltsp server.
>>>> So everybody on this site boots from the Kiwi-ltsp machine, but I want
>>>> to put some users on the newer CentOs-server.
>>>>
>>>>
>>>> So in /etc/dhcpd.conf on the Kiwi-ltsp machine it says:
>>>>
>>>> *group {
>>>> next-server 192.168.66.150;
>>>> filename "/ltsp/i386/pxelinux.0";
>>>>
>>>> host testtc {
>>>> hardware ethernet 00:22:64:29:a9:4e;
>>>> fixed-address 192.168.66.156;
>>>> }
>>>> }*
>>>>
>>>> next-server being the K12ltsp machine.
>>>> host testtc, the test thinclient, is a Hp thinclient attached to the
>>>> Kiwi-ltsp machine.
>>>>
>>>> The K12ltsp setup on the Centos6.2 machine is completely new installed
>>>> and exactly like it's explained on the site.
>>>> So firewall is off.
>>>>
>>>> The thinclient gets an dhcp address and begins booting, then halfway
>>>> down stalls with this EM:
>>>>
>>>> *Dracut: Warning: Boot has failed. To debug this issue add "rdshell" to
>>>> the kernel
>>>> command line.
>>>> Dracut Warning : Signal caught.
>>>>
>>>> Kernel Panic -not syncing : attempted to kill init!
>>>> id:1, comm: init Tainted :6
>>>> --------------------------------------------#2.6.32-131.6.1el6.i6
>>>> 6.thinclient s1
>>>>
>>>> *If I want to add "rdshell", where would I put it?
>>>>
>>>> Could this be a simple permission problem --- the Kiwi-Ltsp machine
>>>> boots with the pxelinux.0 from the CentOs machine
>>>> if I understand it correctly -.
>>>>
>>>> Or could the 2 systems be incompatible?
>>>>
>>>> Thanks for any advise on this.
>>>>
>>>> greetings, J.
>>>> *
>>>> *
>>>>
>>> _______________________________________________
>>> K12OSN mailing list
>>> K12OSN at redhat.com
>>> https://www.redhat.com/mailman/listinfo/k12osn
>>> For more info see<http://www.k12os.org>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:<https://www.redhat.com/archives/k12osn/attachments/20120202/c2f2fe5f/attachment.html>
>>
>> ------------------------------
>>
>> _______________________________________________
>> K12OSN mailing list
>> K12OSN at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12osn
>>
>> End of K12OSN Digest, Vol 96, Issue 2
>> *************************************
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see<http://www.k12os.org>




More information about the K12OSN mailing list