Do you have the workstations in the hosts file? because it sounds like a name resolving issue I had a while ago. And when I added the workstations to the hosts file, It was fixed.
Matthew Winther On Tue, 25 Feb 2003, Ken Cobler wrote: > Jake Schroeder wrote: > > >Please help, o great NFS gurus! > > > >The client is just sitting there and mounting, mounting, mounting. It > >seems that it tries about once every ten seconds. Why would this fail? > > > > > >Sadly this has gone beyond my experience in troubleshooting NFS. I > >would investigate how to turn up debugging on the server to get more > >descriptive errors about what is failing. > > > >I wish you lots of luck though! Let us all know how it goes. > >- Jake > > > > > > > >On Tue, Feb 25, 2003 at 05:31:07PM +0200, Warwick Bruce Chapman wrote: > > > > > >>Howdy > >> > >>When I say sleep, I mean it does nothing more/freezes/dies. > >> > >>/var/log/messages says: > >> > >>Feb 25 19:16:26 krakatoa rpc.mountd: authenticated mount request from > >>192.168.0.150:688 for /opt/ltsp/i386 (/opt/ltsp/i386) > >>Feb 25 19:17:06 krakatoa last message repeated 4 times > >>Feb 25 19:18:16 krakatoa last message repeated 7 times > >>Feb 25 19:19:17 krakatoa last message repeated 6 times > >>Feb 25 19:20:27 krakatoa last message repeated 7 times > >> > >> > I had a similar problem and never received an answer. I did determine > this much. > > My server (Redhat 8.0) has 2 ethernet cards with 10 LTSP workstations. > eth0 (10.0.0.X) was the LAN, eth1 (192.168.1.X) was the Internet > connection through DSL. Default routing (gateway) went through eth1. > > If I turned off default routing, then the LTSP workstation NFS mounted > quickly as expected. However, without a default route, we could not > access the internet. > > If I turned on default routing, we could access the Internet. However, > the NFS would start the described (see above) sleep like state during > LTSP boot. The server would go from 95% idle to 20% idle. After about > 90 seconds, the LTSP workstation NFS mounted and the LTSP workstation > booted the rest of the way as expected. > > It looked like to me, that the NFS replies were being sent down the > wrong ethernet connection (eth1). After the server kernel timed out, it > would switch to eth0 and LTSP workstation would get its reply and > complete NFS mounting. > > For now, we don't turn off the LTSP workstations unless we absolutely > necessary. When we do, we just expect the 90 second delay before LTSP > booting. > > Any insights would be greatly appreciated. > > Ken Cobler > > >> > >> > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _____________________________________________________________________ > 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 > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ 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
