search for: colonfail

I have following trouble on x86_64 machines. On i686 machines all ok. [awasilyev@hyperic ~]$ sudo puppetd -t err: Could not create puppet: Could not find a default provider for cron warning: Not using cache on failed catalog warning: Configuration could not be instantiated: Could not find a default provider for cron [awasilyev@hyperic ~]$ ls /usr/lib/ruby/site_ruby/1.8/puppet/provider/cron

Hello everybody, I would like to know if there is a plugin that allow us to manage advances ACL on a linux system (Debian ) Because for the moment,the idea to use "exec setfacl" to set my ACLs sounds a little bit "dirty" Thanks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hi, I was wondering what people out there are doing to monitor puppetd in large environments. I''d love to hear what the best practices are around this. We have a few hundred hosts and are currently looking at the timestamps on the yaml files in /var/lib/puppet/yaml/facts/ on puppetmasters to make sure all clients are alive. Is it true that for a given client the fact file on the

Hi all. We have a bunch of RHEL servers running Puppet. They are also connected to our Red Hat Satellite server. Currently we don''t have any master documentation system that stores all relevant information (i.e. type of server, hardware info, linux configuration, etc) about the servers. So what I''d like to do is implement some sort of system that can hold all this information.