Hi all,
I have seen this behaviour and I am not sure of why it is happening.
There's a node that is using Puppet normally:
May 20 20:58:18 node1dot90 puppet-agent[50057]: Finished catalog run in
41.90 seconds
Then Puppet was restarted, and after the restart the agent noticed that the
FQDN h
Puppet 4.3.0
Server Debian 7
Client Debian 8
I have verified the server is running and listening on port 8140
The client has the puppet service started, but there are no certs to verify
on the server.
This is the error I am seeing:
root@puppetclient1:/opt/puppetlabs/puppet# puppet agent --test
So I'm new to puppet and I'm having a bear of a time just getting a test
server going.
I installed puppet and the puppet client via yum on CentOS on AWS, so that
saved me some time.
I followed a few various blog posts about getting everything set up and
applying a file, etc.
Now I am trying to
everybody makes mistakes :)
On Wed, Mar 31, 2010 at 9:03 AM, James Cammarata wrote:
>
> On Wed, 31 Mar 2010 08:55:25 +0800, pinoyskull
> wrote:
>> Fixed, the manifests and configs were copied from our production
>> puppet server and the buckets is still pointing to it, :)
>>
>
> Glad to see I w
On Wed, 31 Mar 2010 08:55:25 +0800, pinoyskull
wrote:
> Fixed, the manifests and configs were copied from our production
> puppet server and the buckets is still pointing to it, :)
>
Glad to see I wasn't the only one to make that mistake :D
--
This message has been scanned for viruses and
dan
Fixed, the manifests and configs were copied from our production
puppet server and the buckets is still pointing to it, :)
On Wed, Mar 31, 2010 at 7:38 AM, James Cammarata wrote:
>
> On Wed, 31 Mar 2010 06:59:07 +0800, pinoyskull
> wrote:
>> Cant seem to fix this problem, need help
>>
>> ---
>
On Wed, 31 Mar 2010 06:59:07 +0800, pinoyskull
wrote:
> Cant seem to fix this problem, need help
>
> ---
> Tue Mar 30 11:21:17 + 2010 //yumconf/File[/etc/hosts] (debug):
> Creating checksum {md5}0eea71665fb6890c06421fd13aa3f849
> Tue Mar 30 11:21:17 + 2010
> //yumconf/File[/etc/yum.repos
Cant seem to fix this problem, need help
---
Tue Mar 30 11:21:17 + 2010 //yumconf/File[/etc/hosts] (debug):
Creating checksum {md5}0eea71665fb6890c06421fd13aa3f849
Tue Mar 30 11:21:17 + 2010
//yumconf/File[/etc/yum.repos.d/CentOS-Base.repo]/checksum (debug):
Initializing checksum hash
Tue
awesome! That works.
---
Thanks,
Allan Marcus
505-667-5666
On Dec 4, 2009, at 10:12 AM, Silviu Paragina wrote:
> Actually you only need to rm puppet/ssl/certs/client_name.pem
> It's a bug in the 25 client that caches the signed certificate
> received
> from the server, even if it doesn't ma
Actually you only need to rm puppet/ssl/certs/client_name.pem
It's a bug in the 25 client that caches the signed certificate received
from the server, even if it doesn't match it's own key.
Silviu
On 04.12.2009 18:45, Allan Marcus wrote:
> ug. I figured it out.
>
> Need to clean the cert on the
ug. I figured it out.
Need to clean the cert on the server, then need to rm /etc/puppet/ssl
again, then it works.
---
Thanks,
Allan Marcus
505-667-5666
On Dec 4, 2009, at 9:32 AM, Allan Marcus wrote:
> I have 0.25.1 on client and server.
> Everything is working fine.
> I delete the /etc/pu
I have 0.25.1 on client and server.
Everything is working fine.
I delete the /etc/puppet/ssl dir to simulate a machine rebuild
I run puppetd on the client and I get:
debug: Using cached certificate for ca
debug: Using cached certificate for h09353by20h.lanl.gov
err: Could not request certificate:
I'm investigating switching to mongrel. After the switch, the client seems
to work without the cert signing process. Is that normal or have I done
something wrong?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Pu
Having a problem with cert negotiation between client and server.
client:
CentOS 4.4
2.6.9 kernel
ruby 1.8.1-7
puppet 0.24.8
Server:
Debian 4
2.6.9 kernel
ruby 1.8.7
0.24.8-1
Client:
Launch puppetd with -w30
Server:
puppetca --list shows client server. I puppetca --sign it.
Then on the clien
14 matches
Mail list logo