IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 9 July 2010   (all times are UTC)

00:51leio_ is now known as leio
02:30dobber has joined #ltsp
02:36try2free has joined #ltsp
02:41Faithful has quit IRC
02:41maslak has quit IRC
02:46try2free has left #ltsp
03:02Faithful has joined #ltsp
03:05Egyptian[Home] has quit IRC
03:08marl_scot has quit IRC
03:12nosedrum has joined #ltsp
03:12ogra_cmpc has quit IRC
03:13
<nosedrum>
hi everybody !
03:13
i have a problem on a production ltsp server
03:13
all clients when have => "Error: Ioctl/1.1a failed: Bad file descriptor"
03:13
at boot
03:14
my ltsp image isn't good ?
03:17
nobody have a idea ?
03:19
<dobber>
have you tried to rebuild it ?
03:19
<nosedrum>
i have done a ltsp-update-image -a i386
03:19
as usual
03:20
have to test a "update-initramfs -u" and "ltsp-update-kernels" ?????
03:21Egyptian[Home] has joined #ltsp
03:22
<dobber>
try ltsp-update-kernels
03:23ogra has quit IRC
03:23
<nosedrum>
root@ltsp_a90:/home/admindsi# ltsp-update-kernels
03:23
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386
03:23
root@ltsp_a90:/home/admindsi#
03:23ogra has joined #ltsp
03:24
<nosedrum>
i reboot a thin client too see....
03:25ogra_cmpc has joined #ltsp
03:25
<nosedrum>
the same error message...
03:28dobber has quit IRC
03:28dobber has joined #ltsp
03:28
<nosedrum>
Error: Ioctl/1.1a failed: Bad file descriptor
03:28
can i found more information in logs ????
03:28
i found nothing ...
03:45gentgeen__ has joined #ltsp
03:46
<nosedrum>
I can't solve my issue
03:46
all my thin clients boots result in a :
03:46
Error: Ioctl/1.1a failed: Bad file descriptor
03:46Faithful has quit IRC
03:47vmlintu has joined #ltsp
03:47
<nosedrum>
I don't understand why
03:55
Error: Ioctl/1.1a failed: Bad file descriptor
03:55
anybody have experience why that ?
03:55
<Appiah>
does it just stop there?
03:56
LTSP5 or 4?
03:56
<nosedrum>
5
03:56
Negociation: ...
03:56
Kernel call returned: Broken pipe Reconnecting
03:56
Negociation: ..
03:56
Error: Ioctl/1.1a failed: Bad file descriptor
03:56
login:
03:56
<Appiah>
Ubuntu?
03:56
<nosedrum>
that's all
03:56
ubuntu 9.
03:56
04
03:57
it's a production site who works since 1 year perfectly
03:57
i don't understand
03:58
what "Error: Ioctl/1.1a failed: Bad file descriptor" really mean ?
03:58
<Appiah>
post your lts.conf please
03:59
<nosedrum>
# Global defaults for all clients
03:59
# if you refer to the local server, just use the
03:59
# "server" keyword as value
03:59
# see lts_parameters.txt for valid values
03:59
################
03:59
[default]
03:59
LOCALDEV=True
03:59
SOUND=True
03:59
NBD_SWAP=True
03:59
<Appiah>
PASTEBIn
03:59
<nosedrum>
SYSLOG_HOST=server
03:59
<Appiah>
please
03:59
setop
03:59
<nosedrum>
XKBLAYOUT=fr
03:59
LDM_DEBUG=True
03:59
<Appiah>
stop*
03:59
<nosedrum>
LOCAL_APPS=True
03:59
#Bug #347957 https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/347957
03:59
03:59
SEARCH_DOMAIN = ayme.fr
03:59
DNS_SERVER = 192.168.254.29
03:59
<Appiah>
...
03:59
<nosedrum>
RCFILE_01 = /etc/init.d/chmod-resolv.sh
03:59
CONFIGURE_X = True
03:59
X_CONF = /etc/X11/xorg.conf
03:59
###############
03:59
#configuration par poste d'agence IP / LOGIN / PASSWORD
03:59
###############
03:59
[p2_a90]
03:59
LDM_USER_ALLOW=p2,admindsi
03:59
PRINTER_0_DEVICE=/dev/ttyS0
03:59
PRINTER_0_SPEED=9600
03:59
PRINTER_0_PARITY=N
03:59
<Appiah>
hello?
04:00
<nosedrum>
X_MODE_0=1024x768
04:00
[p3_a90]
04:00
LDM_USER_ALLOW=p3,admindsi
04:00
X_MODE_0=1024x768
04:00
[p4_a90]
04:00
LDM_USER_ALLOW=p4,admindsi
04:00
X_MODE_0=1024x768
04:00
[p5_a90]
04:00
LDM_USER_ALLOW=p5,admindsi
04:00
X_MODE_0=1024x768
04:00
[p6_a90]
04:00
LDM_USER_ALLOW=p6,admindsi
04:00
X_MODE_0=1024x768
04:00
[p7_a90]
04:00
<Appiah>
oh god..
04:00
<nosedrum>
LDM_USER_ALLOW=p7,admindsi
04:00
X_MODE_0=1024x768
04:00
[p8_a90]
04:00
LDM_USER_ALLOW=p8,admindsi
04:00
X_MODE_0=1024x768
04:00
[p9_a90]
04:00
LDM_USER_ALLOW=p9,admindsi
04:00
X_MODE_0=1024x768
04:00
sorry
04:00
http://pastebin.com/mXgqNPiM
04:01
what ?
04:01
<Appiah>
try setting the NBD_SWAP=True to False
04:01
and see if it changes anything
04:01
<nosedrum>
ok i test now
04:03pths has joined #ltsp
04:04
<nosedrum>
exactly the same
04:04vmlintu has quit IRC
04:04
<nosedrum>
the only one mofication before working and not working it's:
04:04
chroot /opt/ltsp/i386
04:04
apt-get install firefox
04:05
ltsp-update-image -a i386
04:05
for local execution of firefox on client
04:15Selveste1 has quit IRC
04:17vmlintu has joined #ltsp
04:22
<Appiah>
try to disable localapps in lts.conf and try again
04:22
if you still get the same I have no idea
04:34mordocai has joined #ltsp
04:41
<nosedrum>
ok my boot is ok
04:41
but now i can't log in ubuntu
04:41
user/pass is sure
04:42
gdm say "password verification, please wait"
04:42
and after 2-3 try a message says "no respond from server" and client reboot...
04:43
<zeitsofa>
hello. what can be wrong if can't burn cd's with usb dvd burner on the thinclient? the device always enable as normal dvd device but not as burner.
04:43
<Appiah>
you cant
04:43
<zeitsofa>
nosedrum: youhave to update ssh-keys
04:43
Appiah: why not?
04:43
<Appiah>
no cd/dvd burn support
04:43
has been like that for long
04:43
<nosedrum>
ok i try
04:44
ltsp-update-sshkeys done not message directly to prompt
04:44
normal ?
04:45
need a client reboot ?
04:45
<Appiah>
yes
04:45
<nosedrum>
yes for normal and reboot ?
04:45
:D
04:46
<Appiah>
sudo ltsp-update-sshkeys
04:46
then reboot the thin client
04:46
<nosedrum>
i'm root
04:46
<zeitsofa>
then without sudo ;p
04:47
<nosedrum>
and no message in output of ltsp-update-sshkeys
04:47
normal ?
04:47
give me the prompt immediatly
04:48
<zeitsofa>
yes so its fine
04:48
<nosedrum>
the issue not resolved
04:48
same login failure
04:48Da-Geek has joined #ltsp
04:51
<nosedrum>
ok resolved
04:54
<zeitsofa>
:)
05:11vmlintu has quit IRC
05:12komunista has joined #ltsp
05:23vmlintu has joined #ltsp
05:28vmlintu has quit IRC
06:04F-GT has quit IRC
06:05vmlintu has joined #ltsp
06:16vmlintu has quit IRC
06:16Da-Geek has quit IRC
06:16F-GT has joined #ltsp
06:25pmatulis has joined #ltsp
06:45vmlintu has joined #ltsp
06:55vmlintu has quit IRC
07:07vmlintu has joined #ltsp
07:08hersonls has joined #ltsp
07:18
<zeitsofa>
Appiah: u mean i cant brun cd's on thinclient. it isn't true. i can do taht. you have to install hal in chroot /opt/ltsp/i386 and e.g. k3b. i can't burn with brasero but k3b works for me.
07:18Faithful has joined #ltsp
07:19
<Appiah>
I see
07:19
then thats info is old about not being able to use cdburners on thinclients for writing
07:24Egyptian[Home] has quit IRC
07:26vmlintu_ has joined #ltsp
07:28sweetpi has joined #ltsp
07:28vmlintu has quit IRC
07:32mordocai has quit IRC
07:37vmlintu_ has quit IRC
08:14Egyptian[Home] has joined #ltsp
08:44korcan has joined #ltsp
08:46Blinny has joined #ltsp
08:48
<Blinny>
Hello - I'm having trouble with network booting a new atom-based thin client. It has a r8169 in it. When removing quiet/splash, the last message is about the eth0 hardware address, mtu, and then 'r8169: eth0: link up' -- nothing afterwards. I'm fairly sure it's not a ldm issue because I have screen_07=shell. This is on a vanilla ubuntu hardy.
08:48
Are xservers loaded from the chroot, and if so should I do an update of the chroot? It's been probably 8 months since I updated it. The server itself is all up to date with patches/updates.
08:59
There's an xserver-core update. I'll apply chroot updates and see if this helps.
09:00
My gut says a NIC problem though - I've plugged into a 100M port and get the same issue (though slightly slower;)
09:04
Strange. Same problem, slightly different order. Now some USB lines occur after an 'r8169: eth0: link down' message.
09:08
Hmm. Maybe it's a memory timing issue. The board has the timings auto-detected all kinds of wrong.
09:08
Or maybe not. Now it won't display. hehe
09:17
OK. BIOS reset and I'm back to square 1.
09:30
<sweetpi>
Blinny: do you get a black screen after all that?
09:32
<Blinny>
sweetpi: No, text stays on the screen.
09:32
(This is with quiet/splash removed) -- If I keep quiet/splash in there, then I get the blinking cursor after the splash.
09:33
The more I scratch my head, the more I feel that it's not xserver related.
09:33
<sweetpi>
check server logs, or maybe try break=premount and see if you can talk to the server manually
09:34
<Blinny>
Where do I 'break=premount'?
09:34
<sweetpi>
kernel options
09:35
<Blinny>
OK - I get my busybox shell.
09:36
<sweetpi>
now see if you can talk to the server
09:37
gtg bbl
09:37sweetpi has quit IRC
09:38
<Blinny>
Anyone know what s/he meant by 'talk to the server'? There's no ping, I can't ifconfig eth0 up, .... ?
09:49vmlintu_ has joined #ltsp
09:58
<dobber>
is there telnet ?
09:58
you can telnet IP:nbd port
09:59
also, where did you get your atom clients ?
10:01nosedrum has quit IRC
10:04
<Blinny>
I got them from newegg - a batch of 5 so I'm hoping I can get these to work!
10:11
No, no telnet
10:11
I don't have any experience with busybox. It looks like there are a lot more features in the newer versions.
10:11Gadi has joined #ltsp
10:13
<Blinny>
Gadi: You have any experience with booting cranky atom clients on hardy?
10:14staffencasa has joined #ltsp
10:23
<_UsUrPeR_>
Blinny: ping?
10:24dobber has quit IRC
10:29try2free has joined #ltsp
10:33
<Blinny>
No ping available.
10:35
I've never understood how a NIC could work to get the kernel via tftp, then dia halfway through boot.
10:35
At least, that's what I think is happening.
10:36vagrantc has joined #ltsp
10:37
<Blinny>
Are there any other tools I can use to try to find out what is going on?
10:37
(besides removing quiet/splash and break=premount)
10:38
I don't get any log entries on the server other than DHCP, but I recall ogra saying that had something to do with my lts.conf variables.
10:56try2free has quit IRC
10:59
<_UsUrPeR_>
Blinny: sorry. I was just making sure you were there. Are you using a switch between your client and the ltsp server? Also, are you using the LTSP server for DHCP, or are you using another device?
11:01pmatulis has quit IRC
11:26otavio has quit IRC
11:27try2free has joined #ltsp
11:28alkisg has joined #ltsp
11:30otavio has joined #ltsp
11:41atkuepker has joined #ltsp
12:08try2free has left #ltsp
12:11litlebuda has joined #ltsp
12:13pmatulis has joined #ltsp
12:13user_ has joined #ltsp
12:22litlebuda has quit IRC
12:23litlebuda has joined #ltsp
12:40litlebuda has quit IRC
12:41litlebuda has joined #ltsp
12:48Guest18895 has joined #ltsp
12:56litlebuda has quit IRC
13:04alkisg has quit IRC
13:07
<Blinny>
Oh
13:07hawkI has joined #ltsp
13:07
<Blinny>
Heh
13:07
_UsUrPeR_: pong!
13:07
<_UsUrPeR_>
Blinny, there you are
13:07
<Blinny>
_UsUrPeR_: Sorry. Lunch. Yeah, there's a switch. The server is 2-NIC'd and DHCP.
13:08
<_UsUrPeR_>
does the switch have spanning tree/portfast capabilities?
13:10
<Blinny>
I'm guessing not. I'm looking through the web interface and don't see any STP
13:10
<_UsUrPeR_>
as a test, try another switch. A dumber switch :)
13:11
<Blinny>
Yah I did. Same thing.
13:11
It was an older 100M switch I plugged into, and got the same deal.
13:11
<_UsUrPeR_>
or just directly connect them The problems you're having with the up/down seem to parallel an experience I had with a cisco switch
13:13
<Blinny>
Hrmmm.
13:15
<_UsUrPeR_>
it may help to get the last transmissions via wireshark
13:15
<Blinny>
Right on
13:16
<_UsUrPeR_>
what brand are the clients?
13:16
<Blinny>
It's connecting to the NBD server
13:17
They're home-brewed atom boards
13:17
D510MOhttp://www.intel.com/products/desktop/motherboards/D510MO/D510MO-overview.htm
13:18
I didn't find anything negative about them when I googled, but maybe I missed something, or they're just too new.
13:21
Woah. Using gPXE (etherboot) I get to a shell.
13:22komunista has quit IRC
13:22
<Blinny>
and LDM
13:23
Now why the hell would that happen.
13:26
That's definitely the difference.
13:26
gpxe works well. PXE does not.
13:27
Wireshark shows tftp data packets and ACKs as the last few hundred packets.
13:28
And, I've found a thread that says "The intel support told me, even if gpxe is selectable, it is not supported" -- which is why the boot process looks like PXE and not etherboot
13:29
<_UsUrPeR_>
the gpxe/pxe issue is weird.
13:30
<Blinny>
Yeah.
13:32
I think I'll give this what-for on Monday.
13:32
Thanks _UsUrPeR_. Cheers mate.
13:33Blinny has quit IRC
13:37slidesinger has quit IRC
13:40slidesinger has joined #ltsp
13:47user_ has quit IRC
14:41gentgeen__ has quit IRC
14:47pmatulis has quit IRC
15:12grantk has joined #ltsp
15:12
<grantk>
hello all
15:16
I was having trouble logging into a few new servers, I copied them from another working server I have, ran ltsp-update-sshkeys , ltsp-update-kernels and ltsp-update-image after changing their ip and assigning a new hostname. I however still see errors in the ldm log on the clients that the authenticity of the host can't be established, do I need to remove the ssh keys to get this to work properly?
15:17
ohh yeah, I only have this issue if I try and log onto a host that is listed in the host chooser and I did not connect to that hosts dhcp server to load up the image
15:19
I think I just found what I need on the mailing list, sorry will try exporting those keys
15:38
can anyone tell me if it is the host's rsa public key that needs to go in the known_hosts file for ldm load balancing?
15:44alkisg has joined #ltsp
15:51
<vagrantc>
grantk: you'll need the public ssh keys for all hosts you want to connect to.
15:52
<grantk>
vagrant, I keep getting myself a little closer, since last message I have ran ltsp-update-sshkeys --export ssh_known_hosts.hostname
15:53
then copied that file to /opt/ltsp/i386/etc/ssh and ran ltsp-update-sshkeys and ltsp-update-image. Reboot the client and get the same errors.
15:53
Is there another way to publish them?
15:54
<vagrantc>
that ought to do it...
15:54
<grantk>
hmm, ok
15:54
:q
15:55
woops, wrong window
15:55
<vagrantc>
!release
15:55
<ltspbot`>
vagrantc: "release" :: please mention the linux distro and release you're using :)
15:55
<vagrantc>
grantk: ^^ ?
15:56
<grantk>
!release
15:56
<ltspbot`>
grantk: "release" :: please mention the linux distro and release you're using :)
15:56
<grantk>
ubuntu 10.04 ltsp 5
16:00hersonls has quit IRC
16:06
<grantk>
so would this be pretty much the same as entering the chroot environment, ssh into the other server, accept the key, rebuild the image and go on your way?
16:09
and yes, that worked for me
16:19grantk has left #ltsp
17:01alkisg has quit IRC
17:03Gadi has left #ltsp
18:40Selveste1 has joined #ltsp
18:42staffencasa has quit IRC
18:46F-GT has quit IRC
18:47F-GT has joined #ltsp
19:01korcan has quit IRC
19:20monteslu has quit IRC
19:20Leolo_3 has quit IRC
19:20jbrett has quit IRC
19:20jhutchins_lt has quit IRC
19:23jhutchins_lt has joined #ltsp
19:37monteslu has joined #ltsp
19:44Selveste1 has quit IRC
19:46try2free has joined #ltsp
19:54vagrantc has quit IRC
20:00giaco has joined #ltsp
20:05F-GT has quit IRC
20:18rick_h_ has joined #ltsp
20:18rick_h_ has left #ltsp
20:20giaco has quit IRC
20:22F-GT has joined #ltsp
20:35highvoltage has joined #ltsp
21:22try2free has left #ltsp
22:03Egyptian[Home] has quit IRC
22:16Egyptian[Home] has joined #ltsp
22:22artchie has joined #ltsp
22:35artchie has quit IRC
23:31Mobe_ is now known as Mobe