> I don't have much in the way of suggestions, but I ran into a lot of > problems recently when I tried to have a docroot sitting on NFS. No > matter what I did I always ran into weird problems just like this. It > sort of worked but definitely not something I could use in production...
We've been using NFS for 2 years and it works great. I worked very hard to eliminate NFS write issues when setting it up - as long as it's used as a read datastore it seems to work fine. The specific problem to which I'm referring didn't appear until we moved to 0.25 a few weeks ago. At 0.24.8 this never happened. I suppose it's possible that there's some sort of write issue with NFS under 0.25, but why would that manifest as an inability to read this one specific function and not in any other part of my massive module stack? Even when I've seen Puppet clients fail because of "Stale NFS filehandle" when the master is reloading something I've changed, they still do the run from cache and load that file fine the next time through. This function error is a critical error that kills the puppet run completely, and it never goes away until I change the .rb file for the function in some way (newline, space, whatever). That's not NFS - that's code. I'm not seeing any response from those who could speak to caching, and now that 2.6 is out, we'll probably have to wait to troubleshoot it with the developers until after we upgrade again. Thanks, everyone, for your response and for taking the time to think about what it might be. Adrian -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
