As a followup to my last plea for hyelp, I have done the following
significant changes to a default install:

1) changed dhcpd.conf

tom@ed1:~$ cat /etc/ltsp/dhcpd.conf
#changed subnet to .100.0
authoritative;

subnet 192.168.100.0 netmask 255.255.255.0 {
range 192.168.100.20 192.168.100.250;
option domain-name "morleyschool.ed";
option domain-name-servers 192.168.192.12;
option broadcast-address 192.168.100.255;
option routers 192.168.100.254;
# next-server 192.168.100.1;
# 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";
}
}

2) changed the interfaces as follows:

tom@ed1:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
#primary interface - changed from dhcp
#to static as follows
#iface eth0 inet dhcp
iface eth0 inet static
address 192.168.192.101
netmask 255.255.252.0
network 192.168.192.0
broadcast 192.168.195.255

#secondary interface - changed subnet
#to .100.0
auto eth1
iface eth1 inet static
address 192.168.100.254
netmask 255.255.255.0
network 192.168.100.0
broadcast 192.168.100.255
up iptables-restore < /etc/ltsp/nat.conf

3) followed the how-to for enabling NAT:
https://wiki.ubuntu.com/ThinClientHowtoNAT
... and added a cron job to set the frigging ip_forward to 1 every minute
because it seems to like being a 0 instead:
sudo sh -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'

4) followed the how-to for Active Directory:
https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
Note that I also checked out the Likewise Open way but I didn't like it
and reverted to the more traditional approach described above.

5) installed ubuntu-restricted-extras for multimedia & internet browsing
support (which, wow, works fantastic)

thanks in advance for any help with this folks.

Regards,
Tom Wolfe

---
Tom Wolfe, Technology Coordinator twolfe@sawback.com
Stoney Educational Authority tel: (403) 881-2755
Box 238, Morley AB, T0L 1N0 fax: (403) 881-2793
Morley Community School | Chief Jacob Bearspaw School | Ta-otha School


On Fri, 5 Dec 2008, Tom Wolfe wrote:

