On Mon, Sep 8, 2008 at 9:36 AM, Horst Prote <[EMAIL PROTECTED]> wrote: > David Hopkins wrote: > > I have searched unsuccessfully for an answer on exactly what services > > need to be restarted to allow clients to boot. Note that my > > authentication server is not the same system as the LTSP server and > > that the authentication is using ldap. > A wild guess: You use LDAP for hostname resolution? > > Your NFS-symptoms remind me of our complete DNS breakdown two months > ago (I use LDAP for user authentication but DNS for hostnames). > > So I would guess that after restarting the authentication server > (i.e. LDAP) the NFS server has problems in resolving the NFS client's > hostname, causing the "permission denied". > > If I guessed right up to this point a possible reason for this lost > LDAP connection could be the nscd. So a restart of the nscd may help. > It keeps a permanent TCP connection to the LDAP server and I sometimes > noticed problems in reconnecting after an LDAP restart. > > Horst >
Thanks! I don't run nscd on the ltsp servers that were complaining about the NFS mount, but do run nscd on the authentication server and did not reset it since I had rebooted the authentication server. I'll try resetting nscd next time. Sincerely, Dave Hopkins ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _____________________________________________________________________ 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
