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 can I recreate my server's original (or a new) 
keypair?

On Monday, July 2, 2018 at 9:18:40 AM UTC-4, Patrick Lesher wrote:
>
> 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 VM so I could take a snapshot and 
> play around with it.
>
>
> In the end I did an upgrade to the latest 2018 ( it was 2017.x ) and 
> everything came up working.  I’m not sure if that will help you but it 
> solved our problem.
>
>
>
> On Jul 2, 2018, at 7:35 AM, Bret Wortman <[email protected] 
> <javascript:>> wrote:
>
> 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 puppetserver: at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> puppet puppetserver: at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> puppet puppetserver: at java.lang.Thread.run(Thread.java:748)
> puppet puppetserver: Background process 4918 exited before start had 
> completed
> puppet systemd: puppetserver.service: control process exited, code=exited 
> status=1
> puppet systemd: Failed to start puppetserver Service.
> puppet systemd: Unit puppetserver.service entered failed state.
> puppet systemd: puppetserver.service failed.
> puppet systemd: puppetserver.service holdoff time over, scheduling restart
> puppet systemd: Starting puppetserver Service...
> puppet puppetserver: OpenJDK 64-Bit Server VM warning: ignoring option 
> MaxPermSize=256m; support was removed in 8.0
>
> Any thoughts about where to look next for a solution, or at least a more 
> in-depth understanding of what's going on? This server has been in 
> operation for several years without any issues until we stomped something...
>
> Thanks,
>
> -- 
> 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 [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/39635033-2e37-49de-8e86-493c7829654a%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/puppet-users/39635033-2e37-49de-8e86-493c7829654a%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ece21bcf-c424-447c-ba71-5a3d373c9b90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to