similar to: troubles with require parametre

Both the server and the client in this example are running 2.6.5: One class seems to be causing the error: debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml /var/lib/gems/1.8/gems/puppet-2.6.5/lib/puppet/resource.rb:396:in

Hi, We''re using puppet from longer time, but now want to switch into stored configs. When I ran locally puppet on puppetmaster server, ie: puppet /var/lib/puppet/manifests/nodes.pp --debug it works smooth. When running client with debug I get message: root@puppet-client:~# puppet agent -v --fqdn=puppet-client.ig.local -- waitforcert 60 --onetime --no-daemonize --logdest console --test

Good morning , I could audar to debug this problem ? "puppet agent - test" Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pentaho for srvdev206.cia.stefanini.com on node srvdev206.cia.stefanini.com /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in

Good morning , I could help to debug this problem ? "puppet agent - test" Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pentaho for s <http://srvdev206.cia.stefanini.com/> erver.test.com /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in

I am using Ubuntu LTS 10.04 with the backported puppet 2.6.1-0ubuntu2~lucid1 I am trying to create user with the following manifests but at the end always getting the Could not find user git error message: What am i missing, seems the manifest not creating the missing git user. /etc/modules/git/manifests/user.pp class git::user { user{''install'': name

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

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]

I am new to using puppet and having trouble when updating an agent from a master which has a lot of files. Usually the updates work, but when there are a lot of files I get this error when running: sudo puppetd --test --server puppet.example.local --trace --debug >>> debug: Failed to load library ''rubygems'' for feature ''rubygems'' debug: Failed to load

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''ve been hitting this issue for a long time. well over a year and I guess it''s time to start pushing it to try to find the root cause. I''ve seen this reported several times in the past but I''ve never seen a resolution found for this exact problems. There are other root causes for pson errors that have been resolved, but not for the ones describing my

I''ve tested this functionality in both 2.6.8 and the latest 2.7.0 RC. As far as I can tell, the TransBucket looks good but fails on #to_catalog due to an alias. https://gist.github.com/1028013 Any help or thoughts would be appreciated! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hi, I am newbie in puppet. Now I have installed the puppet master and puppet client on 2 nodes. when I ran puppet client with the command *$ sudo puppetd --waitforcert 60 --verbose --debug --test* * * *I have got an following error * * * * debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Failed to load library ''ldap'' for

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''m not really sure the problem is a Plugin problem!! Note than a puppet client was installed, i change the setting of ip/hosname and try to re inscription the node to puppetmaster. I would like to understand what happen. The errors/warnings messages are not very easy to understand and sometime i''m lost. thank you for you advice. Eric Puppet version: 0.25.4-2ubuntu6

I just installed the latest rc 1.7 to solve another issue I had. It solved the issue, but I''m getting a different issue. I''m running it interactively from an administrator command prompt. It connects to the master puppet server, processes the configuration items then gives an error. The interesting thing is that it never returns to the command prompt. It just hangs. I have

We are seeing this error in our log files on some clients: puppetd[15068]: Could not run Puppet configuration client: undefined method `initvars'' for #<Puppet::Type::Package:0x2aaaabbb4858> Where do I begin troubleshooting this? The client software versions are: ruby-1.8.5-5.el5_4.8.x86_64 ruby-libs-1.8.5-5.el5_4.8.x86_64 ruby-shadow-1.4.1-7.el5.x86_64 facter-1.5.8-1.el5.noarch

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

I now have it listed in the console but I am now getting new errors err Could not retrieve catalog; skipping run Puppet 2012-04-05 10:22 EDT err Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param ''undef'' at /opt/puppet/ share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node <agent> Puppet 2012-04-05 10:22

Hi, i''ve upgraded many of my client machines to version 2.7.10 lately and since on some clients (server is running 2.7.10) i get the following error (running puppetd -tvd --noop --trace): /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `<=>'' /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `sort'' /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in

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