search for: thinmark

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

...sr/lib64/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:202:in `find'' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find'' /usr/lib64/ruby/site_ruby/1.8/puppet/configurer.rb:208:in `retrieve_new_catalog'' /usr/lib64/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark'' /usr/lib64/ruby/1.8/benchmark.rb:308:in `realtime'' /usr/lib64/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark'' /usr/lib64/ruby/site_ruby/1.8/puppet/configurer.rb:207:in `retrieve_new_catalog'' /usr/lib64/ruby/site_ruby/1.8/puppet/configurer.rb:104:in `retrieve...

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

...usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:121:in `find'' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:191:in `find'' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:243:in `retrieve_new_catalog'' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:348:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:347:in `thinmark'' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:242:in `retrieve_new_catalog'' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:67:in `retrieve_catalog...

...9;' /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:100:in `find'' /usr/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:197:in `find'' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:243:in `retrieve_new_catalog'' /usr/lib/ruby/vendor_ruby/puppet/util.rb:351:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /usr/lib/ruby/vendor_ruby/puppet/util.rb:350:in `thinmark'' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:242:in `retrieve_new_catalog'' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:67:in `retrieve_catalog'...

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)

I updated to 0.22.3-1 from the dlutter repo (CentOS 4.4) and I''m still having trouble adding new nodes as others saw from the previous version, though I believe the error is different now. The procedure I used was: <client> /etc/init.d/puppet once -v <server> /usr/sbin/puppetca --sign nodename <client> /etc/init.d/puppet once -v This used to work for new nodes, now I

After upgrading my puppetmaster server to 0.22.2 using David''s src RPM''s for RHEL4 rebuilt for x86_64 i am getting the following error when puppetd attempts a configuration run. Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run Puppet::[1]Network::Client::Master: Invalid value ''nil'' for noop When puppetd is started the initial run is

...y187/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'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'' C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:351:in `tr...

...:94:in `forward'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:77:in `apply'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:69:in `apply'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:169:in `evaluate'' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:510: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/puppet/util.rb:509:in `thinmark'' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:168:in `evaluate'' /usr/lib/ruby/site_ruby/1.8...

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

I have this: class foo::foobar ($version) { } which is called like this: class facility::sanjose inherits facility::common { class { foo::foobar: version => "1.3.13" } } puppet complains with this on the client: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find parent resource type ''facility::sanjose'' of type hostclass in

...9;' /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:100:in `find'' /usr/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:197:in `find'' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:243:in `retrieve_new_catalog'' /usr/lib/ruby/vendor_ruby/puppet/util.rb:351:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /usr/lib/ruby/vendor_ruby/puppet/util.rb:350:in `thinmark'' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:242:in `retrieve_new_catalog'' /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:67:in `retrieve_catalog'...

.../usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:120:in `find'' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:189:in `find'' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:237:in `retrieve_new_catalog'' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:476: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/puppet/util.rb:475:in `thinmark'' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:236:in `retrieve_new_catalog'' /usr/lib/ruby/si...

...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'' debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/ util.rb:424:in `thinmark'' debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/ transaction.rb:309:in `evaluate'&...

...3: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_ruby/puppet/transaction.rb:104:in `evaluate'' /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:386:in `traverse'' /usr/lib/ruby...

...3: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/1.8/puppet/transaction.rb:238:in `eval_resource'' /u...

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]:

Hi all, The last 2 weeks we have been having problems with puppetd just randomly stopping. The only thing the log shows is: <snip> Apr 21 12:14:59 relay puppetd[1376]: Finished catalog run in 4.78 seconds Apr 21 12:30:07 relay puppetd[1376]: Finished catalog run in 4.76 seconds Apr 21 12:45:20 relay puppetd[1376]: Finished catalog run in 4.61 seconds </snip> There is no pattern when

...ppet/indirector/rest.rb:71:in `find'' /usr/lib/ruby/1.8/puppet/indirector/indirection.rb:193:in `find'' /usr/lib/ruby/1.8/puppet/indirector.rb:50:in `find'' /usr/lib/ruby/1.8/puppet/configurer.rb:229:in `retrieve_new_catalog'' /usr/lib/ruby/1.8/puppet/util.rb:422:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /usr/lib/ruby/1.8/puppet/util.rb:421:in `thinmark'' /usr/lib/ruby/1.8/puppet/configurer.rb:228:in `retrieve_new_catalog'' /usr/lib/ruby/1.8/puppet/configurer.rb:102:in `retrieve_catalog'' /usr/lib/ruby/1.8/p...