similar to: certificate verification failed

I''m running in circles with this issue... I accidentally did a ''puppetca --clean --all'' and lost all certificates. I was able to get the puppetmaster running and re-created certificates for the client system, but I get the following error: warning: peer certificate won''t be verified in this SSL session info: Caching certificate for w0f.lagged.com info:

This is the first time is happening... and It happens consecutively with all the hosts. Fresh kickstarted host (never set up before the name so its not on the revocation list), I just run puppetd -tv (we have autosign on), I just get the output below: [root@server182 puppet]# puppetd -tv info: Creating a new SSL key for server182.domain.com warning: peer certificate won''t be verified in

Hello, Attempting to setup a CA primary/standby as well as seperate puppetmaster servers (all running Apache/Passenger) behind another Apache/Passenger type load balancer. Clients are not getting certs:- err: Could not request certificate: Could not intern from s: nested asn1 error Clearly an SSL issue but not something I know a great deal about. loadbalancer.conf # Puppet Load Balancing

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, ppl I dont know what to do. I configure a new client do sync with my server. the server accept de client_cert without errors and then when i run the "puppet agent -t" agaion i got this error output info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server

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

Hi, I''m trying to do ssl offload on amazon ELB for my puppetmaster servers, it seems amazon ELB is not sending ssl_client_header & client_verify_header puppetmaster Listen 8141 <VirtualHost *:8141> SSLEngine off DocumentRoot /etc/puppet/rack/puppetmaster_8141/public/ RackBaseURI / <Directory /etc/puppet/rack/puppetmaster_8141/> PassengerEnabled on

I had installed puppet master and client on two different machines. machine A has puppet master and machine B has client. both are centos6 64 bit machines. Machine B (client) is successfully connected to master (machine A). My aim is to install New Relic agent (server monitorinig tool) on different clients. I had installed new relic agent on machine A and trying to build a module so that I

Hi Dears, I am installing the puppetmaster server and puppet client is running in the same machine. When i running : puppet agent --test --waitforcert 30 I received the error : Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate'': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed:

Hello, I randomly errors like this: Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog from remote server: end of file reached Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (notice): Using cached catalog Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog; skipping run Here are the versions: puppetmaster

Hi! Everyone, puppet agent is not able to fetch any files, plugins or post catalog, reports to the master. both puppet agent and master are on version 3.0.l, passenger version 3.0.18 , nginx version: nginx/1.3.9 built by gcc 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) TLS SNI support enabled configure arguments: --prefix=/apps/nginx --conf-path=/apps/nginx/nginx.conf

Greetings. I am trying to set up a test puppet server in my environment to evaluate windows clients. On the server side, I am using puppet 2.7.14 (from the repos). I''m using the 2.7.14 windows 64 bit on the client (windows 2008 R2). I have another puppetmaster already using "puppet" hostname in DNS (running a very old version of puppet - can''t upgrade yet for various

I have very strange problem. I set up puppet client on serveral servers but have problem with one of them. When I invoke: root@www ~ # puppet agent --server puppetmaster.domain.ltd --test notice: Ignoring --listen on onetime run info: Caching catalog for puppetclient.domain.ltd info: Applying configuration version ''1326444431'' notice: Finished catalog run in

Hello, First of all I am new to the Puppet technology. I am trying to get my puppet agent (windows) to reach my puppet master (Linux) server. In this tutorial: http://docs.puppetlabs.com/learning/agent_master_basic.html It claims to test your puppet agent you need to use the ''puppet agent --test'' command. My result when I tried this is: C:\Program Files (x86)\Puppet

Hi, I want to run Puppet on a Windows 2003 Server. I already have a working Puppetmaster (Scientific Linux). I installed Puppet on Windows like shown here: http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows This worked very well. But when I want to run puppet. puppet agent --test --debug I get the following output: (I already tried different ruby and puppet versions without

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 am trying to setup Puppet + Mongrel on RHEL5. So far I have followed this document: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel_On_Enterprise_Linux The puppetmasters all start up and Apache starts up on 8140. However, when my client connects I get the following errors: [root@lv1764p puppet]# puppetd --server puppetdev.encana.com --no- daemonize -o -v info: Retrieving

Hi all I started researching on puppet and decided I''ll try it out on Vmware Workstation using Ubuntu 10.04. So I''m trying to do the simplest puppet install pattern as outlined in http://projects.puppetlabs.com/projects/puppet/wiki/Simplest_Puppet_Install_Pattern. For now, I''m trying to test puppetd and puppetmasterd on the same machine. I start puppetmaster and

Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd

Hi Everybody, I have 2 machines, one that running puppetmasterd and another one that running client. Both run Ubuntu. First I installed 2.25.4 (I think) version and then I have upgraded Puppet to 2.6.4 Server does not have any DNS entry, so I am trying to use IP address for the client to connect. Client generates some certificate error. root@puppet-client-ubuntu:~# puppetd --server