Actually I had as many as 5 servers. I'm in the process of upgrading 32-bit 
servers to 64-bit because we had only 32-bit thin clients. These are all 64-bit 
now, so the servers all need to be migrated as well.

I used to use ltsp-cluster. Since that doesn't work with ltsp-pnp, I now use 
ipxe boot menus to boot the clients and load-balancing the servers. All the 
clients boot using HTTP, not TFTP for their final image. I have one tftp boot 
server/dhcp server to load the first menu. When the ltsp option is chosen, the 
least loaded server is chosen.

The first server was upgraded from 32-bit to 64-bit Debian Jessie - not simple 
or really supported, but not impossible. The second server was created with a 
bare-bones install and an RCP restore of the first server. I may have missed 
reconfiguring one of the files for the new server, which is when the SSH key 
problems started. Now that's resolved. The next upgrades should go without any 
problems.

As a  side note, I had posted earlier about a VMWare View kiosk. My solution 
for that was to recreate a separate screen and session file for View. Now we 
have a browser kiosk on screen 3, a vmware view kiosk on screen 5 and the usual 
ldm login on screen 7. I'll have to post those files later.

--

Robert Mavrinac
Server & Network Technician
School of Computer Science
Room 3104 Lambton Tower
University of Windsor
401 Sunset Avenue, Windsor, ON N9B 3P4
519-253-3000 (4410)
Email: [email protected]
________________________________
From: Valtteri Suojanen <[email protected]>
Sent: August 3, 2016 3:38:28 PM
To: [email protected]
Subject: Re: [Ltsp-discuss] Can't login on LTSP client due to SSH key error


Hi

yes. with two application (desktop ) servers.

ltsp-update-sshkeys -u srvname1...
ltsp-update-sshkeys
ltsp-update-image

Updating keys in network with two ltsp servers and both application servers got 
me thinking. I am just curious is (or how it is) in your setup ltsp network  
configured with two ltsp-pnp  perhaps as the defaults and in same network? In 
that case  you would have to manage the servers separately in the dnsmasq dhcp 
configurations also and having two dhcp servers in simple ltsp-pnp network is 
in my opinion not optimal for just 1-2 DE's or app servers  maintenance, 
especially when adding clients in such network . Maybe I just did not now 
understand the setup... and apologize if messing up too much.

In case you need to discuss about the setup in general there are some 
professionals and current developers also online in #ltsp .

3.8.2016 21.29 "Robert Mavrinac" 
<[email protected]<mailto:[email protected]>> kirjoitti:

I think I just found the work-around.


Since this is an ltsp-pnp setup, I ran

ltsp-update-sshkeys -u server_name

on each application server, which by default creates 
/etc/ltsp/ssh_known_hosts.auto.


I've run into issues in the past over hostname versus ip address in 
known_hosts, so I made sure each key begins with server_name,server_ip_address 
not just the server_name

sed -i '/^server_name/server_name,server_ip_address/g' 
/etc/ltsp/ssh_known_hosts.auto

ltsp-update-image --cleanup /

After rebooting the ltsp client again, everything seems good now on both 
servers!


________________________________
From: SZABO Zsolt <[email protected]<mailto:[email protected]>>
Sent: August 3, 2016 1:40 PM
To: 
[email protected]<mailto:[email protected]>
Subject: Re: [Ltsp-discuss] Can't login on LTSP client due to SSH key error

On Wed, 3 Aug 2016, Robert Mavrinac wrote:

> Just to clarify, I login at the shell as 'root' in screen 1, and as a
> regular unprivileged user on screen 7.

Hmm... I know this :-)

Are there any messages about some ssh keys when logging in from screen 1?

Check the folder /root/.ssh... before and after the login.

I guess, that the ssh_known_hosts are incorrect in the folder /etc/ssh .

If so then scp the appropriate file from /root/.ssh/ to the server
and add the relevant keys from that to the appropriate file in
${ltsp-chroot}/etc/ssh/...

(Maybe the ltsp-update-sshkeys script did not run or you have some special
setup and it messed the keys up...)

Zs
--
# Just because they are called 'forbidden' transitions does not mean that they
# are forbidden.  They are less allowed than allowed transitions, if you see
# what I mean.
#                -- From a Part 2 Quantum Mechanics lecture.

------------------------------------------------------------------------------
_____________________________________________________________________
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<http://irc.freenode.net>

------------------------------------------------------------------------------

_____________________________________________________________________
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<http://irc.freenode.net>

------------------------------------------------------------------------------
_____________________________________________________________________
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

Reply via email to