Hi Odeh, On Dienstag, 17. März 2009, Oded Naveh wrote: > while trying to check the status of the issue reported at: > http://bugs.skolelinux.org/show_bug.cgi?id=1320, > As: Thin-clients fail to load: "Connection refused", > I encountered unexpected problems. > The good news first: > * I confirm this issue is fixed by the changes Vagrant has made. > * Installation of Main+LTSP server succeeded finally. > * I didn't encounter bug 1330 either. Great! Thanks for testing+confirming! > The bad news are that at least five installations failed at > 'ltsp-client-builder' and there are problems with build scripts after > installation. > > CD version used: > Debian GNU/Linux 5.0r0+edu0~a0 _Lenny_ - Unofficial i386 CD700 Binary-1 > 20090316-20:49 There was an upload of debian-edu-install with fixes one hour later, so please try a newer image. > 1) I suspect the main issue is with CD access. > Installing on a system with two optical drives failed from secondary > master, succeeded from secondary slave. The failing syslog says: > Mar 16 12:42:28 in-target: mount: /dev/hdc already mounted or /media/cdrom0 > busy Mar 16 12:42:28 in-target: error: LTSP client installation ended > abnormally Some more of the log is at bottom of message. Uh. I'm not sure we can do something here, this sounds pretty much like a debian-installer issue... > 2) Other problems were caused due to small hard drive (13gb) and the > partitioning recipe. This may be considered non issue for working servers > but may affect testing. Definitly. http://wiki.debian.org/DebianEdu/Documentation/Lenny/Requirements currently says 8gb is enough for most profiles, so we need to update that and IMO we should also give different numbers depending on the profile. Do you have specific suggestions? > 3) When 'ltsp-client-builder' fails for any reason it has no second chance. > Any attempt of the installer to rerun the builder will fail without user > intervention, because /opt/ltsp/i386 already exists, if debconf priority is > high the installer will be looping. It would be nice to get this fixed (to succeed to install, but also not to loop endless in case of failure.) Can you please open a bug about the latter? > 4) After some installations (but not the last) splash caused bla[nk|ck] > screen during boot. This affected i810 machine both as thin-client and with > local boot. I couldn't regain display on any VT, removing "quiet splash" > options prevented the death of display. IMO we should at least prominently document how to disable splash, though if its not working on a lot of machines, I'd consider making the splash optional even. > 5) ltsp-build-client fail on debian-edu-artwork(-usplash) authentication. > --early-packages debian-edu-archive-keyring option didn't help. > --accept-unsigned-packages option allowed completion. > But /var/lib/tftpboot/ltsp/ is missing and is not compatible with dhcp > settings. I think this is fixed on newer images. > 6) debian-edu-ltsp fail too, which is regression from 20081106-10:39. > a) If installation CD is not in drive: > E: Failed getting release file file:///cdrom/dists/lenny/Release > error: LTSP client installation ended abnormally > b) With CD in drive: > W: GPG error: http://ftp.skolelinux.org lenny-test Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY FEB19998A26FF456 W: Failed to fetch > http://security.debian.org/dists/lenny/updates/Release Unable to find > expected entry local/binary-i386/Packages in Meta-index file (malformed > Release file?) E: Some index files failed to download, they have been > ignored, or old ones used instead. error: LTSP client installation ended > abnormally Same as 5. > I'm not sure which of these issues to report as bugs, please advise. See above :) In general, its always good to file specific bugs (so six here would have been better than one), though its also definitly good to first report here and then file bugs, based on feedback. regards, Holger
Attachment:
signature.asc
Description: This is a digitally signed message part.