similar to: Puppet with CAcert certificate

I was not able to find specific help for configuring the crt file for CaCert. I gleaned from examples the following order: server certificate CaCert class 3 certificate Cacert root certificate However, when I try to configure my mail reading for IMAP, Dovecot shows the following error in the log: dovecot: imap-login: Aborted login (no auth attempts): I am assuming, based on searches for this

Hello, I''m having trouble between the client and the master. Please help! *root@r3:~# puppet agent --test* Info: Caching certificate for r3.pb Info: Caching certificate_revocation_list for ca 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:

OS - RHEL5.7 Installation Source - epel-testing repo Puppet server version - 2.6.6 puppetd version - 2.6.6 I searched Google and none of the answers were a match for my set up... I can do ''puppetd --test'' from the client and things work as expected. When doing puppet kick hostname I get the following: Triggering hostname Host hostname failed: hostname not match with the server

Hello Puppet Users, I have encountered an interaction problem between the Puppet CA and Apache mod_ssl, when the Puppet CA configuration files are moved. By default Puppet CA and the Puppet client share the same location for their configuration files, $vardir/ssl. If this is changed so that they use different directories, and Apache mod_ssl is being used like in the Mongrel configuration, then

Hello, I am trying to configure a new puppet server on Debian Squeeze, so the server version will be 2.6.2-4. I am trying to configure a client running Lenny, the puppet version is 0.25.4-2 I declare the new client with the command : #puppetd --server puppet.domain.tld --waitforcert 60 --test on the server : #puppetca --sign client.domain.tld When the client finish to execute the first

Hi all, I am trying to setup puppet master and puppetdb on same node using puppetdb module. When I try to run puppet agent -t, I see following erorr notice: Unable to connect to puppetdb server (ip-10-172-161-25.us-west-1.compute.internal:8081): SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed notice: Failed to connect to puppetdb; sleeping 2

Hello, I am installing puppet and keep getting this error [Puppet could not request certificate: No route to host -connect(2)] My DNS is resloving and i can ping the master from the agent. I have added this line to the iptables [iptables -I INPUT -s 192.168.1.20 -m tcp -p tcp --dport 8140 -j ACCEPT], where the IP is my agent. I have also added my master ip to /etc/puppet/puppet.conf Why

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

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

Hi all, Is there a more elegant way to regenerate the Puppet master certificate than what''s described in the CVE-2011-3872 toolkit? > If you can maintain a secondary shell session to the puppet master server, you can start a WEBrick master with puppet master --no-daemonize --verbose and stop it with ctrl-C. > If you prefer to only maintain one shell session, you can start a

Does anyone know if puppet cleans up its certs when you terminate an instance via ''puppet node_aws terminate'' ? it doesn''t say in the docs. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/HJM1U9ic11gJ. To post

It seems like there must be a better way of dealing with these errors in a puppermaster-agent setup. I currently have one master and one agent that work, running on ubuntu 10.10 (maverick meerkat server). On another machine, same os and hardware, I try installing with the same steps and when I run sudo puppet agent --test --verbose --debug --server <serverhostname>, it is constantly

Hello, Have a fully working setup with mostly Linux clients running on a 2.7.x master all is good. Trying to join Solaris clients to this master yields:- info: Creating a new SSL key for <FQDN> warning: peer certificate won''t be verified in this SSL session info: Caching certificate for ca warning: peer certificate won''t be verified in this SSL session warning: peer

Hello all, I''m trying to figure some things out with SSL and would appreciate some help or best practices here. I''m implementing auto scaling over Amazon EC2 for some services I have, all of the instances are based on the same AMI and I''m using Puppet to configure the hosts when they come up to make sure they have the latest configuration, also I''m using

I''m running into certificate signing problem with puppet 0.25.5 Master is running on Ubuntu server 10.04 I think the problem is with the master''s puppetca. After the master signs the certificate request from the client, there is an error in the master''s log: [2010-07-29 15:25:39] ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 state=SSLv3 read client

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

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:

How do I initiate a certificate request without going into non-daemon mode ? According to "Pro Puppet" book, so far the only way I know that can trigger a certficate request with puppet master is like this puppet agent --server=puppetmaster.test.com --no-daemonize --verbose but doing so will break my intention of automation I need to create a puppet client package. A control-C is

Hi all, I launched a Puppet service a few month ago and it did function pretty well for some time. Last week, I tried to clean old entries but I think I deleted too much information as I can no more synchronize my clients. I get a certificate error : *[root@REBITPUPPET01 ~]# puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect

Hi, I just upgrade my puppet server from version 2.6.7 to 2.7.3 and now I can''t connect new clients. When trying to connect the clients I''m denied with the following error message: err: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the time is out of sync on the server or