This is what I have in my httpd.conf file and apache is running as the user puppet -
LoadModule passenger_module /opt/passenger-2.2.15/ext/apache2/ mod_passenger.so PassengerRoot /opt/passenger-2.2.15 PassengerRuby /usr/bin/ruby PassengerHighPerformance on PassengerMaxPoolSize 20 PassengerPoolIdleTime 1500 PassengerStatThrottleRate 120 PassengerDefaultUser puppet RailsAutoDetect On On Aug 21, 1:54 pm, Patrick <kc7...@gmail.com> wrote: > On Aug 21, 2010, at 10:37 AM, Rustler wrote: > > > One thing I found when trying to get both working in apache is that > > the passenger and rails setting in both files were stomping on each > > other. > > > Dashboard needed "RailsAutoDetect On" which was getting turned off by > > the other vhost file. > > > I deleted the settings from each vhost file and put one set in > > httpd.conf after the loading of the passenger module. > > > I now have puppet master 2.6.0 and dashboard working in apache 2. > > So did you end up using RailsAutoDetect off or on? > > > On Aug 20, 12:21 pm, Asif Iqbal <vad...@gmail.com> wrote: > >> I downloaded the puppet-dashboard.git > >> fromhttp://github.com/puppetlabs/puppet-dashboardanddid the installation > >> in my > >> ubuntu lucid puppet server following the steps in "Installation". > > >> Now I can run it fine using the WEBrick like this > > >> r...@sys-ubuntu { ~/git/puppet-dashboard }$ ./script/server -e production > >> => Booting WEBrick > >> => Rails 2.3.5 application starting onhttp://0.0.0.0:3000 > >> => Call with -d to detach > >> => Ctrl-C to shutdown server > >> [2010-08-20 15:06:23] INFO WEBrick 1.3.1 > >> [2010-08-20 15:06:23] INFO ruby 1.8.7 (2010-04-19) [x86_64-linux] > >> [2010-08-20 15:06:23] INFO WEBrick::HTTPServer#start: pid=8489 port=3000 > > >> And I can see all the nodes through the web. > > >> Bu I am failing to see it in the apache2 + passenger. I am using > >> apache2 + passenger to run puppet master and that is > >> working fine. So no issue with apache2 + passenger. > > >> I need help with the virtualhost config, so that I can see the nodes > >> through the apache2's web > > >> I copied the ext/passenger/dashboard-vhost.conf exactly as it it and > >> started on port 8080. But I do only see > >> the directories and not the rails view of node. > > >> # tail /etc/apache2/apache2.conf (works perfect) > > >> # Passenger > >> LoadModule passenger_module > >> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/ext/apache2/mod_passenger.so > >> PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15 > >> PassengerRuby /usr/bin/ruby1.8 > > >> # cat /etc/apache2/conf.d/puppetmasterd (works perfect) > > >> # 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/sys-ubuntu.arl.qwestip.net.pem > >> SSLCertificateKeyFile > >> /var/lib/puppet/ssl/private_keys/sys-ubuntu.arl.qwestip.net.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 > > >> 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> > > >> So as you can see from below apache2's passenger modules spawns puppet > >> master just fine > > >> $ ps -ef | grep a[p]ache2 > >> root 7448 1 0 15:02 ? 00:00:00 /usr/sbin/apache2 -k start > >> www-data 7450 7448 0 15:02 ? 00:00:00 /usr/sbin/apache2 -k start > >> root 7469 7448 0 15:02 ? 00:00:00 > >> /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/ext/apache2/ApplicationPoolServerExecutable > >> 0 /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/bin/passenger-spawn-server > >> /usr/bin/ruby1.8 /tmp/passenger.7448 > >> www-data 7473 7448 0 15:02 ? 00:00:00 /usr/sbin/apache2 -k start > >> www-data 7474 7448 0 15:02 ? 00:00:00 /usr/sbin/apache2 -k start > > >> $ ps -ef | grep p[u]ppet > >> puppet 7565 1 0 15:02 ? 00:00:05 master > >> puppet 7888 1 0 15:03 ? 00:00:03 master > > >> But puppet-dashboard is not quite working. vhost starts fine, but the > >> gui only shows files > > >> $ cat /etc/apache2/conf.d/dashboard-vhost.conf > >> PassengerHighPerformance on > >> PassengerMaxPoolSize 12 > >> PassengerPoolIdleTime 1500 > >> PassengerStatThrottleRate 120 > >> RailsAutoDetect On > > >> Listen 9000 > >> <VirtualHost *:9000> > >> DocumentRoot /usr/share/puppet-dashboard/public/ > >> <Directory /usr/share/puppet-dashboard/public/> > >> Options +Indexes > >> AllowOverride AuthConfig > >> Order allow,deny > >> allow from all > >> </Directory> > >> ErrorLog /var/log/apache2/dashboard.example.com_error.log > >> LogLevel warn > >> CustomLog /var/log/apache2/dashboard.example.com_access.log combined > >> ServerSignature On > >> </VirtualHost> > > >> so apache2 starts fine for puppet (port 8140) and for > >> puppet-dashboard(port 9000) > > >> tcp 0 0 0.0.0.0:9000 0.0.0.0:* > >> LISTEN 7448/apache2 > >> tcp 0 0 0.0.0.0:8140 0.0.0.0:* > >> LISTEN 7448/apache2 > > >> But when I visit the page on port 9000 I only get the list of files > >> and dirs. It does > >> not look anything like the webrick gui. > > >> Anyidea what I am doing wrong. I thought I followed the > >> README.markdown correctly > >> from the puppet-dashboard.git > > >> The /usr/share/puppet-dashboard is the git clone of puppet-dashboard.git > > >> -- > >> Asif Iqbal > >> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu > >> A: Because it messes up the order in which people normally read text. > >> Q: Why is top-posting such a bad thing? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
