On Tue, Mar 9, 2010 at 11:37 AM, Robert Pelletier <robp2...@gmail.com> wrote: > This is what I get when I try to open fl_teachertool. There are no > extra characters in the key. > This Also try to copy the key manually (ctrl-alt-f2 then pull it with scp > from the server) to /root/.ssh/authorized_keys and see if things work. > - Show quoted text - did not work. > > --- 172.31.100.138 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.183/0.183/0.183/0.000 ms > PING 172.31.100.140 (172.31.100.140) 56(84) bytes of data. > > --- 172.31.100.140 ping statistics --- > 2 packets transmitted, 0 received, 100% packet loss, time 1000ms > > PING 172.31.100.109 (172.31.100.109) 56(84) bytes of data. > > --- 172.31.100.109 ping statistics --- > 2 packets transmitted, 0 received, 100% packet loss, time 1000ms > > PING 172.31.100.105 (172.31.100.105) 56(84) bytes of data. > > --- 172.31.100.105 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.212/0.212/0.212/0.000 ms > PING 172.31.100.110 (172.31.100.110) 56(84) bytes of data. > > --- 172.31.100.110 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.207/0.207/0.207/0.000 ms > PING 172.31.100.189 (172.31.100.189) 56(84) bytes of data. > > --- 172.31.100.189 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.173/0.173/0.173/0.000 ms > PING 172.31.100.138 (172.31.100.138) 56(84) bytes of data. > > --- 172.31.100.138 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.097/0.097/0.097/0.000 ms > PING 172.31.100.141 (172.31.100.141) 56(84) bytes of data. > > --- 172.31.100.141 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.235/0.235/0.235/0.000 ms
up 141 138 189 110 105 down 140 109 These following lines are because these guys are down. You can see ping failed for them. > ssh: connect to host 172.31.100.140 port 22: No route to host > ssh: connect to host 172.31.100.140 port 22: No route to host > ssh: connect to host 172.31.100.140 port 22: No route to host > ssh: connect to host 172.31.100.109 port 22: No route to host > ssh: connect to host 172.31.100.109 port 22: No route to host Here is the problem. > Permission denied (publickey,gssapi-with-mic). > Permission denied (publickey,gssapi-with-mic). > lost connection > Permission denied (publickey,gssapi-with-mic). > Permission denied (publickey,gssapi-with-mic). > Permission denied (publickey,gssapi-with-mic). > lost connection > Permission denied (publickey,gssapi-with-mic). The following is because this host is not known to the server yet. Not a big deal. > The authenticity of host '172.31.100.189 (172.31.100.189)' can't be > established. > RSA key fingerprint is a8:a7:d7:cb:2d:71:c0:d8:af:4c:dc:d7:fa:86:f8:e8. > Are you sure you want to continue connecting (yes/no)? ssh: connect to > host 172.31.100.109 port 22: No route to host Again don't try to use fl-tt until you can get the ssh key issue resolved. Have you setup ssh keys before? Try reading some tutorials on ssh key setup. Remember the ltsp client is running the sshd server. If you can ssh into a client from the ltsp server (without a password) then fl-tt should work. (root account to root account) BTW you would think copying root's public key to /opt/ltsp/i386/root/.ssh/authorized_keys would work but it doesn't. That's why I did that hack of pasting it to rc.local on the client. Things to check: make sure sshd is running of the client make sure root login is permitted make sure it's root's public key on the server you are copyiing how are you running fl-tt? su - then run fl-tt as root on the server. -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
