similar to: puppet push mode

Hi, I have been getting the below error for sometime now. Both master and client are using version 0.24.8. Output from /var/log/messages err: Could not call puppetmaster.getconfig: #<#<Class:0xb7b50a9c>: execution expired> err: Could not retrieve catalog: execution expired P.S- all of this was working absolutely fine and suddenly has started to misbehave. Regards, -- You

https://projects.puppetlabs.com/issues/2476 This does seem to confuse a fair few new users. What would be a better name for "--test"? -- 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

Hello All, Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred directory structure for using multiple environments? Does it work much different in 2.6 than in 2.5? When I made the move I assumed (I know) that my current structure and configurations would just roll over but that isn''t the case. Thanks, Jim -- You received this message because you are subscribed to the

C:\Users\ml623>puppet --version 2.7.7 Puppet complains about a package resource I am trying to use saying: Invalid parameter install_options The resource is defined as: package { "splunk": name => $gu_splunk::client::splunk_package, provider => ''msi'', ensure => installed, source =>

I thought I read somewhere in Puppet docs/wiki... that it is "recommended" to avoid spaces in file paths, or some similar verbiage, but now I cant find it. Does Puppet have any known issues with spaces in file paths? It would of course scare Windows admins away... So I hope I am wrong in thinking I read that. Thanks a lot, Mohamed. -- You received this message because you are

Hi, am trying this rule: firewall { ''100 allow ssh from GUNET'': proto => ''tcp'', dport => ''22'', source => [''10.0.0.0/8'',''192.168.0.0/16'',], action => accept, } and it only seems to add a rule for the first subnet. The second is silently

In our environ, there are several services that are deployed via an NFS mount, so that the executables and configs are consistent across the board. Is there any reason why this couldn''t be done with Puppet? For example, each individual system would contain its own /etc/puppet and rc.d and pid files -- but the primary deployment would come from NFS. For that matter, as Enterprise

Sorry for being off topic. am trying the following and yaml fails to construct the object: The inventory document, from Puppet dashboard inventory service, looks like: --- !ruby/object:Puppet::Node::Facts name: pirates.uis.example.com values: productname: VMware Virtual Platform kernelmajversion: "2.6" My code: class PuppetFacts(yaml.YAMLObject): yaml_tag =

I have this in a template: ===============cut here===================== # Allow ICMP traffic -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT <% if netbackup_master_servers %> <% netbackup_master_servers.each do |master_server| -%> # Allow communication with NetBackup master server <%= master_server[0] %> -A RH-Firewall-1-INPUT -p tcp -m tcp -s <%= master_server[1]

I noticed that is if I uninstall an MSI that was installed by Puppet, Puppet does not notice. Looking at the source I see it might be checking for a state file to know whether a package is installed or not: C:\ProgramData\PuppetLabs\puppet\var\db\package\msi\SplunkForwarder.yml So one has to rememebr to delete that too.... Is this design not a problem? Thanks, Mohamed. -- You received this

What does this message mean: [root@pirates puppet]# rm -rf /var/lib/puppet/ssl/ [root@pirates puppet]# puppet cert --version 2.6.3 [root@pirates puppet]# puppet cert notice: Signed certificate request for ca notice: Rebuilding inventory file Invalid method to apply It seems to have created the ca and other things just fine. Thanks, Mohamed. -- You received this message because you are

Hello all, This is not a puppet proper issue of course.. but I was wondering if any of you could share some thoughts... When you deploy a system like Puppet at a large park of systems, you instantly increase the efficacy of mistakes and bugs in destroying the environment.... How do you deal with that? I would be interested in any experience or input, especially puppet proper best practices...

I could swear this worked fine earlier.. Now facter, and hence puppet, do not see the domain name anymore: What could cause this? C:\Temp>facter --version 1.6.2 C:\Temp>facter | findstr kernel kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 C:\Temp>facter fqdn NCS-VDI-05.none C:\Temp>facter hostname NCS-VDI-05

Is it normal that "facter --puppet" does not show the environment variable? is there a way to have it include it? Thanks a lot, Mohamed. -- 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

We are using ruby-entreprise, instead of redhat''s default ruby.... I was trying to deploy the needed gem using: /opt/ruby-enterprise/bin/gem install --no-rdoc --no-ri /tmp/ruby-augeas-0.3.0.gem But found out this would require gcc to be installed! How can I preb-build this gem to remove the need for gcc on the nodes? is there an option of the gem command to generate a distributable

Hi guys! I need configure one command exec with onlyif parameter. I want test file size exist or no. Ho i do this? Tks in advanced. Douglas -- 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

Hello All, I''m trying to start using external nodes under foreman, and I''m running into some issues. I have the entries in puppet.conf: [main] external_nodes = /etc/puppet/external_node.rb node_terminus = exec The enternal_node.rb script is the one that came with foreman: #!/usr/bin/ruby # a simple script which fetches external nodes from Foreman # you

Hello All, I''m happy to announce a new release candidate of Foreman, top highlights for this release includes: * New look and feel * Extended restful API * Support for New Puppet Reports format * Full VM/physical host Provisioning * Powerful template generator ( pxelinux, gpxe, kickstart, preseed, grub etc..) * introduce a new service called smart proxy (which can run on remote

Anybody knows what this error, bellow, means, the target file, C:/Splunk/etc/system/local/inputs.conf, does exist. sometimes, if I delete the file, it does actually create it, but never update it if it exists and changed... The resource is defined as:     file { "splunk_inputs":        owner   => SYSTEM,        group => SYSTEM,        mode    => 664,        require =>

am I doing something wrong? this seems to never find my .$env file: source => [ "puppet:///modules/gu_puppet/puppet.conf.$fqdn", "puppet:///modules/gu_puppet/puppet.conf.$environment", "puppet:///modules/gu_puppet/puppet.conf.$operatingsystem", "puppet:///modules/gu_puppet/puppet.conf" ] It