> Hi again,
>
> I'm now having problems with a few seemingly random clients that do not
> boot up but fail at the following:
>
> on tty8:
> * Starting basic networking
> * Starting kernel event manager
> * Loading hardware drivers
> * Loading kernel modules
> * Loading manual drivers
> * Setting up LTSP Client
> Disconnecting: que, disconnect, sock, done
> [ 27.484772] nbd0: Receive control failed (result -32)
>
> on tty1:
> IP-Config: eth0 hardware address ... etc. etc.
>
> address: 192.168.100.31 broadcast: 192.168.100.255 netmask: 255.255.255.0
> gateway: 192.168.100.254 dns0: 192.168.192.12 dns1: 0.0.0.0
> domain: morleyschool.ed
> rootserver: 192.168.100.254 rootpath: /opt/ltsp/i386
> filename: /ltsp/i386/nbi.img
> Negotiation: ..size = 156428KB
> bs=1024, sz=156428
> Kernel call returned: Broken pipe Reconnecting
> Negotiation: ..size = 156428KB
> Error: Ioctl/1.1a failed: Bad file descriptor
>
> ----
> I get the tty1 error on all machines even ones that succeed in booting up
> (I'm using one of those right now in fact). But the ones that fail stop
> with the message above (tty8). There doesn't seem to be any rhyme or
> reason to which clients fail -- for example, a few Dell Optiplex GX115
> work, a few don't; a few IBM Netvista work, a few don't.
>
> Any advice?
>
> Regards,
> Tom Wolfe
>
> ---
> Tom Wolfe, Technology Coordinator twolfe@sawback.com
> Stoney Educational Authority tel: (403) 881-2755
> Box 238, Morley AB, T0L 1N0 fax: (403) 881-2793
> Morley Community School | Chief Jacob Bearspaw School | Ta-otha School
>
> --
> edubuntu-users mailing list
> edubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>

--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

I had the same problem some clients worked some didn't. Finally I tried
disabling NBD and enabling NFS as described here:
http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/customizing-thin-client.html
http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/customizing-thin-client.html
. I followed the instructions under "However, some people still want to use
NFS. Fortunately, it's easy to switch back to NFS, if it's so desired:".

Now my Dell OptiPlex GX1 client comes up, finally. I realize this is just a
workaround, there's something wrong in the NBD setup but I couldn't figure
it out. I'm using Ubuntu intrepid 8.10.

Regards,
Guðmundur


Tom Wolfe wrote:
>
> Hi again,
>
> I'm now having problems with a few seemingly random clients that do not
> boot up but fail at the following:
>
> on tty8:
> * Starting basic networking
> * Starting kernel event manager
> * Loading hardware drivers
> * Loading kernel modules
> * Loading manual drivers
> * Setting up LTSP Client
> Disconnecting: que, disconnect, sock, done
> [ 27.484772] nbd0: Receive control failed (result -32)
>
> on tty1:
> IP-Config: eth0 hardware address ... etc. etc.
>
> address: 192.168.100.31 broadcast: 192.168.100.255 netmask: 255.255.255.0
> gateway: 192.168.100.254 dns0: 192.168.192.12 dns1: 0.0.0.0
> domain: morleyschool.ed
> rootserver: 192.168.100.254 rootpath: /opt/ltsp/i386
> filename: /ltsp/i386/nbi.img
> Negotiation: ..size = 156428KB
> bs=1024, sz=156428
> Kernel call returned: Broken pipe Reconnecting
> Negotiation: ..size = 156428KB
> Error: Ioctl/1.1a failed: Bad file descriptor
>
> ----
> I get the tty1 error on all machines even ones that succeed in booting up
> (I'm using one of those right now in fact). But the ones that fail stop
> with the message above (tty8). There doesn't seem to be any rhyme or
> reason to which clients fail -- for example, a few Dell Optiplex GX115
> work, a few don't; a few IBM Netvista work, a few don't.
>
> Any advice?
>
> Regards,
> Tom Wolfe
>
> ---
> Tom Wolfe, Technology Coordinator twolfe@sawback.com
> Stoney Educational Authority tel: (403) 881-2755
> Box 238, Morley AB, T0L 1N0 fax: (403) 881-2793
> Morley Community School | Chief Jacob Bearspaw School | Ta-otha School
>
> --
> edubuntu-users mailing list
> edubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>
>

--
View this message in context: http://www.nabble.com/random-clients-stall-out-at-Error%3A-Ioctl-1.1a-failed%3A-Bad-file-descriptor-tp20858391p20903941.html
Sent from the edubuntu-users mailing list archive at Nabble.com.


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

OK Guðmundu, thanks for putting me on to that wor-around.At first I was
getting errors though like "NFS over TCP not available from server ip" and
"mount call failed: 13". So with a little research I realised I had to do
a few extra things in addition to the "how-to" you linked to:


1. sudo apt-get install nfs-kernel-server

2. sudo vi /etc/exports
add the following:

/opt/ltsp/i386 192.168.100.1/24(rw,no_root_squash,async)

(change 192.168.100.1 to your own network)

3. sudo /etc/init.d/nfs-kernel-server restart

4. sudo exportfs -a

** For the above steps, these pages kinda helped:
http://ubuntuforums.org/showthread.php?t=249889
http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg34378.html

** Now the how-to workaround you suggested will work, here it is for
reference:


5. sudo chroot /opt/ltsp/i386

6. Now edit /etc/default/ltsp-client-setup and change the value of the
root_write_method variable to use bind mounts instead of unionfs, it
should look like this afterwards:

root_write_method="bind_mounts"

7. Next, create the file /etc/initramfs-tools/conf.d/ltsp and add the
following line (set the value of the BOOT variable to nfs):

BOOT=nfs

8. Regenerate the initramfs:
update-initramfs -u

9. Hit CTRL-D to exit the chroot now. Make sure LTSP uses the new
initramfs to boot:

sudo ltsp-update-kernels

... all clients now boot, but I have to say I feel quite leary about this
workaround.


Is there somewhere I can report this as a bug?

Can anyone recommend any other solution?

Regards,
Tom Wolfe

---
Tom Wolfe, Technology Coordinator twolfe@sawback.com
Stoney Educational Authority tel: (403) 881-2755
Box 238, Morley AB, T0L 1N0 fax: (403) 881-2793
Morley Community School | Chief Jacob Bearspaw School | Ta-otha School


On Mon, 8 Dec 2008, v-gudmk wrote:




I had the same problem some clients worked some didn't. Finally I tried
disabling NBD and enabling NFS as described here:
http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/customizing-thin-client.html
http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/customizing-thin-client.html
. I followed the instructions under "However, some people still want to use

NFS. Fortunately, it's easy to switch back to NFS, if it's so desired:".

Now my Dell OptiPlex GX1 client comes up, finally. I realize this is just a
workaround, there's something wrong in the NBD setup but I couldn't figure
it out. I'm using Ubuntu intrepid 8.10.

Regards,
Guðmundur


Tom Wolfe wrote:


Hi again,

I'm now having problems with a few seemingly random clients that do not
boot up but fail at the following:


on tty8:
* Starting basic networking
* Starting kernel event manager
* Loading hardware drivers
* Loading kernel modules
* Loading manual drivers
* Setting up LTSP Client
Disconnecting: que, disconnect, sock, done
[ 27.484772] nbd0: Receive control failed (result -32)

on tty1:
IP-Config: eth0 hardware address ... etc. etc.

address: 192.168.100.31 broadcast: 192.168.100.255 netmask: 255.255.255.0
gateway: 192.168.100.254 dns0: 192.168.192.12 dns1: 0.0.0.0
domain: morleyschool.ed
rootserver: 192.168.100.254 rootpath: /opt/ltsp/i386
filename: /ltsp/i386/nbi.img
Negotiation: ..size = 156428KB
bs=1024, sz=156428
Kernel call returned: Broken pipe Reconnecting
Negotiation: ..size = 156428KB
Error: Ioctl/1.1a failed: Bad file descriptor

----
I get the tty1 error on all machines even ones that succeed in booting up
(I'm using one of those right now in fact). But the ones that fail stop
with the message above (tty8). There doesn't seem to be any rhyme or
reason to which clients fail -- for example, a few Dell Optiplex GX115
work, a few don't; a few IBM Netvista work, a few don't.


Any advice?

Regards,
Tom Wolfe

---
Tom Wolfe, Technology Coordinator twolfe@sawback.com
Stoney Educational Authority tel: (403) 881-2755
Box 238, Morley AB, T0L 1N0 fax: (403) 881-2793
Morley Community School | Chief Jacob Bearspaw School | Ta-otha School

--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/edubuntu-users




--
View this message in context: http://www.nabble.com/random-clients-stall-out-at-Error%3A-Ioctl-1.1a-failed%3A-Bad-file-descriptor-tp20858391p20903941.html
Sent from the edubuntu-users mailing list archive at Nabble.com.


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users