Quantcast
Channel: Ask Puppet: Puppet DevOps Q&A Community - RSS feed
Viewing all articles
Browse latest Browse all 6104

unable to start httpd when using puppetmaster.conf

$
0
0
Hi I am trying to use puppetmaster-passenger' with httpd. However when I put the puppetmaster.conf in /etc/httpd/conf.d/ with the content advised in the instructions I the error below: -- Unit httpd.service has begun starting up. Aug 20 04:39:26 puppetmaster.com httpd[8484]: AH00526: Syntax error on line 16 of /etc/httpd/conf.d/puppetmaster.conf: Aug 20 04:39:26 puppetmaster.com httpd[8484]: Invalid command 'PassengerMaxPoolSize', perhaps misspelled or defined by a module not included in the server configuration Aug 20 04:39:26 puppetmaster.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE Aug 20 04:39:26 puppetmaster.com kill[8488]: kill: cannot find process "" Aug 20 04:39:26 puppetmaster.com systemd[1]: httpd.service: control process exited, code=exited status=1 Aug 20 04:39:26 puppetmaster.com systemd[1]: Failed to start The Apache HTTP Server. -- Subject: Unit httpd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit httpd.service has failed. -- -- The result is failed. Aug 20 04:39:26 puppetmaster.com systemd[1]: Unit httpd.service entered failed state. Aug 20 04:39:26 puppetmaster.com systemd[1]: httpd.service failed. Aug 20 04:39:27 puppetmaster.com polkitd[678]: Unregistered Authentication Agent for unix-process:8468:6940078 (system bus name :1.523, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.U Aug 20 04:40:01 puppetmaster.com systemd[1]: Started Session 140 of user root. -- Subject: Unit session-140.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel Here is the content of the puppetmaster.conf file: # You'll need to adjust the paths in the Passenger config depending on which OS # you're using, as well as the installed version of Passenger. # Debian/Ubuntu: #LoadModule passenger_module /var/lib/gems/1.8/gems/passenger-4.0.x/ext/apache2/mod_passenger.so #PassengerRoot /var/lib/gems/1.8/gems/passenger-4.0.x #PassengerRuby /usr/bin/ruby1.8 # RHEL/CentOS: #LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-4.0.x/ext/apache2/mod_passenger.so #PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-4.0.x #PassengerRuby /usr/bin/ruby # And the passenger performance tuning settings: # Set this to about 1.5 times the number of CPU cores in your master: PassengerMaxPoolSize 12 # Recycle master processes after they service 1000 requests PassengerMaxRequests 1000 # Stop processes if they sit idle for 10 minutes PassengerPoolIdleTime 600 Listen 8140 # Make Apache hand off HTTP requests to Puppet earlier, at the cost of # interfering with mod_proxy, mod_rewrite, etc. See note below. PassengerHighPerformance On SSLEngine On # Only allow high security cryptography. Alter if needed for compatibility. SSLProtocol ALL -SSLv2 -SSLv3 SSLCipherSuite EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA SSLHonorCipherOrder on SSLCertificateFile /var/lib/puppet/ssl/certs/puppetmaster.com.pem SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/puppetmaster.com.pem SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem SSLCACertificateFile /var/lib/puppet/ssl/ca/ca_crt.pem SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crt.pem SSLCARevocationCheck chain SSLVerifyClient optional SSLVerifyDepth 1 SSLOptions +StdEnvVars +ExportCertData # Apache 2.4 introduces the SSLCARevocationCheck directive and sets it to none # which effectively disables CRL checking. If you are using Apache 2.4+ you must # specify 'SSLCARevocationCheck chain' to actually use the CRL. # 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 DocumentRoot /usr/share/puppet/rack/puppetmasterd/public Options None AllowOverride None # Apply the right behavior depending on Apache version. Order allow,deny Allow from all= 2.4> Require all granted ErrorLog /var/log/httpd/puppet-server.example.com_ssl_error.log CustomLog /var/log/httpd/puppet-server.example.com_ssl_access.log combined I would really appreciate some help on this issue, Please update me if you need more information.

Viewing all articles
Browse latest Browse all 6104

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>