On Nov 10, 6:02 am, madAndroid <andrewsta...@gmail.com> wrote: > That sounds a little heavy handed ... > > also, I feel that it would probably stop the mount from happening at > all? > how would the fstab initiate the nfs mount if it's not able to resolve > the address of the nfs server correctly? > unless I'm missing something .. > > On Nov 9, 7:12 pm, Guy Matz <gm...@matz.org> wrote: > > > OK. This may seem like a bad idea, but it's a workaround that has worked > > for me: > > I add the nfs server to the 127.0.0.1 entry of the hosts file which causes > > NFS to time out pretty immediately. :-\ > > > On Wed, Nov 9, 2011 at 10:00 AM, madAndroid <andrewsta...@gmail.com> wrote: > > > We've only recently discovered that puppet can manage mount points > > > using the mount directive; > > > however, a short while back we built an nfs client and server classes > > > without using this resource, and we've encountered a problem where > > > puppet seems to hang when the nfs server is unavailable. > > > > Using --debug doesn't seem to specify exactly at which point the run > > > is failing, which could steer us in the right direction around putting > > > something in place in the classes in question. > > > > Is there anything we can do, short of switching over to using the > > > mount directive/resource, in order to mitigate the problem when the > > > nfs server is unavailable? It's preventing us from managing other > > > resources on the clients when this happens..
It all comes down to mount options. I'd recommend you absorb the material in nfs(5), but options of particular interest include 'retry', 'retrans', and 'timeo'. Do notice that the latter two will affect all operations on the mounted filesystem, not just the initial mount (and maybe not the initial mount at all -- the docs aren't quite clear on that). Unlike Len, I would not recommend using the "bg" option. Doing so likely would prevent Puppet from hanging for a long time attempting the mount, but it would also prevent Puppet from correctly managing the resource. Puppet needs to know whether it has succeeded in mounting the remote filesystem. It may also cause you trouble later if the client never does succeed in mounting the filesystem. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
