Chris Lee
2012-Jun-12 09:57 UTC
[Puppet Users] Dashboard with RackbaseURI / and RailsAutoDetect off
Hi all I am testing an installation on SLC 6.2 I am trying to configure my Vhost so that RailsAutoDetect is set to off, and RackBaseURI / However I keep in getting an error as follows: *Error message:* No such file or directory - config.ru *Exception class:* Errno::ENOENT *Application root:* /usr/share/puppet-dashboard If I take out the RackBaseURI statement and return the RailsAutoDetect to on, Everything works, though we want to know if its possible without the RailsAutoDetect. Below are copies of the configs when it fails *APassenger.conf *> # you probably want to tune these settings > > > LoadModule passenger_module > /usr/lib/ruby/gems/1.8/gems/passenger-3.0.12/ext/apache2/mod_passenger.so > PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-3.0.12 > PassengerRuby /usr/bin/ruby > > PassengerHighPerformance on > PassengerMaxPoolSize 12 > PassengerPoolIdleTime 1500 > # PassengerMaxRequests 1000 > PassengerStatThrottleRate 120 > RackAutoDetect Off > RailsAutoDetect Off >*Dashboard.conf*: Listen 3000> <VirtualHost *:3000> > ServerName vmm.atds.pup-05 > #RailsAutoDetect On > DocumentRoot /usr/share/puppet-dashboard/public/ > SetEnv RAILS_ENV production > RackBaseURI / > <Directory /usr/share/puppet-dashboard/public/> > AllowOverride AuthConfig > Order allow,deny > Allow from all > Options -MultiViews > </Directory> > ErrorLog /var/log/httpd/dashboard_error.log > LogLevel warn > CustomLog /var/log/httpd/dashboard_access.log combined > ServerSignature On > </VirtualHost> >*Rack.conf*> > 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/vmm-atds-pup-05.cern.ch.pem > SSLCertificateKeyFile > /var/lib/puppet/ssl/private_keys/vmm-atds-pup-05.cern.ch.pem > SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem > SSLCACertificateFile /var/lib/puppet/ssl/ca/ca_crt.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 > SSLOptions +StdEnvVars > > ErrorLog logs/puppet_error_log > TransferLog logs/puppet_access_log > LogLevel warn > # 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 /etc/puppet/rack/public/ > RackBaseURI / > <Directory /etc/puppet/rack/> > Options None > AllowOverride None > Order allow,deny > allow from all > </Directory> > </VirtualHost> > >is it possible to do this? -- 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/-/On20sw8vm-4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Chris Lee
2012-Jun-18 12:06 UTC
[Puppet Users] Re: Dashboard with RackbaseURI / and RailsAutoDetect off
Has anyone ever got this right before? -- 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/-/DiGW9XkhIF4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Maybe Matching Threads
- multiple puppet masters
- centos 6.2 - puppet 2.7.13 - SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert protocol version
- dashboard under passenger reporting over https not working
- Puppet / Passenger SSL Problems with DRBD
- puppet dashboard gui looks odd from apache2