[Puppet Users] Puppetserver won't start

2018-07-02 Thread Bret Wortman
After accidentally running puppet agent on our puppet server, the server no 
longer works. I've run a "yum reinstall puppetserver" on it to no avail.

What's happening is that it keeps trying to start but fails for some 
reason. /var/log/messages shows:

:
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.

Any thoughts about what to check next to see why this is failing?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/461e5335-006c-47e8-ab0a-ec801496cf41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: Can we install.. Oracle, weblogic, Notepad++ and tomcat using Puppet

2018-07-02 Thread dhananjay patade
Josh, did you use https://forge.puppetlabs.com/biemond/orawls for managed 
server creation. I am trying to create managed server but not able to 
figure out how to do it. Can you please share steps to create managed 
server using orawls module.

On Thursday, June 25, 2015 at 7:46:22 PM UTC+5:30, Josh Sinfield wrote:
>
> Hi Santosh,
>
> yes you can. We do at our company.
>
> I recommend https://forge.puppetlabs.com/biemond/orawls for Weblogic.
>
> For oracle 11g client we wrote a module which currently cannot be open 
> sourced as it's got some company specific data in it.
>
> we also wrote a module for notepad++ but again, it has some company 
> specific data in it.
>
> if by oracle you mean java, then I recommend this module: 
> https://forge.puppetlabs.com/biemond/jdk7
>
> For tomcat we use PuppetLabs own tomcat module which you can also find on 
> the puppet forge.
>
> HTH,
> Josh
>
> On Wednesday, 24 June 2015 13:49:30 UTC+1, Santosh Gaddam wrote:
>>
>> Can we install.. Oracle, weblogic, Notepad++ and tomcat using Puppet..
>> if yes what is the process for this...
>>
>> i have one doubt apart from default classes can we install more products 
>> using this...? 
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6cd98817-46fd-4c2b-aadb-e7a3d8447d9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Puppet server stopped working

2018-07-02 Thread Bret Wortman
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  > 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 puppet-users...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/39635033-2e37-49de-8e86-493c7829654a%40googlegroups.com
>  
> 
> .
> 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 puppet-users+unsubscr...@googlegroups.com.
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.


[Puppet Users] Re: Puppet server stopped working

2018-07-02 Thread Bret Wortman
Further to this, journalctl -xe has this to contribute when I try to start 
it up:

:
systemd[1]: Unit puppetserver.service entered failed state.
systemd[1]: puppetserver.service failed.
polkitd[632]: Unregistered Authentication Agent for 
unix-process:16477:1258070 (system bus name :1.652, object pathy 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_us.UTF
:



On Monday, July 2, 2018 at 8:35:33 AM UTC-4, Bret Wortman 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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7a4aefa7-5e9f-4c98-a7e9-e97b8e2ab474%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Puppet server stopped working

2018-07-02 Thread Patrick Lesher
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  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 puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/39635033-2e37-49de-8e86-493c7829654a%40googlegroups.com
>  
> .
> 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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1D21CE3C-83A5-487C-8C12-D003564B0634%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Puppet server stopped working

2018-07-02 Thread Bret Wortman
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/39635033-2e37-49de-8e86-493c7829654a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.