similar to: PUT type REST API

Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I get this error: *notice: Signing certificate ...* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using

I''m still having some issues with cloud provisioner. I have a fresh install of provisioner, .60rc1, puppet 2.7.3, and dashboard 1.2.0. Everything has a very default install as described in the documentation. I was unable to get bootstrap to work, so I did things in a linear fashion (create, install, classify). Classify is failing and theres not really any good debug info, I just get

Hi everyone, On my dashboard, for everynode on the ''event'' tab I am able to click on the ''content changed'' (the md5 sum seems to be a link) but when I do I get a window with ''getaddrinfo: Name or service not known'' Here is the error on the dahsboard: Processing FilesController#show (for 10.63.1.64 at 2012-09-20 12:47:02) [GET] Parameters:

I wanted to do a little playtesting with Samba as a domain controller. I spun up a Debian 10 box, installed Samba (package 4.9.5+dfsg-5+deb10u1) , and attempted to join it to the domain. It crashed horribly. ;) Unfortunately their domain ends in ".local". There's nothing I can do about it at the moment. But I do remove multicast DNS from nsswitch to prevent it from attempting to

I need to programmatically remove cert from Puppet master and remove all information in Puppet DB for a node from another machine which is neither Puppet Master or PuppetDB. It does have a Puppet signed cert since it is also provisioned using Puppet. I can''t find any decent documentation on this. I am using the Community Edition. Any pointers / help is appreciated. Rajul -- You

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

Hi, I''ve recently started using the GPL PV Drivers (0.9.10) for a pair of test machines, one XP and one 2003. XP works beautifully: Thank you for the development efforts. 2003 works almost as well, with one exception. When I either xm reboot or xm shutdown and subsequently restart the virtual machine, at first login I get this dialogue: The system has restarted after an unplanned

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

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":

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

Hi. I have a client and server running Puppet 2.7.1 from GEMS (though the same problem occurs using the Ubuntu Lucid standard packages). I try to update the client against the server, and it freezes at this line: debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson Any idea what would cause that? I''m afraid I didn''t recognize any usable

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

Not sure if people are already aware of this, but it might save someone some time in the future. I''ve been tracking down the following error today, it''s rather unhelpful in telling you where the problem is in your manifests: # puppetd --test info: Retrieving plugin err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could

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''m trying to load balance multiple puppetmasters using apache and passenger as described in James''s book. Was able to get a single passenger server installation to work correctly. When I configure the frontend load balancer and backend workers, the backend workers does not authenticate even though I am passing the headers to it. curl -v -H "Accept: pson, yaml" \

Hi, i was testing puppet postrun_command option and i found that it will be executed even if puppet run fails to complete successfully as seen in this snippets : debug: Executing ''rm /root/file'' > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; > using pson > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could

Hi all, I''d like to comment my puppetd --debug output with some expert or other admin cause I see some thing that I don''t understand. 1.-) Defaults. I define my defaults in site.pp like: case $operatingsystem { ''RedHat'' , ''CentOS'' : { [...] Package { provider => yum,

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

possibly related to (or the same as) issues 4830 and 2244, i''m getting errors when adding a custom fact and provider to a module to propagate to clients. am i missing something here? i tried the workaround of adding a fileserver.conf to the master (referenced below and in the tickets) with no change. thanks for any help. here''s a pile of details: puppetmaster 2.6.9 is running

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