similar to: "Cannot find definition Class" and "Could not find class" hiccups after manifest/module update - once for every agent

I am trying to figure out if I am missing something simple here. After upgrading to puppet 3.0 running puppet-rspec tests that use custom resources from modules in the fixtures directory are failing. I have a module that uses the anchor type and with 2.7.19 it works fine. After upgrading to 3.0 all of the tests are failing with Puppet::Error: Puppet::Parser::AST::Resource failed with

Hi, I have a puppet infrastructure running 2.6.14 under Passenger with about 30 nodes. I''m just spinning up a new Cent 6.3, puppet 2.7.19 master. Right now I have the master built and configured using the same configuration as my 2.6.14 setup, with a few tweaks for the new version. Puppet on the master built itself fine. I have puppetd stopped on the master. I tried pointing one

How do I debug errors with external nodes? When my client connects, the following appears on the puppetmaster when running in debug mode. It''s not feasible to always be running the pupeptmaster in debug mode. debug: importing ''/etc/puppet/modules/yum/manifests/client.pp'' in environment production info: Automatically imported yum::client from yum/client into production

I had this problem all of a sudden, just changed some puppet classes in my modules, but no particular stuff or no error in the catalog creation. Env : Puppet master version 3.2.0-rc1 Centos kernel 2.6.32-279.11.1.el6.x86_64 ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Info: Caching catalog for jbossvdbmaster.prod.italy.cloudlabcsi.eu Debug: Searched for resources in 0.01 seconds Debug:

When I use the latest puppet 0.25.1 I got the same problem. This is what I do: 0. Install the Ubuntu 8.04 server with ssh, ruby, rdoc, libopenssl- ruby and git-core (which gets removed after clone). 1. Install the latest puppet from git repositories on both machines using git clone «git clone git://github.com/reductivelabs/puppet» and «git clone git://github.com/reductivelabs/facter» 2. Install it

Not sure if this is another issue cropping up with 0.24.1 but I''m getting the following: info: Loading fact raid /etc/puppet/facts/location.rb:5: private method `split'' called for nil:NilClass (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call'' from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value'' from

Anyone know what this is? It doesn''t seem related to puppet but I''m stumped. info: Loading facts in dmidecode info: Loading facts in cpuinfo debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in

Trying to get an EC2 AMI running puppet 0.25 and i''m hitting a problem. After installing the rpms and starting puppet it was just quitting with only: puppetd[3313]: Reopening log files In the log file. When running it with the following I get some more output. -bash-3.1# puppetd -D -d -t --trace debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug:

Hi everyone, I''m stuck with this error trying to set up inspection reports : Could not send report: Error 400 on SERVER: Could not intern from yaml: undefined method `intern'' for nil:NilClass Earlier, I had this one : Could not run: Could not find catalog for hostname That I fixed with : catalog_cache_terminus = yaml Agent and server are running puppet 3.2.3. Full

I can''t seem to get the authorized_key type to work at all on my systems. Below is my configuration that I used. I could have something missing but the examples I see make it difficult to compare. Additionally if I try and do the reverse using puppet resource nothing comes up: puppet resource ssh_authorized_key (this returns nothing) puppet resource ssh_authorized_key username

Hi, My puppet master don''t want to start anymore. Any idea ? [root@puppetmaster requests]# puppet master --no-daemonize --debug debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug:

Hello Everybody, I am trying to install the puppetdb on the same machine as am running my puppetmaster. I am getting the following error when am trying to connect the agent: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ''replace facts'' command for ftldwshost180.wsdev.citrix.com to PuppetDB at

I am trying to streamline the current distribution specific setup and creation of VE''s within OpenVZ with puppet. My first attempt has gone horribly wrong as you will see below. Here''s the script I wrote to replace the redhat specific setup that OpenVZ used: [jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh #!/bin/bash # # Debug - take out later set -x

Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

Hello. While trying to get to the bottom of a puppetmaster+unicorn+nginx rig that''s serving empty files, it seemed to be a relatively sensible idea to upgrade the puppetmaster to 2.6.1 This broke in a manner that seems to be the multiple-& bug. Running the puppetmaster standalone gives the following: [ ... ] info: mount[files]: allowing *.mysparedomain.com access info:

Well imitation is the highest form of flattery they say. So I''m surprised to see these packages neatly built to install into /opt/csw correctly and yet they exist somewhere else and have nothing to do with us here at Blastwave. fascinating. I guess we can always send an email to the person doing this and just ask if they want those packages in testing and then into the catalog for

All, I''m having an interesting certificate problem with a host I provisioned today. The host was provisioned and puppet was installed as part of the post-os provisioning process. After I signed the certificate I see the following on the client side: [root@client ~]# puppetd --verbose --no-daemonize notice: Starting Puppet client version 0.25.4 err: Could not retrieve catalog from

I''m running into certificate signing problem with puppet 0.25.5 Master is running on Ubuntu server 10.04 I think the problem is with the master''s puppetca. After the master signs the certificate request from the client, there is an error in the master''s log: [2010-07-29 15:25:39] ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 state=SSLv3 read client

I have the reporting enabled on puppet and am seeing several errors per day from random clients. The errors on the client are always ''cannot retrieve file metadata'' errors, for example (from a client machine''s syslog): puppetd[22451]: (//syslog-ng/Config-file[syslogngconf]/File[/opt/ syslog-ng/etc/syslog-ng.conf]) Failed to retrieve current state of resource: Could not

All, Rails 1.1.2 Win XP Pro Rubyful Soup 1.0.4 htmltools 1.0.9 I am terribly confused as to what pulling in a gem does with respect to how many modules get loaded at runtime. I am using two gems in my app, Rubyful Soup and htmltools. RubyfulSoup requires one module from the htmltools gem (html/sgml-parser). My app requires the RubyfulSoup gem. When I started my app, something was causing