diff options
| author | Matt Robinson <matt@puppetlabs.com> | 2011-07-19 11:27:03 -0700 |
|---|---|---|
| committer | Matt Robinson <matt@puppetlabs.com> | 2011-07-26 12:57:31 -0700 |
| commit | 1d4acb5afda61b1f2c05223afff19c68248a3996 (patch) | |
| tree | 0b014e631e95b1de40a5d015db724e4715c124e3 /lib/puppet/rails/rails_resource.rb | |
| parent | 8baa4897e777f9515dc1663317f432ace3067bae (diff) | |
| download | puppet-1d4acb5afda61b1f2c05223afff19c68248a3996.tar.gz puppet-1d4acb5afda61b1f2c05223afff19c68248a3996.tar.xz puppet-1d4acb5afda61b1f2c05223afff19c68248a3996.zip | |
maint: Suggest where to start troubleshooting SSL error message
Much like the infamous "hostname was not match" error message, there's
another SSL error that people run into that isn't clear how to
troubleshoot.
err: Could not send report: SSL_connect returned=1 errno=0
state=SSLv3 read server certificate B: certificate verify failed.
As far as I can tell this only ever happens when the clock is off on the
master or client. People seem to think it will happen other times, but
I haven't been able to reproduce it other ways - missing private key,
revoked cert, offline CA all have their own errors. I googled around
and the only thing I've seen for this error in relation to puppet is the
time sync problem.
So the error message text just has some additional info to suggest you
check your clocks.
Reviewed-by: Nick Lewis <nick@puppetlabs.com>
Diffstat (limited to 'lib/puppet/rails/rails_resource.rb')
0 files changed, 0 insertions, 0 deletions