I'm not 100% sure if this works as you would expect in your manifests,
but I've used something like this to build a redmine class:
class ruby-gems::install {
package { 'ruby1.9.1': ensure = present }
}
class bundler::install {
Package {
require = Class
{ remount-storage:
command = mount -a,
unless = grep $brand /proc/mounts,
onlyif = nc -zv $nfs_server 2049 -w 3,
}
The works for us in all use cases, and seems to be the best way
forwards :)
- Andrew
On Nov 11, 11:03 am, madAndroid
{ remount-storage:
command = mount -a,
unless = grep $brand /proc/mounts,
onlyif = nc -zv $nfs_server 2049 -w 3,
}
The works for us in all use cases, and seems to be the best way
forwards :)
- Andrew
On Nov 11, 11:03 am, madAndroid
the mounts, will give those
suggestions a try as well.
Thanks again,
Andrew
On Nov 10, 3:10 pm, jcbollinger john.bollin...@stjude.org wrote:
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
...@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
We had the same issue ... looks like a newer version has fixed it
though: 1.5.6-2ubuntu2.3
On Nov 8, 6:48 am, raffis raffael.sa...@gmail.com wrote:
Yep thanks, the ubuntu package 1.5.6-2ubuntu2.2 was the problem. Roll-
back to 1.5.6-2ubuntu2 solved the facter bug.
On Nov 8, 2:21 am, Jacob
how big is the directory structure?
we've had incredibly painful experiences trying to manage directory
perms/ownerships on large directory trees...
so much so that we only set the perms on a few of the top level
directories and left the rest
it's something to do with needing to do an md5 and
very odd problem!
is it possible that an nrpe check is being executed at 9pm which is
changing the atime on the plugin directory thereby causing the agent
to check the Md5s? Does your nagios box run any specific checks on
those affected nodes at the same time you're seeing the puppet
oddness?
