Description
To reproduce if you don't hit the issue on boot of EL 7 then you can just do the following.
service pe-puppet stop
|
rm -rf /var/run/pe-puppet/
|
service pe-puppetserver restart
|
Check your /var/log/pe-puppetserver/puppetserver.log for errors like:
2015-02-08 01:47:52,045 ERROR [puppet-server] Puppet Could not set 'directory' on ensure: Permission denied - /var/run/pe-puppet
|
org/jruby/RubyDir.java:443:in `mkdir'
|
or
2015-02-08 01:47:52,087 ERROR [puppet-server] /File[/var/run/pe-puppet]/ensure change from absent to directory failed: Could not set 'directory' on ensure: Permission denied - /var/run/pe-puppet
|
2015-02-08 01:47:52,181 ERROR [p.t.internal] shutdown-on-error triggered because of exception!
|
java.lang.IllegalStateException: There was a problem adding a JRubyPuppet instance to the pool.
|
You can correct the issue by starting the pe-puppet service or creating the directory with the correct permissions.
Attachments
Issue Links
- blocks
-
ENTERPRISE-502 pe-puppetserver and pe-console-services not starting after reboot on new PE install on Ubuntu 14.04
-
- Resolved
-
- relates to
-
ENTERPRISE-425 Order of service starts can cause issues
-
- Resolved
-
-
SERVER-336 Puppetserver on EL7 or Ubuntu 14.04 does not always work after a reboot
-
- Closed
-
- mentioned in
-
Page Loading...