[10:03] <sunson> I followed https://help.ubuntu.com/community/UbuntuLTSP/FatClients. I used to run thin clients. I built the fat client in /opt/ltsp/fat386 and modified /etc/ltsp/dhcpd.conf to use "/ltsp/fat386" instead of "/ltsp/i386". Now the fat clients show login screen but auth fails. In a flicker, the login screen reappears. how do I debug?
[10:03] <sunson> I run edubuntu 11.04
[10:25] <highvoltage> hey sunson
[10:26] <highvoltage> sunson: it sounds like you need to do ltsp-update-sshkeys, I'm not sure if it's aware of other paths than /opt/ltsp/i386 and /opt/ltsp/amd64, you could perhaps check if it takes an argument for that
[10:26] <highvoltage> sunson: (I can't check now because I'm in the middle of a few things)
[10:27] <sunson> highvoltage: thanks. i ran itsp-update-sshkeys (without any args, right?) and it gave no output. not sure what it did. i tried running strace and gave up trying to parse the cryptic stuff that happened.
[10:27] <sunson> s/itsp/ltsp/
[10:29] <sunson> highvoltage: if I ran ltsp-update-sshkeys (without sudo) I see it complaining about not being able to remove /opt/ltsp/fat386/etc/ssh/ssh_known_hosts. that means it does know about the new fat386 path.
[10:30] <highvoltage> sunson: ah, indeed
[10:30] <highvoltage> sunson: did you also run ltsp-update-image for that chroot afterwards?
[10:30] <sunson> highvoltage: yes
[10:31] <sunson> highvoltage: if I go into the chroot and do adduser, I should be able to ALT+F1 and login, right?
[10:31] <sunson> (and of course, ltsp-update-image after the adduser)
[10:32] <highvoltage> sunson: well, LDM authenticates against your server, not local accounts in the thin client
[10:32] <highvoltage> sunson: if you add a local user in the thin client you'll just be able to log in on a VT
[10:32] <highvoltage> (ah I think that's what you might have been asking)
[10:32] <highvoltage> sunson: so... yes :)
[10:33] <sunson> highvoltage: oh, so that's irrelevant?
[10:33] <sunson> highvoltage: i mean, by adding user to chroot, i get no successful login from ldm?
[10:34] <sunson> how does it actually work? is there a doc somewhere? I looked and looked.
[10:34] <sunson> i got a faint picture that it uses sshfs. but would like to know more so that I can debug.
[10:35] <highvoltage> sunson: that's correct, adding a local user won't let you log in via ldm
[10:36] <highvoltage> sunson: ldm basically uses ssh to log in to the server
[10:36] <highvoltage> sunson: you could log in with a local user on a client and type "ssh server". if it asks you to type "yes" then the ssh keys isn't in the client
[10:37] <sunson> how does it know server? or where is that specified in the configs? I basically understand it starts off from tftp, dhcp, etc., but once the nbd root image is mounted, where is the context maintained?
[10:37] <highvoltage> sunson: which is usually the #1 thing that goes wrong when the logins don't work. it's also possible that next-server might be wrong in your dhcpd.conf
[10:37] <highvoltage> sunson: because then it would try to log in to the wrong server
[10:37] <highvoltage> sunson: I don't have a link handy but there's an ltsp manual that contains more details on these things
[10:38] <sunson> next-server is commented out in my dhcpd.conf
[10:38] <sunson> is that bad?
[10:41] <highvoltage> hmm, I thought that ldm used that to get the LTSP server, but I may be wrong.
[10:41] <highvoltage> maybe hang around a bit for a 2nd opinion (or try it out) or check the manual, I have to go for now...
[10:42] <sunson> highvoltage: ok. thanks for the help
[10:42] <sunson> i tail'ed /var/log/auth.log and found that auth happens successfully, but then it says "Received disconnect from xx.xx.xx.xx: 11: disconnected by user"
[10:59] <sunson> is there a limit to nbd image file size? I built a fat client. The image is ~774MB. I see a message in syslog "size of export file/device is 809943040" followed by a "Disconnect request received".