Hi Marc, Thanks for the reply. > It's quite > possible that the server is not the same on 2 requests.
Are you saying that each time the ldm login screen loads the user might get a different server after logging out and in? In any event, it's consistently opposite after different logins with some thin clients. >It's quite > possible that the server is not the same on 2 requests. If this were a feature, it would make a lot of sense loadbalancing wise. However, it's my understanding that without exporting the correct LDM_SERVER variable on the thin client this breaks local devices. I thought that the thin client uses ssh connect to LDM_SERVER to mount the local media in /media/$USER/. Am not not understanding how this works? And indeed I see the media showing up mounted on the wrong node. Thanks much, Peter On Tue, Sep 20, 2011 at 3:24 PM, Marc Gariépy <mgari...@ubuntu.com> wrote: > hello, > > LDM_SERVER is a loadbalancer ip address of all your appserv. It's quite > possible that the server is not the same on 2 requests. > > The server LDM uses to login is refreshed when user login, so if the > appserv is down by the time the user login it won't try to log into a > server. I suggest you to use the ltsp-cluster-control log tab and look > the event action: "User login". > > On Tue, 2011-09-20 at 14:53 -0400, Peter Hartmann wrote: >> hiya, >> Running ltsp-cluster on Ubuntu 10.04 with one root server and two >> nodes serving apps. The problem is sometimes clients that log into >> LDM server app-srv1 have the environment variable LDM_SERVER set to >> the other server app-srv2. For testing purposes, I have screen_04 = >> shell, and screen_02 = xterm (minimal X script). env returns the' >> LDM_SERVER variable and from xterm, running ltsp-cluster-info from >> xterm shows the Application Server value. When the problem occurs, >> after login and one opens a command prompt, the hostname at the shell >> is either app-srv1 or app-srv2 but the info garnered from the other >> screens is indeed the opposite server. In other words, It goes both >> ways: sometimes actual LDM is app-srv1 and LDM_SERVER is set to >> app-srv02 or actual LDM is app-srv2 and LDM_SERVER is set to >> app-srv1. >> >> >> In Cluster Control, the Terminal Logs show the accurate LDM server >> the clients are using. Any ideas on where to start looking? >> >> Earlier I fixed a problem with /etc/ltsp/lbaconfig.xml that was >> setting LDM_SERVER to the interface associated with the default >> gateway but this seems like a different problem. >> >> Thanks in advance, >> >> Peter Hartmann >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2dcopy1 >> _____________________________________________________________________ >> 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 > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _____________________________________________________________________ > 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 > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _____________________________________________________________________ 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