On 17/12/2011, at 5:22 AM, [email protected] wrote:
I'll top post, because there is so much stuff below that may be noise or very important. ssh needs a reverse lookup or it will take long. Your client needs to have to have an entry, I aways have a domain dunno if you need one, assumes here that you do If one is not built correctly then lts.conf is wrong. /etc/hosts in your chroot 192.168.whatever.ip yourserver.yourdomain yourserver Nothing should overwrite or change it in particular dynamic dns If your server needs to contact the clients (I use ssh) then the /etc/hosts on the server needs client entries. I have this sort of stuff 192.168.5.121 ws121.home ws121 192.168.5.122 ws122.home ws122 The ssh server section shows what I do http://tigger.ws/wiki/index.php5?title=Ltsp A 127.0.01 line on the server /etc/hosts saying that is me won't break anything (but often it is called localhost). James > I checked and resolv.conf had entries for IPv6 and also had a weird entry of > > 127.0.1.1 ncslts3 > > on the ncslts3 server. I commented out all the IPv6 entries and also > the above line. Logins still take about 25 seconds to authenticate, > but that is less than the 30 second timeout limit so they are working. > However, this is still much longer than the 3-5 seconds that it was > requiring before all this started. > > It still takes 30+ seconds to ssh to either ncslts3 from a thin client > shell using either the IP address or the hostname. nslookup resolves > either immediately (no lag) in the shell. > > It is baffling and I'll come back to address the time issue in the morning. > > Thanks for the suggestions, they are truly appreciated. > > Sincerely, > Dave Hopkins > > On Wed, Dec 14, 2011 at 8:08 PM, Rob Owens <[email protected]> wrote: >> I'm not sure what else to suggest except that you take a look at >> /etc/resolv.conf and test lookups using the nslookup command. >> >> -Rob >> >> On Wed, Dec 14, 2011 at 07:38:44PM -0500, David Hopkins wrote: >>> Yep .. that is exactly what mine looks like and it gets overwritten at >>> each client though I do not know how. >>> >>> On the server that works, the login finishes in about 26 seconds ... >>> timed with a stopwatch. However, on the other systems, the 'no >>> response from server' message appears at 30 seconds .. so it appears >>> that the one server is working only because it completes something >>> just before the timeout. >>> >>> Sincerely, >>> Dave >>> >>> On Wed, Dec 14, 2011 at 7:31 PM, Rob Owens <[email protected]> wrote: >>>> On Wed, Dec 14, 2011 at 07:05:05PM -0500, David Hopkins wrote: >>>>> All, >>>>> >>>>> I am beginning to suspect this issue is because ssh isn't resolving >>>>> names correctly? ?Timing >>>>> >>>>> ssh myserver >>>>> >>>>> from a shell (ALT-CTL-F2) takes about 30 seconds to resolve myserver. >>>>> However, ssh any_other_server returns immediately. ?So, why wouldn't >>>>> myserver resolve quickly? ?This is true from any of the servers .. >>>>> they do not resolve their names quickly. ?On all of them, the local >>>>> (thin client) /etc/hosts has the form >>>>> >>>>> 127.0.0.1 localhost >>>>> 127.0.0.2 ltsp50 >>>>> 192.168.0.254 server >>>>> >>>>> where the thin client is lstp50 ... but ... server is not defined in >>>>> DNS, only in the thin clients /etc/hosts. ?Logging in at the console >>>>> for any account also works. >>>>> >>>> I've never configured an /etc/hosts file on the thin clients. ?Is your >>>> hosts file on the server configured properly? >>>> >>>> On my Debian system, /etc/hosts in the chroot looks like this: >>>> >>>> #This is a ltsp chroot and this file will be rewritten in boot process >>>> #of terminal. >>>> 127.0.0.1 localhost >>>> >>>> Not sure if any of this helps you... >>> ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _____________________________________________________________________ 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
