Hello everyone. I'm asking this question with reluctance; but I've been 
working on this upgrade for most of the day. I had a working Kubuntu 12.04 
puppet master 2.7.19 with most clients at 2.7.19 as well. I'm trying to 
upgrade the puppetmaster to 3.0.1 for the speed improvements. Upgrading via 
apt generated unwelcome errors that I need not go into here. Let's just say 
that I uninstalled all ruby versions & ruby gems and started from scratch.

So now I have puppet 3.0.1 installed from the puppetlabs debian repo and I 
thought I'd fought my way through the thicket, but I've hit a wall with 
this error When running puppet agent on the clients. I get the following 
error:

Ruby (Rack) application could not be started


*Error message:*undefined method `settings' for Puppet:Module*Exception 
class:*NoMethodError*Application root:* /etc/puppet/rack/puppetmaster
*Backtrace:*  # File Line Location  0   
/usr/lib/ruby/vendor_ruby/puppet/application.rb    273  in `run_mode'  1   
/usr/lib/ruby/vendor_ruby/puppet/application/master.rb    5 
 2   /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb    36 in 
`gem_original_require'  3   
/usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb    36 in `require'  
4   config.ru    13 
 5   /var/lib/gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb    46 in 
`instance_eval'  6   /var/lib/gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb    
46 in `initialize'  7   config.ru    1 in `new'  8   config.ru

My puppetmaster site and conf files are attached. I'd be under many 
obligations for some help.

TIA,

Dave

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/3BNJL8OuZVsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

# you probably want to tune these settings
PassengerHighPerformance on
PassengerMaxPoolSize 12
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
RackAutoDetect Off
RailsAutoDetect Off

Listen 8140

<VirtualHost *:8140>
        SSLEngine on
        SSLProtocol -ALL +SSLv3 +TLSv1
        SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP

        #SSLCertificateFile      
/var/lib/puppet/ssl/certs/bearkub.thinkwell.lan.pem
        SSLCertificateFile      
/var/lib/puppet/ssl/certs/puppet.thesecurityappliance.com.pem
        SSLCertificateKeyFile   
/var/lib/puppet/ssl/private_keys/bearkub.thinkwell.lan.pem
        SSLCertificateChainFile /var/lib/puppet/ssl/certs/ca.pem
        SSLCACertificateFile    /var/lib/puppet/ssl/certs/ca.pem
        # If Apache complains about invalid signatures on the CRL, you can try 
disabling
        # CRL checking by commenting the next line, but this is not recommended.
        SSLCARevocationFile     /var/lib/puppet/ssl/ca/ca_crl.pem
        SSLVerifyClient optional
        SSLVerifyDepth  1
        # The `ExportCertData` option is needed for agent certificate 
expiration warnings
        SSLOptions +StdEnvVars +ExportCertData

        # This header needs to be set if using a loadbalancer or proxy
        RequestHeader unset X-Forwarded-For

        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/
        RackBaseURI /
        <Directory /usr/share/puppet/rack/puppetmasterd/>
                Options None
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>
</VirtualHost>


LoadModule passenger_module 
/var/lib/gems/1.8/gems/passenger-2.2.11/ext/apache2/mod_passenger.so
PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
PassengerRuby /usr/bin/ruby1.8

# Recommended Passenger Configuration
PassengerHighPerformance on
PassengerUseGlobalQueue on
# PassengerMaxPoolSize control number of application instances,
# typically 1.5x the number of processor cores.
PassengerMaxPoolSize 10
# Restart ruby process after handling specific number of request to resolve MRI 
memory leak.
PassengerMaxRequests 4000
# Shutdown idle Passenger instances after 30 min.
PassengerPoolIdleTime 1800
# End of /etc/httpd/conf.d/10_passenger.conf

# /etc/httpd/conf.d/20_puppetmaster.conf
# Apache handles the SSL encryption and decryption. It replaces webrick and 
listens by default on 8140
Listen 8140
<VirtualHost *:8140>

SSLEngine on
SSLProtocol -ALL +SSLv3 +TLSv1
SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
# Puppet master should generate initial CA certificate.
# ensure certs are located in /var/lib/puppet/ssl
# Change puppet.example.com to the fully qualified domain name of the Puppet 
master, i.e. $(facter fqdn).
SSLCertificateFile /var/lib/puppet/ssl/certs/puppet.thesecurityappliance.com.pem
SSLCertificateKeyFile 
/var/lib/puppet/ssl/private_keys/puppet.thesecurityappliance.com.pem
SSLCertificateChainFile /var/lib/puppet/ssl/certs/ca.pem
SSLCACertificateFile /var/lib/puppet/ssl/ca/ca_crt.pem
# CRL checking should be enabled
# disable next line if Apache complains about CRL
SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem
# optional to allow CSR request, required if certificates distributed to client 
during provisioning.
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +StdEnvVars
# The following client headers record authentication information for down 
stream workers.
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 /etc/puppet/rack/puppetmaster/public/
<Directory /etc/puppet/rack/puppetmaster/>
Options None
AllowOverride None
Order allow,deny
allow from all
</Directory>
</VirtualHost>
# /etc/httpd/conf.d/20_puppetmaster.conf

Reply via email to