Displaying 20 results from an estimated 5000 matches similar to: "err: Could not retrieve catalog from remote server: certificate verify failed"
2011 Jul 11
2
err: Could not retrieve catalog from remote server: certificate verify failed
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
2008 Nov 19
2
Could not request certificate: Certificate does not match private key
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
2010 Nov 13
12
certificate verify failed
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
2011 Mar 11
6
failed to retrieve certificate on Amazon EC2
Hi,
I''m using puppet on EC2 to setup my VMs with the following configuration:
# puppetd --version
0.25.5
# uname -a
Linux hostname.domain 2.6.16-xenU #1 SMP Mon May 28 03:41:49 SAST 2007 i686
i686 i386 GNU/Linux
But I keep facing some timeout from puppetd:
warning: peer certificate won''t be verified in this SSL session
Exiting; failed to retrieve certificate and waitforcert
2006 Oct 18
19
Creating client certificates
I testing Puppet 0.19.3. If we decide to use it, we''d deploy it
across several thousand hosts. The method described for creating
client certificates described in the documentation - running
"puppetd --server <server> --waitforcert 60 --test" and "puppetca
--sign <client>" - is not practical for our installation. I''ve
tried creating
2010 Apr 21
3
revoked host can't be re-added?
I have a problem I can''t figure out. I was having cert problems with a
host - it seemed to have multiple host names (mot likely from dns
changes in the past) and all the certs were valid. Although it was
giving an error about a cert I could not identify. So I tried:
puppetca --revoke hostname
puppetca --clean hostname
restart puppetmaster
puppetca --list --all
(host does not show up -
2011 Apr 18
4
Certificate request does not match existing certificate
Hello there,
I have a problem while I''m trying to puppetize a client, I get this
error:
err: Could not request certificate: Certificate retrieval failed:
Certificate request does not match existing certificate; run ''puppetca
--clean puppetclienttest.sl.ss''.
I checked
-Shutdown puppet on client/server side, delete ssl/ dir to regenerate
certificate.
-Be sure that the
2011 Feb 15
11
Puppetmasterd not receiving certificate request
Hi: I''m trying to configure Puppet on Ubuntu, and strangely I am never
able to generate a certificate because my server never shows any
pending certificate requests.
Put differently, on the server I am running puppetmasterd and on the
client I am able to connect to the server, but the client continues
printing
notice: Did not receive certificate
warning: peer certificate
2006 Nov 02
6
certificate not trusted
Hello,
I try to install puppet on freebsd 6.X. All is well but i cannot get
the certificte to install and be recognized. I run .19.3.
I run the puppetd --test --waitforcert 60
then sign
and then i got:
err: No certificate; running with reduced functionality.
info: Creating a new SSL key at
/usr/local/.aqadmin/puppet/conf/ssl/private_keys/xxxxxxxxxxxxxx.pem
info: Creating a new certificate
2008 Apr 25
4
Certificate retrieval failed: Connection reset by peer
Hi.
When registering a new client with the puppetmaster I get the
following error:
[root@host ~]# puppetd --server puppetmaster --waitforcert 50 --test
info: Creating a new certificate request for host
info: 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:
2011 Nov 02
5
Puppet certificate
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:
2008 Jan 02
4
Puppetmaster doesn''t know itself
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
2009 Dec 03
1
Could not retrieve catalog
Hello all,
I''m running puppet for the first ime. I''ve finished the install but
I''m stuck at the certificate part.
The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet
client (0.24.8-4.el5) is running on CentOS 5.3.
After the install, from the client side, I''ve run:
puppetd --server puppetmaster.domain.com --waitforcert 60 --test
On the
2008 Nov 10
12
CA_Server woes
I''m having difficulty getting my head around some CA issues
My client has:
[puppetd]
ca_server=puppetca.mydomain.com
and puppet resolves to a different machine.
when puppet connects, it requests a signature from
puppetca.mydomain.combut then on the next pass fails with the
following:
err: Could not retrieve catalog: Certificates were not trusted: SSL_connect
returned=1 errno=0
2011 Mar 10
2
Puppet Certificate verify failed
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
2010 Jun 09
4
Could not retrieve catalog from remote server: certificate verify failed
Hi guys,
I''m trying to setup my first puppet installation and I''m running into problems.
I''ve got the puppetmaster running on a fresh install of Centos 5.4.
The puppet client is also on another Centos 5.4 server.
Once I''ve signed the client certificate on the puppetmaster, the
client seems to break. See below for the debug output from the client.
Any clue as
2007 Jul 03
7
CA migration
Anyone ever migrated the puppetca to a different host? What are the steps
that are involved?
2013 Feb 11
27
Certificate verify fails without indications
I have a puppet master on Centos 6.3 connected and working properly with
other Centos 6.3 agent. I installed puppet agent via gems on a RED HAT 4
node. This is what happens when I try to sign certificate for the new node:
AGENT
[root@FP2 ~]$ puppet agent -t Info: Creating a new SSL key for fp2 Info:
Caching certificate for ca Info: Creating a new SSL certificate request for
fp2 Info:
2010 Sep 16
1
'sslv3 alert handshake failure' when using puppet load-balanced through Apache
I''ve setup a puppet load-balanced solution based on these
instructions: http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Scalability
I have 4 puppetmaster instances running on my puppet server and an
Apache instance running on that server listening on port 8140 and
round-robining the requests from puppet clients. This works fine for
all my existing client machines.
The problem
2013 Aug 22
1
ssl ofloading on amazon ELB for puppetmasters
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