[Puppet Users] extlookup in 2.6.1 defaults
Hmmm
So I was just trying the extlookup function that comes with puppet
2.6.1. It now lets you do this:
$version = extlookup("rsyslog_version", "present", "packages")
which, according to the documentation:
# This will look for a version configured in packages.csv and then in
the rest as configured
# by $extlookup_precedence if it's not found anywhere it will default
to "present", this kind
# of use case makes puppet a lot nicer for managing large amounts of
packages since you do not
# need to edit a load of manifests to do simple things like adjust a
desired version number.
This seems a bit weird to me. The second parameter isn't optional (I
think the 2nd and 3rd parameters should be switched), which means that
you MUST have a default value in there, which means, you might as well
use the same value as in the file, which means the file is somewhat
redundant. Anyone else see that?
Doug.
--
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.
[Puppet Users] Where does extlookup go?
Where does extlookup get copied to on the puppetmaster for 2.6.1? In my 0.24.8 installation, it's running happily in /var/lib/puppet/parser/functions. However, 2.6 doesn't have a parser directory. I created a parser/functions directory, and got this: Could not retrieve catalog from remote server: Error 400 on SERVER: Unknown function extlookup at /etc/puppet/modules/elements/manifests/tfel0.pp:18 on node app01.pax.xxx.com Also happens when I put it in /var/lib/puppet. Where does it belong? It's not actually documented IN the script. (hint: this would be very useful to know). Doug -- 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.
Re: [Puppet Users] Debugging errors with external nodes
On Sat, Aug 21, 2010 at 4:19 PM, Jeff McCune wrote:
> On Sat, Aug 21, 2010 at 3:59 PM, Douglas Garstang
> wrote:
>> My site.pp:
>>
>> node default {
>> }
>
> Your empty node classification is entirely consistent with the terse
> agent output you pasted.
That's not what is happening. It is finding the app01 node, and then
webrick barfs and dumps a backtrace. The puppetmaster then complains
it can't find a catalog for app01, and the client ends up doing
nothing.
Doug.
--
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.
[Puppet Users] Neverending Scope Issues
Lets say I have this for an external node: classes: software::application environment: production parameters: appvar1: appkey1 ... appvarN: appkeyN The software::application class can access the appvarN variables. I keep seeing people here say stuff like 'oh just move it up into a class'. Well, if I move the parameter definitions out of the node and up into another class like this: classes: software::application software::application_parameters environment: production parameters: then the software::application class CANNOT access the appvarN variables. What made initially think about this is that we are running 10 or more instances of a specific application on a server, and need to set up to 50 variables for each instance. For tidyness, I was hoping that each instance could be split into a separate file and the puppetmaster supported a file include function. Looks like it doesn't. This made me think of simply putting each instance into it's own class, but then of course they go out of scope. Puppet scoping issues strike again! How can I do this? Doug. -- 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.
Re: [Puppet Users] Re: puppet dashboard gui looks odd from apache2
On 08/21/2010 05:45 PM, Rustler wrote: > 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 > > Often, people are surprised to find major apache2 settings in weird places in Debian... I know I've definitely had some head scratchers that resembled this issue before because of it. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode L'ennui est contre-révolutionnaire -- 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.
Re: [Puppet Users] Debugging errors with external nodes
On Sat, Aug 21, 2010 at 3:59 PM, Douglas Garstang
wrote:
> My site.pp:
>
> node default {
> }
Your empty node classification is entirely consistent with the terse
agent output you pasted.
On Fri, Aug 20, 2010 at 5:06 PM, Douglas Garstang
wrote:
> Aug 21 00:04:09 app01 puppet-agent[5975]: Starting Puppet client version 2.6.0
> Aug 21 00:04:10 app01 puppet-agent[5975]: Finished catalog run in 0.01 seconds
-Jeff
--
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.
Re: [Puppet Users] Debugging errors with external nodes
My site.pp:
# /etc/puppet/manifests/site.pp
import "definitions/*.pp"
import "modules/*.pp"
import "nodes/pax/*.pp"
#import "nodes/den/*.pp"
# The filebucket option allows for file backups to the server
filebucket { main: server => 'puppet' }
# Set global defaults - including backing up all files to the main
filebucket and adds a global path
File { backup => main }
Exec { path => "/usr/bin:/usr/sbin/:/bin:/sbin" }
Package {
provider => yum,
require => $operatingsystem ? {
default => Class['yum::client']
}
}
node default {
}
Doug.
On Fri, Aug 20, 2010 at 7:17 PM, Jeff McCune wrote:
> On Aug 20, 2010, at 5:06 PM, Douglas Garstang wrote:
>>
>> When I create a default node, the client logs:
>>
>> Aug 21 00:04:09 app01 puppet-agent[5975]: Starting Puppet client version
>> 2.6.0
>> Aug 21 00:04:10 app01 puppet-agent[5975]: Finished catalog run in 0.01
>> seconds
>>
>> which doesn't really help.
>>
>> Doug.
>
> Please copy and paste your default node stanza.
>
> -Jeff
>
> --
> 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.
>
>
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627
--
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.
[Puppet Users] Re: puppet dashboard gui looks odd from apache2
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 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 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
>
> >>
> >> 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 /
> >>
> >> Options None
> >> AllowOverride None
> >> Order allow,deny
> >> allow from all
> >>
> >>
>
> >> 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
Re: [Puppet Users] Re: puppet dashboard gui looks odd from apache2
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 wrote:
>> I downloaded the puppet-dashboard.git
>> fromhttp://github.com/puppetlabs/puppet-dashboardand did 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
>>
>>
>> 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 /
>>
>> Options None
>> AllowOverride None
>> Order allow,deny
>> allow from all
>>
>>
>>
>> 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
>> puppet7565 1 0 15:02 ?00:00:05 master
>> puppet7888 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
>>
>> DocumentRoot /usr/share/puppet-dashboard/public/
>>
>> Options +Indexes
>> AllowOverride AuthConfig
>> Order allow,deny
>> allow from all
>>
>> ErrorLog /var/log/apache2/dashboard.example.com_error.log
>> LogLevel warn
>> CustomLog /var/log/apach
[Puppet Users] Re: puppet dashboard gui looks odd from apache2
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.
On Aug 20, 12:21 pm, Asif Iqbal wrote:
> I downloaded the puppet-dashboard.git
> fromhttp://github.com/puppetlabs/puppet-dashboardand did 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
>
>
> 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 /
>
> Options None
> AllowOverride None
> Order allow,deny
> allow from all
>
>
>
> 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
>
> DocumentRoot /usr/share/puppet-dashboard/public/
>
> Options +Indexes
> AllowOverride AuthConfig
> Order allow,deny
> allow from all
>
> ErrorLog /var/log/apache2/dashboard.example.com_error.log
> LogLevel warn
> CustomLog /var/log/apache2/dashboard.example.com_access.log combined
> ServerSignature On
>
>
> 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
