Many thanks for the help -- I managed to get it going
The other problem I had for the record was that I set the server_url to
localhost while the server's CA was in its real name and that caused all
sorts of confusion.
Regards
Scott
--
You received this message because you are subscribed
If you're reaching expiry you might consider this thing, it worked for me to
refresh the CA cert:
https://forge.puppet.com/puppetlabs/certregen
(NB, check all your puppetserver/puppetmaster hosts for stray puppet/ssl/ca
directories, having extra ones around can cause a bit of pain. Make sure
I did, by building a new server. That said, I'd try this advice before
starting over:
https://puppet.com/docs/puppet/5.5/ssl_regenerate_certificates.html
For us it was also a change to move from a monolithic, everything on one
server architecture to something a bit more distributed.
On Thu, Jul
Were you able to resolve this issue? I am now getting the same problem
Thanks
Scott
--
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
Aha! According to the puppetserver.log, I've got a weird keypar:
ERROR [async-dispatch-2] [p.t.internal] Error during service init!!!
java.lang.IllegalArgumentException: Expected a KeyPair or PrivateKey, got
org.bouncycastle.openssl.PEMEncryptedKeyPair@748f579b
:
:
What is this thing, and how
One of our guys did something similar a couple weeks ago and we didn’t have a
backup. It sounds like ours was a little different in that the server was
running fine, remote agents could connect, process, etc, but the puppet
master’s agent refused to run.
Ours is a mono deployment on a single
I accidentally ran puppet agent on our puppet master and now puppet server
won't start up any more. Multiple reboots have failed to clear the
situation and I can't figure out what file changed.
Here's the tail end of /var/log/messages | grep puppetserver, minus the
datestamps:
:
puppet
