Thin Client (LTSP) failure to chroot

[ulat]

Hi!
I am trying to build a fat-client-image with ltsp-build-client but I always get the warning: Failure trying to run: chroot /opt/ltsp/amd64 mount -t proc proc /proc
I think there is one "proc" too much, the command should be: "chroot /opt/ltsp/amd64 mount -t proc /proc", should it?
Any idea how to handle this problem?
Thanks!

[FarquahrWindsor]

from memory its mount type device location so even though it looks funny actually its right.

where are you getting the error ltsp.log ?

It worked but there is quite a bit to do with LTSP yet.
I think the dev's are busy with kerb and it might be a while.

[jsalamero]

Does it fail the image build? ltsp.log? That command is OK.

[Neru]

Hello ulat and sorry for the delay,

could you please give us some more information (mainly /var/log/zentyal/ltsp.log and zentyal.log) ?

Regards.

[ulat]

well, after reinstalling the server 2 times, I managed to create a thin-client-image.

Yet, if I want to boot via PXE I get always "PXE-E32: TFTP open time out" error.

I installed a firewall rule for ftp, ssh, kerberos.

As the zentyal server is not the dhcp server I put the following options to the dnsmasq:
dhcp-boot=/ltsp/i386/pxelinux.0,srv-lin-01,192.168.2.253
dhcp-option=17,192.168.2.253:/opt/ltsp/i386

and to DHCPd:
filename "pxelinux.0";
next-server 192.168.2.253;

where 192.168.2.253 is the static IP adress of the zentyal server.

Any idea, where to start looking for the bug?

[FarquahrWindsor]

Dunno if that will work ?

There is one thing you can do and if you create vlans you can put the ltsp dhcp on a different scope.

Have a look at vlans and ip-helper s

That way it would separate your internal lan and thin clients which adds security.

Looking at what you have done
dhcp-option=17,192.168.2.253:/opt/ltsp/i386 how is it going to access that is it a share?

[ulat]

Probably the next-server doesn't really work...?

When trying to connect it says:
Client IP: 192.168.2.101 Mask: 255.255.255.0 DHCP IP: 192.168.2.1
Gateway IP 192.168.2.1

Where 192.168.2.1 is the DHCP-Server and the Gateway. But shouldn't the client be forwarded to the zentyal server?

[FarquahrWindsor]

Unless its shared and you have access maybe not but I am really not sure of that config.

Have you got layer2 switches as create a vlan that uses a iphelper on that vlan to point to the right dhcp server and do it native

[ulat]

I have run into another problem. When I want to create or update an image, the machine always hangs. I am trying with a new computer sometime or give up....
Thank you for your replies!

[FarquahrWindsor]

http://forum.zentyal.org/index.php/topic,12176.msg50293.html#msg50293

Trying things myself I am wondering once you get past some of the bugs what do you think of the requirements LTSP puts on a main server?