similar to: Certificate problems.

Is there a way to get a list of all the classes available from the puppet master? I have 2 goals for this - one is documentation in a human readable form, and the other is potentially importing that data into dashboard. I did find some info on the rest API (http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I can''t make any sense of the output from it. Thanks.

I''m running puppet in a local VM to do some testing, and all of our systems are behind a proxy. I''ve got the http_proxy environment variable set properly, but when I try to use puppet module install <foo> it doesn''t seem to honor it and can''t connect. I used wget to download it, but even when I use modulepath it still tries to connect to the forge and

I am trying to use puppet to configure Amazon EC2 instances. The server is my own box at home. Both server and clients are Ubuntu 8.04 running puppet 0.24.5. On the client when I run: puppetd --server myserver.com --waitforcert 60 --test I get a cert to sign on the server. I sign it and run the command above again on the client. But then I get 3 errors similar to this: warning: Certificate

I''m getting these errors when running ''puppet agent --test'' after doing a new installation of an agent: err: /Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content: change from {md5}512f42272699eaa085c83d2cc67c27ea to {md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up

Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''

Hi all I''m trying to set up a separate puppet master and client on EC2. I''ve used two instances of CentOS5.4 with nothing other than the base install and have installed puppet via the ruby gems. Puppet is at 2.6.4 on both machines. I''ve been following the guide to get a basic configuration working (http://docs.puppetlabs.com/guides/configuring.html) with a little tweak

hello, I''ve just added a new client to an existing configuration but cannot get it recognised. Both client and server are running 0.24.5, installed on gentoo linux using portage. This is what I dis: Server: /etc/init.d/puppetmaster start * Starting puppetmaster ... [ ok ] Client: puppetd --test warning: peer certificate won''t be verified in this SSL session notice: Did not

Hello readers, I have this little issue that my puppet client refuses to do anything because of SSL validation errors. Maybe I''ll just post dump of what happens, that makes it clear I hope. Does anyone have a suggestion why that might happen? what I already checked: On the master: - Puppet and puppetmaster is running - Something is listening on Port 8140 (although I cannot

Does puppet doc require a specific version of any gems (such as rdoc or rake) to operate? I''m getting some errors when I try to generate my rdoc now. # puppet doc --output /var/www/test --modulepath /etc/puppet/environments/test/modules -m rdoc RDoc::RDocError is deprecated and will be removed in RDoc 4 Could not generate documentation: uninitialized constant RDoc::RDoc::Generator

I recently started trying to use rspec-puppet and puppetlabs-rspec-helper. When I ran ''rspec-puppet-init'' in one o fmy modules, it created a series of symlinks. Now, when I run puppet doc (via a rake task supplied by The Foreman, but also when I call it directly) I get the following error: Could not generate documentation: Definition ''mongodb::addmongouser''

1. I get the following error when I run “puppet device’ err: Could not request certificate: Could not write /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to privatekeydir: Permission denied - /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem Any thought? Thanks, -- You received this message because you are subscribed to the Google Groups

I have a module located at /etc/puppet/environments/test/modules/ruby. I n this I have a manifests folder with two .pp files - init.pp and gemInstall.pp. In one of my node def files I have: include ruby ruby::gemInstall { ''someGem-version.gem'': path => ''/path/to/agent/local/gem/repo'', } ruby::gemInstall is a define, and it has some logic to get around

Hi, I have puppet 3.0.1 installed with passenger and the clients are unables to request a certificate. I get a httpd error. 10.1.1.9 - - [11/Dec/2012:16:09:44 +0000] "GET /production/certificate/puppet-client2.tcl-oob.net? HTTP/1.1" 500 11298 "-" "-" When I run puppet master without passenger, I am able to request and sign certificates. I see this in http

Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted:

I am banging my head against the wall for recently built hosts that are unable to verify the server''s certs. The usual is not working. on the puppet agent machine: find /var/lib/puppet/ssl -type f -delete on puppet master: puppetca --clean <new_host_cert> on agent: puppetd --server puppet --waitforcert 2 --no-daemonize -d -o on puppet master: puppetca --sign

When I try to connect to my new puppet master, I get an error because of a self-signed certificate: ---snip--- # puppet agent --test --noop Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [self signed certificate in certificate chain for /CN=Puppet CA:

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

Hi, I posted an other problem with puppet and windows weeks ago. With the new Version 2.7.12 those problems were fixed. But now I don''t get puppet to work. I installed puppet as explained here: http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows It worked so far. But when I start puppet agent --test --waitforcert 10 I get the following error message:

A quick overview of our setup: We have an EBS-backed puppet master instance with an Elastic IP, and a number of puppet agent AMI images in various regions. When these AMIs were created, they were authenticated with the puppet master using the following command: # puppet agent --certname=$(cat /etc/puppet/certname) --server puppet.ourdomain.net --waitforcert 30 --test ...and accepted on the

Hi All, I have spent couple of days trying to work-out this problem with not luck. I am working on a Linux Fedora 14. I ssh from the server to the client using teh IP with no problem. Client: # puppetd --server puppet --waitforcert 60 --test --verbose info: Creating a new SSL key for bar03 warning: peer certificate won''t be verified in this SSL session warning: peer certificate