search for: christopher_wood

Hi all, I got this directory configuration: file { "${codebase_ng::repository_mount}/${sonatype_work_dir}": ensure => directory, owner => $nexus_user, group => $nexus_group, mode => 0755, recurse => false, backup => false, } Today I added some 100GB of artifacts

Couple of questions. Firstly, what''s the plugin error about? puppet agent --onetime --test --verbose info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from source(s) puppet://puppet/plugins info: Caching catalog for mon01.ap1.xxx.com info: Applying configuration version ''1346878830'' err:

Few of my puppet clients (puppet 0.24.8, ruby 1.8.5, facter 1.5.2) are dying with out any error messages on on syslog. I cannot see much system resource usage on these nodes. What is the best way to troubleshoot the root cause of the problem? -Basil -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email

Has anyone successfully puppetized BigIP (F5)? I''m specifically trying to figure out a path in making our BigIP instances be under puppet so all the VIPs, pools, profiles, etc. are all under puppet control. My requirements are probably going to be fulfilled even with just uploading a rules file if a delta''s detected. The main issue I have now is figuring out when to reload the

Hello fellow community members! I just joined you in order to find an information about how to start using Puppet... Currently we use cfengine for our legacy system containing several OS platforms, including physical and virtual servers. For fresh new hardware and OS versions we decided to go with Puppet due to it''s growing popularity (wow, 4082 members of this group only!).

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''

Short version: How do you (the multitudes) handle puppetized networking with nfs volumes? Details: I''m tweaking work''s puppetized networking for debian/ubuntu hosts. As part of this, I''d like better handling of networking changes when I have nfs mounts present on the server. Right now on all hosts (debian, ubuntu, centos) with puppetized networking will kill their

I'm having what appears at first glance to be a kickstart+anaconda issue on CentOS 7.4. As near as I can tell in the program.log in the anaconda environment, the partitioning instructions downloaded with the kickstart from cobbler appear to simply not be applied. Then /mnt/sysimage is not mounted, the logs are not copied to /mnt/sysimage/root and the installation stalls due to the anamon