I am new in DevOPS. Basically i want to Configure a Puppet Master Server with Passenger and Apache on CentOS

Keywords: Tomcat - Linux - Technical issue - Other
Description:
error.log

[ E 2018-03-20 11:26:02.3256 27718/T9 age/Cor/Con/CheckoutSession.cpp:285 ]: [Client 2-63] Cannot checkout session because a spawning error occurred. The identifier of the error is d69cd0fb. Please see earlier logs for details about the error. App 30348 stdout: App 30348 stdout: [ E 2018-03-20 11:26:02.6076 27718/Taw age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /usr/share/puppet/rack/puppetmasterd: An error occurred while starting up the preloader. Error ID: e12e5a83 Error details saved to: /tmp/passenger-error-aI1hLd.html Message from application: cannot load such file – puppet/util/command_line (LoadError) /usr/lib64/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in require’
/usr/lib64/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:inrequire’ config.ru:40:in block in ’
/usr/lib64/ruby/gems/2.2.0/gems/rack-2.0.4/lib/rack/builder.rb:55:ininstance_eval’ /usr/lib64/ruby/gems/2.2.0/gems/rack-2.0.4/lib/rack/builder.rb:55:in initialize’
config.ru:1:innew’ config.ru:1:in ’
/usr/lib64/ruby/gems/2.2.0/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:110:ineval’ /usr/lib64/ruby/gems/2.2.0/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:110:in preload_app’
/usr/lib64/ruby/gems/2.2.0/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:156:in’ /usr/lib64/ruby/gems/2.2.0/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:30:in module:PhusionPassenger
/usr/lib64/ruby/gems/2.2.0/gems/passenger-5.2.1/src/helper-scripts/rack-preloader.rb:29:in’

puppetmaster.conf

RHEL/CentOS:
And the passenger performance tuning settings:
PassengerHighPerformance On

Set this to about 1.5 times the number of CPU cores in your master:
PassengerMaxPoolSize 6

Recycle master processes after they service 1000 requests
PassengerMaxRequests 1000

Stop processes if they sit idle for 10 minutes
PassengerPoolIdleTime 600 Listen 8140 SSLEngine On # Only allow high security cryptography. Alter if needed for compatibility. SSLProtocol All -SSLv2 SSLCipherSuite HIGH:!ADH:RC4+RSA:-MEDIUM:-LOW:-EXP SSLCertificateFile /etc/puppetlabs/puppet/ssl/certs/prdadmin001.autocapitalcanada.local.pem SSLCertificateKeyFile /etc/puppetlabs/puppet/ssl/private_keys/prdadmin001.autocapitalcanada.local.pem SSLCertificateChainFile /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem SSLCACertificateFile /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem SSLCARevocationFile /etc/puppetlabs/puppet/ssl/ca/ca_crl.pem SSLVerifyClient optional SSLVerifyDepth 1 SSLOptions +StdEnvVars +ExportCertData # These request headers are used to pass the client certificate # authentication information on to the puppet master process RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e #RackAutoDetect On DocumentRoot /usr/share/puppet/rack/puppetmasterd/public RackBaseURI / Options None AllowOverride None Order allow,deny allow from all

Config.ru

a config.ru, for use with every rack-compatible webserver.
SSL needs to be handled outside this, though.
if puppet is not in your RUBYLIB:
$LOAD_PATH.unshift(’/opt/puppetlabs/puppet/lib/’)
$0 = “master”

if you want debugging:
ARGV << “–debug”
ARGV << “–rack”

Rack applications typically don’t start as root. Set --confdir, --vardir,
–logdir, --rundir to prevent reading configuration from
~/ based pathing.
ARGV << “–confdir” << “/etc/puppetlabs/puppet” ARGV << “–vardir” << “/opt/puppetlabs/server/data/puppetmaster” ARGV << “–logdir” << “/var/log/puppetlabs/puppetmaster” ARGV << “–rundir” << “/var/run/puppetlabs/puppetmaster” ARGV << “–codedir” << “/etc/puppetlabs/code”

disable always_retry_plugsin as a performance improvement. This is safe for a master to
apply. This is intended to allow agents to recognize new features that may be
delivered during catalog compilation.
ARGV << “–no-always_retry_plugins”

NOTE: it’s unfortunate that we have to use the “CommandLine” class
here to launch the app, but it contains some initialization logic
(such as triggering the parsing of the config file) that is very
important. We should do something less nasty here when we’ve
gotten our API and settings initialization logic cleaned up.

Also note that the “$0 = master” line up near the top here is
the magic that allows the CommandLine class to know that it’s
supposed to be running master.

–cprice 2012-05-22
require ‘puppet/util/command_line’

we’re usually running inside a Rack::Builder.new {} block,
therefore we need to call run here.
run Puppet::Util::CommandLine.new.execute

So please help me in resolving this error… Your help would be highly appreciated.

Hi,

This Community forum is intended to solve problems related to the Bitnami Stacks, Virtual Machine or Cloud Images.

For information regarding the application itself or customization of the content within the application, we highly recommend checking forums and user guides made available by the project behind the application or generic sites like https://stackoverflow.com/ or https://serverfault.com/.

Best regards,
Carlos R. Hernández

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.