[02:30] hi, is there any tool in edubuntu to generate crossword puzzles? === lns is now known as askdjfksjdkfsjkd === askdjfksjdkfsjkd is now known as lns [07:30] hi, does anyone here know where to find instructions on how to compile ltsp5 custom kernels? === ogra_ is now known as ogra [13:09] ogra: looks like I wasn't too far off :) http://www.linuxdevices.com/news/NS5036131897.html [13:09] indeed [13:09] :) [13:48] Hi all [13:48] I have a login issue on my ltsp clients [13:48] they are authenticating to OpenLDAP [13:49] When logging on as an LDAP user at a LTSP client it fails with the message "This workstation is not allowed to connect to the server" [13:49] when trying from the LTSP server console, it works [13:50] how could this be? [13:50] did you change your server IP at some point ? [13:51] nope [13:51] it is static [13:51] both the LTSP and the LDAP servers have static addresses [13:51] anything in /var/log/auth.log from sshd ? [13:52] yes one odd thing [13:53] error bind to port 22 on 0.0.0.0 failed, address already in use [13:53] hrm === blue-frog_ is now known as blue-frog [14:11] ogra, I tried restarting the dhcp server but that didn't help [14:11] any thoughts? [14:12] dhcp has nothing to do with that [14:12] its ssh vs pam you have to look at [14:12] (its not even ltsp related if your clients boot fine) [14:12] they seem to boot fine [14:13] but why doesn't it fail at the LTSP console then? [14:13] its only from a dumb client that it fails [14:13] can you set SCREEN_07=ldm and SCREEN_02=shell to your lts.conf and check /var/log/ldm.log on the client for any weirdness ? [14:14] sure, just a minute [14:15] rebooting the client [14:16] last time I got this message it was a permissions issue with the NFS shares, but thats not the case this time [14:16] I already checked that [14:18] hrm, it just gives me a screwed up screen on tty2 [14:18] I can [14:18] I can't type anything or see anything [14:52] ogra: I looked through the pam and ldap stuff but it all seems fine [14:53] could it be a bad host key for sshd? [14:54] maybe I should try recreating that [14:54] thats why i asked for the IP first place :) [14:55] but the IP hasn't changed [14:55] but the mac did [14:55] the mb fried on this server and was replaced [14:55] hmm, thats shouldn affect the key [14:55] hrm [14:56] could you tell me the command to re-generate the host keys [14:57] lets just try it and see [14:58] ahha [14:58] I just tried logging onto the client with a local user account and it gave the same error [14:58] so it has to be ssh [14:58] at least to my knowlage [15:00] ogra: what do I need to do to regenerate the host keys? [15:00] is there docs on the edubuntu site that cover this? [15:00] sudo ltsp-update-sshkeys && sudo ltsp-update-image [15:01] (the latter part only for gutsy and newer) [15:01] ogra: thanks :) [15:01] hrm, how do I tell which distro I am using? [15:02] I don't remember which version I installed [15:03] oh well I'll just do it [15:03] it won't hurt anything [15:04] lsb_release -a [15:05] oh, ok [15:05] thanks [15:05] I am running gutsy [15:06] ogra: that fixed it [15:06] maybe mac address does matter [15:06] or maybe the keys just got corrupted some how [15:07] yeah, rather the latter [15:07] mac shouldnt matter [15:14] thanks for the help ogra :) [15:15] :) [20:13] anyone run into issues where a thin client will start to boot and then re-dhcp (to a different dhcp server, for instance ... my gateway instead of my ltsp server) ... and then drop to busybox? [20:23] nm - trying a suggestion from #ltsp ... setting my primary gateway's dhcp to hand out the information and disabling my ltsp server's dhcp === blue-frog_ is now known as blue-frog [20:47] ogra: final edubuntu-docs uploaded [20:48] ogra: we got 2 new translations of About Edubuntu and a couple more translations of the .desktop as well [20:48] gracias [20:50] kein problem [20:50] not sure if that's the way you'd say it [20:59] perfect [20:59] :) [23:55] I have a powerpc that I am trying to boot via ltsp [23:55] the client and server are both powerpc [23:56] I get a "invalid memory access" error