Is both servers clock in sync?
On Fri, Feb 15, 2013 at 4:20 AM, Calero <francisco.cal...@ngahr.com> 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.6
>
> puppet --version
>
> 3.1.0
>
> cat /etc/hosts
>
> 127.0.1.1 puppetmaster.domain.name puppetmaster puppet
>
>
>
> Client:
>
>
>
> cat /etc/SuSE-release
>
> SUSE Linux Enterprise Server 11 (x86_64)
>
> VERSION = 11
>
> PATCHLEVEL = 2
>
>
>
> puppet --version
>
> 2.6.12
>
> cat /etc/hosts
>
> 127.0.0.1 puppetclient01.domain.name puppetclient01
>
> 192.168.203.128 puppet puppetmaster.domain.name
>
>
>
> puppet agent --test
>
> info: Creating a new SSL key for puppetclient01.domain.name
>
> warning: peer certificate won't be verified in this SSL session
>
> warning: peer certificate won't be verified in this SSL session
>
> info: Creating a new SSL certificate request for puppetclient01.domain.name
>
> info: Certificate Request fingerprint (md5):
> 88:B5:17:BF:DD:39:90:ED:0D:1A:9D:3C:A7:51:8C:D3
>
> warning: peer certificate won't be verified in this SSL session
>
> warning: peer certificate won't be verified in this SSL session
>
> warning: peer certificate won't be verified in this SSL session
>
> Exiting; no certificate found and waitforcert is disabled
>
>
>
> Once I sign it in the server….
>
>
>
> puppetclient01:~ # puppet agent --test
>
> warning: peer certificate won't be verified in this SSL session
>
> info: Caching certificate for puppetclient01.domain.name
>
> err: Could not retrieve catalog from remote server: SSL_connect returned=1
> errno=0 state=SSLv3 read server certificate B: certificate verify failed
>
> warning: Not using cache on failed catalog
>
> err: Could not retrieve catalog; skipping run
>
>
>
> puppet agent --test
>
> err: Could not retrieve catalog from remote server: SSL_connect returned=1
> errno=0 state=SSLv3 read server certificate B: certificate verify failed
>
> warning: Not using cache on failed catalog
>
> err: Could not retrieve catalog; skipping run
>
> ----------------------
>
>
>
> In this point is where i'm struck right now, i have deleted several times
> all certificates both hosts and i'm getting the same kind of error.
>
>
>
> And this is the ouput if i try to do it in the same server.
>
>
>
> ------------------
>
> puppet agent --test
>
> 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: [certificate signature failure for
> /CN=puppetmaster.domain.name]
>
> Info: Retrieving plugin
>
> Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources
> using 'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server
> certificate B: certificate verify failed: [certificate signature failure for
> /CN=puppetmaster.domain.name]
>
> Error: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect
> returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify
> failed: [certificate signature failure for /CN=puppetmaster.domain.name]
> Could not retrieve file metadata for
> puppet://puppetmaster.domain.name/plugins: SSL_connect returned=1 errno=0
> state=SSLv3 read server certificate B: certificate verify failed:
> [certificate signature failure for /CN=puppetmaster.domain.name]
>
> Error: Could not retrieve catalog from remote server: SSL_connect returned=1
> errno=0 state=SSLv3 read server certificate B: certificate verify failed:
> [certificate signature failure for /CN=puppetmaster.domain.name]
>
> Warning: Not using cache on failed catalog
>
> Error: Could not retrieve catalog; skipping run
>
> Error: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3
> read server certificate B: certificate verify failed: [certificate signature
> failure for /CN=puppetmaster.domain.name]
>
>
>
>
>
> Thanks
>
>
> ________________________________
>
> This email is sent on behalf of Northgate Information Solutions Limited and
> its associated companies ("Northgate") and is strictly confidential and
> intended solely for the addressee(s).
>
> If you are not the intended recipient of this email you must: (i) not
> disclose, copy or distribute its contents to any other person nor use its
> contents in any way or you may be acting unlawfully; (ii) contact Northgate
> immediately on +44 (0)1442 232424 quoting the name of the sender and the
> addressee then delete it from your system.
>
> Northgate has taken reasonable precautions to ensure that no viruses are
> contained in this email, but does not accept any responsibility once this
> email has been transmitted. You should scan attachments (if any) for
> viruses.
>
> ________________________________
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
