Couldn't start puppet 4.2

asked 2015-07-30 09:45:19 -0500

hiero_nymus
1 ●3 ●3 ●4

updated 2015-07-30 09:49:23 -0500

Hi There,

When I starting puppet 4.2 service puppetserver start, following errors appears.

[...] 2015-07-30 16:03:38,817 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. [...] Caused by: org.jruby.embed.EvalFailedException: (Error) Cannot determine basic system flavour [...]

I've seen the following know issue but I don't know if is a related problem : Ruby 1.8 vs Ruby 1.9.

As anyone the same problem or as an idea?

P.S.-: Should the puppet client be configured too? Because actually I've only installed and configured the Master server. Regards

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2015-07-30 12:11:13 -0500

johnnyb04
71 ●2 ●4 ●8

No, you don't need to configure a client for a Puppet server to run. Have you looked at the following URL? It seems somewhat related. Be sure to check out the first comment at the bottom of the page and the link provided.

https://tickets.puppetlabs.com/browse/ENTERPRISE-676

edit flag offensive delete link

add a comment

answered 2015-08-04 09:23:52 -0500

hiero_nymus
1 ●3 ●3 ●4

updated 2015-08-04 09:25:35 -0500

Thank you for your reply but unfortunately the link doesn't correspond to my problem.. I'm running CentOS. Here is the error's message: ERROR [p.t.internal] shutdown-on-error triggered because of exception!

and here in the details:

1) java.lang.IllegalStateException:There was a problem adding a JRubyPuppet instance to the pool

2) Caused by: org.jruby.embed.EvalFailedException: (Error) Cannot determine basic system flavour

I don't know what I have to check. I see nothing anymore...

I've find the following, could it be a problem?

 # /opt/puppetlabs/bin/puppetserver ruby --version
jruby 1.7.20.1 (1.9.3p551) 2015-06-10 d7c8c27 on OpenJDK 64-Bit Server VM 1.8.0_51-b16 +jit [linux-amd64]
# ruby --version
ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]

It is the right way to start the service?: