Hi all,
When I run puppet agent --test, I got this error:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Failed to submit 'replace facts' command for example.com to PuppetDB at
example.com:8081: SSL_connect returned=1 errno=0 state=SSLv3 read server
certificate B:
On Friday, November 2, 2012, hasufel wrote:
I'm having this issue, too.
What version of Puppet? Is the master using a different confdir than it
was in a previous version? The semantics of the default confdir have
changed as of 3.0.
-Jeff
--
You received this message because you are
I'm using Puppet 2.7.14, on a CentOS 6.3 VM. I'm using the VM for both the
master and agent, and I was able to get things running using puppet apply
site.pp, but I can't get things running with puppet agent --test; it
gives me the following errors:
err: Could not retrieve catalog from remote
I've tried clearing out the SSL directory and cleaning the certificates,
but it's still giving me the same errors.
On Friday, November 2, 2012 5:22:58 PM UTC-4, hasufel wrote:
I'm using Puppet 2.7.14, on a CentOS 6.3 VM. I'm using the VM for both
the master and agent, and I was able to get
On Fri, Nov 2, 2012 at 2:24 PM, hasufel mever...@hammers.com wrote:
I've tried clearing out the SSL directory and cleaning the certificates,
but it's still giving me the same errors.
How is the master process being started? Could you paste the exact command
with the complete argument vector
To properly reply to you, I killed my puppet process, and restarted it, and
somehow everything started working correctly with puppet agent --test,
from the master VM. However, the agent VM is still giving the same error,
so I guess it's possible it's now just a time issue.
The master process
I am using puppet to control my master, but currently when the agent runs
(on the master) I am getting err: Could not retrieve catalog from remote
server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate
B: certificate verify failed. This is often because the time is out of
That was it, thanks. I guess I assumed the command would resolve the
hostname and provide the FQDN for me.
On Friday, March 30, 2012 10:01:43 PM UTC-7, denmat wrote:
Try using fully qualified domain name. vm1.blah.com
--
You received this message because you are subscribed to the Google
Apologies if this is a duplicate, but GG seems to have eaten my previous
post
I'm trying to set up a simple master/agent on two VMs under the same ESXi
host.
I start up the master successfully on vm1, then start up the agent on vm2
sudo puppet agent --server vm1 --waitforcert 60 --test
Try using fully qualified domain name. vm1.blah.com
The server name needs to match the certificate. What you can do is remove all
your ssl puppet dirs (usually /var/lib/puppet/ssl) and set certname in your
puppet.conf to be what you call the hosts instead of using dns names.
ie: on master:
Hi All,
I am running puppet (2.7.3) with nginx and passenger (3.0.8) and
ruby-1.9.2p290. I am receiving the following error on the client when
connecting to the server.
info: Creating a new SSL key for hostname.domain.com
err: Could not request certificate: SSL_connect returned=1 errno=0
I could use some help. I am a newbie with puppet, and am trying to
learn it and use it here at the office. I have created 2 CentOS 5.5
machines ( puppet.1on1.com - puppetmaster and puppetclient.1on1.com -
which will be the client that I control.) When I attempt to connect
my client to the
PuppetNewbie jtsta...@gmail.com wrote:
I could use some help. I am a newbie with puppet, and am trying to
learn it and use it here at the office. I have created 2 CentOS 5.5
machines ( puppet.1on1.com - puppetmaster and puppetclient.1on1.com -
which will be the client that I control.) When I
PuppetNewbie jtsta...@gmail.com wrote:
I could use some help. I am a newbie with puppet, and am trying to
learn it and use it here at the office. I have created 2 CentOS 5.5
machines ( puppet.1on1.com - puppetmaster and puppetclient.1on1.com -
which will be the client that I control.) When I
Hi,
I use Debian 5.0.8 with puppet 6.2.6.
I've got the following problem after installing puppet and registering
the certificates:
client1:/home/pascal# puppetd --server=puppet.test.ch --debug --no-
daemonize --verbose --waitforcert 60
debug: Failed to load library 'selinux' for feature
try putting an entry for puppet into hosts; its detailed somewhere in the
docs i think
On Tue, Feb 1, 2011 at 1:59 PM, Pascal pascal.stoc...@man.eu wrote:
Hi,
I use Debian 5.0.8 with puppet 6.2.6.
I've got the following problem after installing puppet and registering
the certificates:
Hi,
is the time on both hosts (puppet master and puppet client) in sync?
see http://projects.puppetlabs.com/projects/1/wiki/Certificates_And_Security
Kind regards,
Martin
On Feb 1, 2011, at 2:59 PM, Pascal wrote:
Hi,
I use Debian 5.0.8 with puppet 6.2.6.
I've got the following problem
On 12/06/2010 09:13 PM, Kikanny wrote:
Whenever I try to connect to the master from the client, I get the
following error:
Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0 state=SSLv3 read server certificate B: certificate verify
failed
I tried google and
Whenever I try to connect to the master from the client, I get the
following error:
Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0 state=SSLv3 read server certificate B: certificate verify
failed
I tried google and most of the results say the problem is due the
On Mon, Dec 06, 2010 at 12:13:37PM -0800, Kikanny wrote:
Whenever I try to connect to the master from the client, I get the
following error:
Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0 state=SSLv3 read server certificate B: certificate verify
failed
I can
Is the clock of the troublesome host synchronized with all of the
others? This is often the cause of certificate verification failures.
Hope this helps,
--
Jeff McCune - (+1-503-208-4484)
On Nov 13, 2010, at 10:49 PM, David Birdsong
david.birds...@gmail.com wrote:
I am banging my head against
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
To: puppet-users@googlegroups.com
Subject: [Puppet Users] 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
/hosts, so I
updated the agent machine's /etc/hosts and it now works.
--
From: David Birdsong david.birds...@gmail.com
Sent: Saturday, November 13, 2010 2:49 PM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] certificate verify failed
I'm seeing this sporadically. What does it mean?
Sep 21 14:48:35 solr01 puppet-agent[3423]:
(/Stage[main]/Openldap::Client/File[/etc/pam.d/sudo]) Could not evaluate:
certificate verify failed Could not retrieve file metadata for
puppet:///modules/openldap/client/etc/pam.d/sudo: certificate verify
On Tue, 21 Sep 2010 13:52:23 -0700, Douglas Garstang
doug.garst...@gmail.com wrote:
I'm seeing this sporadically. What does it mean?
Sep 21 14:48:35 solr01 puppet-agent[3423]:
(/Stage[main]/Openldap::Client/File[/etc/pam.d/sudo]) Could not evaluate:
certificate verify failed Could not
On Tue, Sep 21, 2010 at 3:02 PM, James Cammarata j...@sngx.net wrote:
On Tue, 21 Sep 2010 13:52:23 -0700, Douglas Garstang
doug.garst...@gmail.com wrote:
I'm seeing this sporadically. What does it mean?
Sep 21 14:48:35 solr01 puppet-agent[3423]:
27 matches
Mail list logo
