Stefan,
That is a very weird error. The way it reads it sounds like something that
should happen on every JRuby instance or on none of them
("NoClassDefFoundError" usually means it's trying to load some code that
doesn't exist), so I wouldn't expect you to see a difference in behavior
between 16 instances and 32 instances.
It might be best if you open a bug about this on our issue tracker:
https://tickets.puppetlabs.com/browse/SERVER , so that we can get some
other folks to weigh in on it... would you mind doing that?
On Tuesday, August 25, 2015 at 12:05:54 PM UTC+1, Dietrich, Stefan wrote:
>
> Hello,
>
> we tried to today to migrate our Puppet Masters from Apache/Passenger to
> Puppet Server 1.1.1.
> However, Puppet Server just dies with error messages as soon as we
> increase the number of JRuby instances to >24 and a JVM heapsize of > 16GB.
>
> During startup of Puppet Server, it starts to spawn the JRuby instances
> one after another and around ~8 instances an exception is logged:
> 2015-08-25 10:25:05,676 INFO [puppet-server] Puppet Puppet settings
> initialized; run mode: master
> 2015-08-25 10:25:06,254 INFO [p.s.j.jruby-puppet-agents] Finished
> creating JRubyPuppet instance 7 of 32
> 2015-08-25 10:25:08,567 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: (LoadError) load error:
> jopenssl/load -- java.lang.NoClassDefFoundError:
> org/jruby/ext/openssl/NetscapeSPKI
> at
> org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:132)
> ~[puppet-server-release.jar:na]
> at
> org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1341)
> ~[puppet-server-release.jar:na]
>
> The full log file is available in this Gist [1].
> The log file is from the initial setup with max-active-instances set to 32
> and a JVM heap size of 48gb.
> We had a working setup with 16GB Heap and 16 instances. Sometimes 24
> worked as well, but not always.
> However, 16 instances will be too small to handle all the Puppet agents.
> Increasing the timeout in /etc/sysconfig/puppetserver did not help either.
>
> We use rather beefy HW for our 3x Puppet Masters (2x Dell R715, 1x R815),
> for Apache/Passenger this scaled nicely.
>
> The OS on the Puppet Masters is Scientific Linux 6.6 (RHEL 6.6 clone) and
> OpenJDK 8 is used.
> We tried the Oracle JRE as well, but this did not change anything.
> HTTPS is terminated at our F5 Loadbalancer, which forwards the traffic
> unencrypted to Puppet Server.
>
> Any help would be appreciated!
>
> [1] https://gist.github.com/stdietrich/5a5b8f9b1dc2445c3ec7
>
> Regards,
> Stefan
>
> --
> ------------------------------------------------------------------------
> Stefan Dietrich Deutsches Elektronen-Synchrotron (IT-Systems)
> Ein Forschungszentrum der Helmholtz-Gemeinschaft
> Notkestr. 85
> phone: +49-40-8998-4696 22607 Hamburg
> e-mail: stefan....@desy.de <javascript:>
> Germany
> ------------------------------------------------------------------------
>
--
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/f38505c9-8793-45d4-bee0-1aa0f45bdf94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
