search for: usecacheonfailure

Hi everyone, I have an issue setting up Puppet with an ENC. For some nodes, puppet calls my ENC twice with a 2 sec interval. All my agents share the same configuration file. Considering this very basic ENC : #!/bin/bash > nodeName=$1 > echo `date` $nodeName >> /tmp/encCalls > echo "--- > classes: > testClass:" Here is the content of /tmp/encCalls after a

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

All, I have --confdir=/etc/puppet/common in my /etc/init.d/puppetmaster and /etc/init.d/puppet files, vardir set to /var/lib/puppet in /etc/puppet/common/puppet.conf, and yet, every time I run puppetca it creates /etc/puppet/ssl. Anyone know why? Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email

So I''m trying to get multiple environments to work with puppet 0.25.1 on ubuntu 8.04 and no matter what I do, puppet just completely ignores any environment setting. There''s really next to no information in terms of configuration on the multiple environments documentation page (http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments) other than saying that the

...tate.yaml storeconfigs = false storeconfigs_backend = active_record strict_hostname_checking = false summarize = false syslogfacility = daemon tagmap = /etc/puppet/tagmail.conf tags = "" templatedir = /etc/puppet/templates thin_storeconfigs = false trace = false use_cached_catalog = false usecacheonfailure = true user = puppet vardir = /var/lib/puppet yamldir = /var/lib/puppet/yaml zlib = true ## Agent mode config root@vusion-production:~# puppet config print all --mode agent allow_duplicate_certs = false archive_file_server = vusion-deployment.texttochange.org archive_files = false async_storeconfi...

Hi All, Am new to puppet and started writing simple manifest files. I have setup Server/Client mode for puppet and when I try to apply my manifest to local machine using "puppet agent" everything works well. Is there any option to apply the manifests to a remote machine without ssh into the machine? -- You received this message because you are subscribed to the Google Groups

When an error occurs in prerun_command, puppet continues execution instead of stopping. We can see the error at the log file, but puppet cotinues doing changes: puppetd[18430]: Failed to prepare catalog: Could not run command from prerun_command: Execution of ''/path/to/command'' returned 1: We want to prevent changes when an error occurs in prerun_command. Our puppet.conf:

...39; debug: puppetd: Setting puppetdlog to ''$logdir/puppetd.log'' debug: puppetd: Setting httplog to ''$logdir/http.log'' debug: puppetd: Setting runinterval to ''60'' debug: puppetd: Setting listen to ''false'' debug: puppetd: Setting usecacheonfailure to ''true'' debug: puppetd: Setting puppetdlockfile to ''$statedir/puppetdlock'' debug: puppetd: Setting configtimeout to ''30'' debug: puppetmaster: Setting railslog to ''$logdir/rails.log'' debug: certificates: Setting hostprivkey to...

Hi All, In my set-up, I''ve got a cron job that triggers a Puppet run every 20 minutes. I''ve found that on approximately 13 nodes (out of 166), puppetd just hangs. I have to go in, kill the process, remove /var/lib/puppet/state/puppetdlock, and run puppet again and then it''s fine. After a while, it just hangs again so I have to go in, kill the process, etc. Any ideas?

...use the cached configuration when the remote # configuration will not compile. This option is useful for testing # new configurations, where you want to fix the broken configuration # rather than reverting to a known-good one. # The default value is ''true''. # usecacheonfailure = true # The fact name used to determine the node name used for all requests the agent # makes to the master. WARNING: This setting is mutually exclusive with # node_name_value. Changing this setting also requires changes to the default # auth.conf configuration on the Puppet Mast...