search for: request_cert

Hi I am looking for quite a while now to run Puppet inside a vserver. The installation worked perfectly, but when I run a test I get this message: smb-configmaster / # puppetd --server 192.168.0.144 --waitforcert 60 --test /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Could not connect to 192.168.0.144 on port 8140 (Puppet::Error) from /usr/bin/puppetd:345 What can I do to make puppet run inside a vserver? Norbert

I have one puppet complaining - Could not retrieve configuration: Certificates were not trusted: block type is not 01 Puppetmaster and puppet''s are CentOS 4.5 and I use the Lutter rpms of 23.2, anyone ever see this? Thx Tim

...fo: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/ host.pem warning: peer certificate won''t be verified in this SSL session err: Could not call puppetca.getcert: #<Errno::ECONNRESET: Connection reset by peer> /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Connection reset by peer (Puppet::Error) from /usr/sbin/puppetd:356 I''m not sure what may be causing this, but should add that we recently upgraded from 0.24.1 to 0.24.2 Regards, kenneho --~--~---------~--~----~------------~-------~--~---...

...t & other configurations are done. I have issues getting certificates from server. vm1 is server & vm2 is client. In client I run, root@vm2# puppetd --server vm-devserver-18.dev.s.vonagenetworks.net -- waitforcert 60 --test and I see, /usr/lib/ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Could not connect to vm1 on port 8140 (Puppet::Error) from /usr/sbin/puppetd:356 In server I run, root@vm1:/var/home/gsivaraj# puppetca --list And I get No certificates to sign As this is related to opening up the ports so, I did the following t...

...etc/puppet] debug: Finishing transaction -607037388 with 0 changes debug: Calling puppetca.getcert warning: peer certificate won''t be verified in this SSL session /usr/lib/ruby/1.8/puppet/network/xmlrpc/client.rb:57:in `getcert'' /usr/lib/ruby/1.8/puppet/network/client/ca.rb:26:in `request_cert'' /usr/lib/ruby/1.8/puppet/executables/client/certhandler.rb:38:in `retrieve_cert'' /usr/lib/ruby/1.8/puppet/executables/client/certhandler.rb:27:in `read_retrieve'' /usr/sbin/puppetd:347 err: Could not request certificate: Certificate retrieval failed: Certificates were not...

...--test warning: peer certificate won''t be verified in this SSL session. info: Creating a new certificate request for asmc1n2.dev.gridapp.com info: Creating a new SSL key at /etc/puppet/ssl/private_keys/asmc1n2.dev.gridapp.com.pem /usr/lib64/site_ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Certificate request does not match existing certificate; run ''puppetca --clean asmc1n2.dev.gridapp.com''. (Puppet::Error) from /usr/sbin/puppetd:346 Eugene Ventimiglia Director of Systems GridApp Systems e: eventi@gridapp.com o: 6...

I restarted puppetmasterd and it announced that the Cert does not match existing key ! [root@puppet ~]# puppetmasterd --verbose --no-daemonize info: Starting server for Puppet version 0.24.1 info: mount[files]: allowing 10.100.0.0/16 access info: mount[files]: allowing *.gridapp.com access info: mount[files]: allowing *.dev.gridapp.com access info: Retrieving existing certificate for

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a