similar to: Puppet dashboard blank stylesheet

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

Hi, I am new to the job and forum. I installed puppet and puppetmaster and set up my first dependencies acording to a manual that we have here in our company. Everything works fine and I can set up new nodes with several modules to choose from. Unfortunatley the Dashboard <http://forge.puppetlabs.com/puppetlabs/dashboard>gives me errors instead of starting correctley. Here the

Dear All, I already deploy puppet-dashboard with passanger. i''m want to try puppet-dasboard work in like myserver.com/puppet-report using apache proxy reverse, but still getting work, its just show the index then when i try to click some link like nodes, its will be goto myserver.com/nodes, not to myserver.com/puppet-report/nodes its just work if i try to reverse to myserver.com.

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

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

Puppet Dashboard 1.2.23-rc3 is a maintenance release candidate of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23-rc3.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For

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

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

Hi everyone, I have my puppet master running happily under passenger. To save some ram I recently switched my dashboard over to run under passenger. After a few hickups (basically had to turn off RackBaseURI and turn on RailsAutoDetect) i got it running under https. I noticed today that reports hadn''t shown up since I switched to passenger and https so I switched it back to http and

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

Hi there, I installed puppet-dashboard, which works just fine, and trying to activate *inventory-services *but get this error on the agent: err: Could not retrieve catalog from remote server: Error 400 on SERVER: > Please install the mysql adapter: `gem install activerecord-mysql-adapter` > (Could not find RubyGem mysql (~> 2.8.1) > on the master, these are the packages I got

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

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

Puppet Dashboard 1.2.13-rc1 is a maintenance and bugfix release candidate of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13-rc1.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at:

Hi, I have noticed that when a typo is introduced or a module is plain broken, puppet will run using a cached catalog. This is logged as an error on the local client, however, it is not logged as an error on Puppet Dashboard. How can I change this behavior, so that using the cached catalog will result in a warning/error being displayed on Puppet Dashboard? Foreman does this. I''ve

Hello, we run Puppet Dashboard 1.2.23 in our sandbox and get an error deleting a node. - first time we press the delete button nothing happens - second time we press the delete button we get the following error; ActiveRecord::StatementInvalid in NodesController#destroy Mysql::Error: Lock wait timeout exceeded; try restarting transaction: DELETE FROM `node_group_memberships` WHERE `id` = 53

Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz Available in native package format in the Puppet Labs yum and apt repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Please report

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 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