search for: eval_resource

Hi, I''m testing puppet from the subversion trunk. I have a rather hacked-together system to install a CRM into one of my nodes, which worked (more or less) with version 0.19.3. When I tried to do a puppet run on a completely clean node it seemed to stall on the ''compilation'' part (I do an exec of ''perl Makefile.PL'' in the appropriate dir). When I broke

Hi I''m having the following problem and tried already several workarounds, as well benp- tried to help me on irc. I copied the ntp modul from DavidS repo and adapted it in the Service part to run as well under openbsd. Which was just adding some binary if openbsd is the operatingsystem. However then I wanted to run it as well on a gentoo system (on centos, debian and openbsd it was

...tion/resource_harness.rb:60:in `perform_changes'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:133:in `evaluate'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:49:in `apply'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:84:in `eval_resource'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:476:in `thinmark'' C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:475:in `thinmark&...

.../local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/ transaction.rb:346:in `failed_dependencies?'' debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/ transaction.rb:619:in `skip?'' debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/ transaction.rb:219:in `eval_resource'' debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/ transaction.rb:310:in `evaluate'' debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/ util.rb:425:in `thinmark'' debug: /usr/local/puppet-0.24.8-2/lib/ruby/1.8/benchmark.rb:308:in `realtime'&...

...or_ruby/puppet/transaction/resource_harness.rb:32:in `perform_changes'' /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:133:in `evaluate'' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:49:in `apply'' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:84:in `eval_resource'' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:104:in `evaluate'' /usr/lib/ruby/vendor_ruby/puppet/util.rb:509:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /usr/lib/ruby/vendor_ruby/puppet/util.rb:508:in `thinmark'' /usr/lib/ruby/vendor...

...opertychanges'' /usr/lib/ruby/1.8/puppet/type/file.rb:1123:in `propertychanges'' /usr/lib/ruby/1.8/puppet/type.rb:833:in `evaluate'' /usr/lib/ruby/1.8/puppet/transaction.rb:60:in `apply'' /usr/lib/ruby/1.8/puppet/transaction.rb:239:in `eval_resource'' /usr/lib/ruby/1.8/puppet/util.rb:425:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'' /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'' /usr/lib/ruby/1.8/puppet/util.rb:424:in `thinmark'' /usr/lib/ruby/...

I am consistently getting the following error from puppetd when an exec resource is triggered by a refresh event: Apr 23 10:36:11 mailhub puppetd[37884]: Reopening log files Apr 23 10:36:11 mailhub puppetd[37884]: Starting Puppet client version 0.22.3 Apr 23 10:36:11 mailhub puppetd[37884]: Starting configuration run Apr 23 10:36:12 mailhub puppetd[37884]:

I''m rather new to puppet and I''ve been trying to get a module to work on the client servers. Right now I''m trying to get http://forge.puppetlabs.com/ghoneycutt/pam to run. When I try to run it I get these two errors: err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of resource: Could not retrieve information from source(s)

...17:in `apply_changes'' /usr/lib/site_ruby/1.8/puppet/transaction.rb:109:in `collect'' /usr/lib/site_ruby/1.8/puppet/transaction.rb:109:in `apply_changes'' /usr/lib/site_ruby/1.8/puppet/transaction.rb:81:in `apply'' /usr/lib/site_ruby/1.8/puppet/transaction.rb:238:in `eval_resource'' /usr/lib/site_ruby/1.8/puppet/transaction.rb:237:in `thinmark'' /usr/lib/site_ruby/1.8/puppet/util.rb:444:in `measure'' /usr/lib/ruby/1.8/benchmark.rb:342:in `realtime'' /usr/lib/site_ruby/1.8/puppet/util.rb:444:in `thinmark'' /usr/lib/site_ruby/1.8/puppet/...

I''m trying to run puppetmasterd the first time with --mkusers. It fails with the following error message: 001 # /usr/bin/puppetmasterd --mkusers Could not configure for running; got 1 failure(s) Adding --verbose and --debug does nothing to improve the output. How do I begin to debug this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

...9; /usr/lib/ruby/1.8/puppet/transaction.rb:186:in `generate_additional_resources'' /usr/lib/ruby/1.8/puppet/transaction.rb:84:in `eval_generate'' /usr/lib/ruby/1.8/puppet/transaction.rb:104:in `eval_children_and_apply_resource'' /usr/lib/ruby/1.8/puppet/transaction.rb:92:in `eval_resource'' /usr/lib/ruby/1.8/puppet/transaction.rb:143:in `evaluate'' /usr/lib/ruby/1.8/puppet/util.rb:414:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /usr/lib/ruby/1.8/puppet/util.rb:413:in `thinmark'' /usr/lib/ruby/1.8/puppet/transaction.rb:142:...

...1.8/puppet/transaction/resource_harness.rb:93:in `evaluate'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:49:in `apply'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:114:in `eval_children_and_apply_resource'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:92:in `eval_resource'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:143:in `evaluate'' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:414:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'' /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'' /usr/lib/ruby/site_ruby/1.8...

Greetings. I am trying to set up a test puppet server in my environment to evaluate windows clients. On the server side, I am using puppet 2.7.14 (from the repos). I''m using the 2.7.14 windows 64 bit on the client (windows 2008 R2). I have another puppetmaster already using "puppet" hostname in DNS (running a very old version of puppet - can''t upgrade yet for various

Hello, we have one puppet server managing approx servers, all FreeBSD. The problem is that the puppet clients all hangs, one by one, eventually. They will run for anything between an hour up to a week. But eventually the all hang. We really like puppet and want to keep using it. But the way it is now is completely unusable. We''ve tried many versions, from 24.x, and now 2.6.1rc1. But