similar to: Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48

Hello, This is the way we currently define nodes using modules/classes. Unsure if this is the best method but as dashboard does not do parameterized class variables seems the right way. We apparent zen_ to everything thats making up our servers. I am having problems with the MySQL module as I need to include mysql:: several times to get the features -

This is a maintenance release of Puppet Dashboard. This release resolves issues #10198, #10270, and #10543. More details below. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

I have just set up my puppet dashboard to be used as a ENC. This is for the time being the easiest way to get support guys to add nodes to classes. I have to use global parameters in my modules if I would like to declare parameters using dashboard as the ENC. So I have a module which does this: class resolver ($domain_name=$::domainname, $search_path=$::searchpath,

Hi, My puppetmaster is running through apache, and now I am setting up dashboard to be run by apache too. I followed docs in http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#starting-and-managing-delayed-job-workers, but after I restarted httpd, I see a apache welcome page. I set documentroot to be: DocumentRoot /usr/share/puppet-dashboard/public/

I downloaded the puppet-dashboard.git from http://github.com/puppetlabs/puppet-dashboard and 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 root@sys-ubuntu { ~/git/puppet-dashboard }$ ./script/server -e production => Booting WEBrick => Rails 2.3.5 application starting on

Hello all Puppet, puppetmaster, ruby, etc installed from standard Ubuntu 11.10 x86_64 APT repos Dashboard 1.26 from .deb pulled from http://apt.puppetlabs.com/pool/oneiric/main/p/puppet-dashboard/ Apache config pulled from /usr/share/puppet-dashboard/ext/passenger/dashboard-vhost.conf My simple test with webbrick worked a treat. So I installed Apache and passenger mod (from Ubuntu APT

Hello, I installed puppet-server, passenger and dashboard. I have tested every step in between to make sure all is running well and not errors are carrying forward. Dashboard worked well with my test in WEBrick. After configure the dashboard with passenger I got the message” The environment must be purely alphanumeric, not ''''” instead of the dashboard. I verified the

I am using Ubuntu 10.04 and ruby-enterprise (not ubuntu ruby) and installed puppet via gem. How can I install puppet-dashboard if I don''t see a gem available and if I use the ubuntu package, i get the whole slop of ruby packages sucked in (which i am trying to avoid)? # dpkg -i puppet-dashboard_1.1.0-1_all.deb Selecting previously deselected package puppet-dashboard. (Reading database

Am using dashboard 1.1.1 with the use_file_bucket_diffs option. When clicking on the links within a report it will show the old md5 file (on the left) but not the new md5 file (on the right) like; content content changed ''{md5}26a3112822d01f2ce6b3f052bf2809de'' to ''{md5}dd97364ab0559344d73231f517951595'' 26a3112822d01f2ce6b3f052bf2809de ==> is displayed

Hi All, Im trying to install but with no luck. Any idea what I did wrong ? ** mkdir -p /var/log/pe-console-auth ** touch /var/log/pe-console-auth/cas.log ** touch /var/log/pe-console-auth/auth.log ** chmod 770 /var/log/pe-console-auth ** chmod 660 /var/log/pe-console-auth/auth.log ** touch /var/log/pe-console-auth/cas_client.log ** chmod 660 /var/log/pe-console-auth/cas_client.log ** chown -R

I have setup passenger w/ apache, but my dashboard is not connecting properly. I am getting the following errors em::Specification#installation_path called from /etc/puppet/puppet-dashboard/vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:93. NOTE: Gem::Specification#installation_path is deprecated, use base_dir. It will be removed on or after 2011-10-01.

I get this error can''t activate rack (~> 1.0.1), already activated rack-1.2.2 It appears that puppet-dashboard uses rack 1.0.1 but passenger 3.0.7 needs to use rack1.2.2 Is there a way around this or make dashboard use rack 1.2.2? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

I''m currently running a dashboard as a separate process and have a proxy in apache with authentication to access as http://puppet.ourhost.com/dashboard/ I have to start the dashboard with "-P /dashboard" option to make it work. I''m wondering how to achieve this with passenger. The config I found in ext/passanger seems to run the dashboard under the root of the virtual

Hello, I am having problems with Puppet since upgrading to 3.0.0. When I call an inventory search I get a Error 400. I have used dashboard + Perl Oct 4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET /production/facts_search/search?facts.lsbdistcodename.eq=lenny Oct 4 08:58:43 puppet01 puppet-master[7008]: header too long ii facter

Hi All, Puppet-dashboard appears to be having some trouble. Under inventory, it says: "Could not retrieve facts from inventory service: Permission denied - certs/dashboard.private_key.pem" When I run: curl -k -H "Accept: yaml" https://puppet:8140/production/facts/host.domain I get the expected dump of facts. Versions: puppet-dashboard is 1.1.0 (using passenger) puppet-master

Hello Puppet Users ! We encounter a problem with the dashboard on this URI : /reports/changed The /reports works fine with ~130000 reports (up to 3 months and auto-cleaning with rake reports:prune job) I make a reports:prune:orphaned, juste in case, but without any success. The most recent change on the server was the puppetmaster upgrade from 3.0.2 to 3.1.0. Here is the dashboard error log

Hello, I would like to know if it is possible to automatically import the puppet classes to the dashboard in order to manage them from the gui. I didn''t find exact instructions to make the puppet clients report directly to the dashboard instead of importing the reports every time through the command rake RAILS_ENV=production reports:import . Does anyone has the exact instructions? Thanks

I''m having trouble getting puppet dashboard (1.2.21) to run on apache. i installed puppetmaster-passenger and puppet-dashboard package. It didn''t create user puppet-dashboard automatically as stated in the installation guide, so i created one manually and chowned all files under /puppet-dashboard. when testing with webrick everything works fine (as root). when i try with

I''m playing around with foreman for the moment. I can''t seem to figure out how to make the dashboard look like in this screenshot http://theforeman.org/wiki/foreman/Screenshots#Dashboard In order for those statistics to work what should be done? I have activated the rrdgraph reports in puppetd, uncommented the line ":rrd_report_url: report/" in config/settings.yaml

Greetings, I have a tested, working setup of Puppet and Webrick. I can add nodes, classes, etc. Then I switched to Puppet/Passenger and get the error below. Puppet, Apache and Passenger are all up. I have installed using *YUM *repos and *GEMs*. So, I have the most updated packages they have. Puppet version: 2.7.19 Ruby version: 1.8.7 (2011-06-30 patchlevel 352 i386) Apache: 2.2.15 The error