Well, i'm not 100% sure if this is what should be sync between host and
client.
puppetclient01:~ # openssl x509 -text -noout -in
/var/lib/puppet/ssl/certs/puppetclient01.domain.name.pem | grep Validity
-A2
Validity
Not Before: Feb 18 13:02:04 2013 GMT
No
No, i'm not using passenger, i only have puppetmaster.
El martes, 19 de febrero de 2013 13:27:44 UTC+1, Sirtaj Singh Kang escribió:
>
> On 2/19/2013 3:39 PM, Calero wrote:
> [snip]
> >
> > Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server
> > certificate B: certificate verify fai
No, i'm not using passenger, i have only puppetmaster installed.
On 19 February 2013 13:27, Sirtaj Singh Kang wrote:
> On 2/19/2013 3:39 PM, Calero wrote:
> [snip]
>
>
>> Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server
>> certificate B: certificate verify failed: [certificate si
On 2/19/2013 3:39 PM, Calero wrote:
[snip]
Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server
certificate B: certificate verify failed: [certificate signature failure
for /CN=puppetmaster.domain.name]
Are you using passenger? If so, check whether the SSL cert+key files in
the web
ok, I have configured a ntp client pointing to the same ntp server and both
systems are sync, if I’m not wrong.
Puppetmaster.
root@puppetmaster:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
===
Is both servers clock in sync?
On Fri, Feb 15, 2013 at 4:20 AM, Calero wrote:
> Hi all,
>
>
>
> I'm trying to understand how puppet works, and my idea is to learn
> installing a new environment from the scratch.
>
>
>
> I have the following:
>
>
>
> Master:
>
>
>
> cat /etc/debian_version
>
> 6.0
