Puppet users - Nov 2008 - Some cert problem

Bunch of weird stuff after a power failure here this morning.  One of my
virtual servers, managed through puppet, seems to not be talking to the
master any more.  And I can''t get it to reconnect.  I did puppetca
--clean
on the master, cleaned off certs on the client, started puppetd manually
on the client, and got this:

sh-3.2# rm -rf /var/lib/puppet/ssl/
sh-3.2# puppetd --server prcapp00 --verbose --no-daemonize
info: Creating a new certificate request for vl31.pinerivercapital.loca\
l
info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/vl31.p\
inerivercapital.local.pem
warning: peer certificate won''t be verified in this SSL session
notice: Did not receive certificate
notice: Got signed certificate
notice: Starting Puppet client version 0.24.5
warning: Certificate validation failed; considering using the certname \
configuration option
err: Could not retrieve catalog: Certificates were not trusted: hostnam\
e not match with the server certificate
notice: Starting catalog run
warning: Certificate validation failed; considering using the certname \
configuration option

(The signing request appeared on the master, and I signed it, at the right
point in the above sequence.)


[ddb@prcapp00 ~]$ sudo puppetca --sign vl31.pinerivercapital.local
Could not load confine test ''operatingsystem'': No such file to
load --
puppet/provider/confine/operatingsystem
Could not load confine test ''operatingsystem'': No such file to
load --
puppet/provider/confine/operatingsystem
Could not load confine test ''operatingsystem'': No such file to
load --
puppet/provider/confine/operatingsystem
Signed vl31.pinerivercapital.local

(Googling seems to show those warnings aren''t important?)

So what''s going on here?  The certificate signing request showed up,
and
the client acknowledged getting the signed certificate, so I don''t have
a
really basic network or config problem here.





-- 
David Dyer-Bennet, dd-b@dd-b.net; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Sorry to follow up to myself, but I found the problem.

I need to use the FQDN for the server on the command line, not just
the host name.

The error messages don''t suggest that as the problem at all.  And the
fact that the certificate showed up in the signing queue on the server
made me rule that out as a possible problem.  But that''s the problem
anyway; changing the command to use the FQDN (after wiping out the
cert on both sides again) worked fine.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---