similar to: Yaml reports not uploading to puppet dashboard

Hello! I''m trying to install puppet dashboard according to the instructions in the documentation : http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html I am installing it from the .deb package, however after installation I cannot find the "settings.yml" file. Also, when trying to "prepare schema" by running rake RAILS_ENV=production db:migrate it

no matter what I try I keep getting this error: rake RAILS_ENV=production db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate rake aborted! Access denied for user ''dashboard''@''localhost'' to database ''production'' I have setup the dashboard user in mysql DB, tested

Hello I have just installed puppet dashboard from git. everything seems to load ok except it seems as though background tasks are not being run. According to the code README: running: # env CPUS=4 RAILS_ENV=production /.../script/delayed_job -p dashboard -n $CPUS -m start will start the worker. however it seems as though it is not running (or if it is how can I check?) and the back ground

Hi I''m trying to configure Puppet-dashboard after installing Puppet from the open source package. But there was no issues when using the Enterprise package. Do you have any solutions for the below error? I''m trying to configure Puppet-dashboard. # rake RAILS_ENV=production db:migrate NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after

I''ve installed Puppet and am installing Dashboard on CentOS 6. I''m running into an ''undefined method'' when installing the dashboard. To install Puppet Open Source, I ran: > rpm -ivh

Hello, I successfully installed puppet on redhat 6. Nodes can connect to master and run catalog. I installed dashboard and was hoping to see the reports uploaded in dashboard... I have no problem browsing to the dashboard but when an agent sends a report to the master, I always get the same error in the master''s log: *Unable to submit report to http://127.0.0.1:3000/reports/upload

Hello Group, I have a problem with pending tasks in puppet-dashboard after I set the MySQL parameter autocommit = 0 and sql_mode = TRADITIONAL. Does the dashboard need autocommit to be enabled? Workers are running: env RAILS_ENV=production script/delayed_job status delayed_job: running [pid 4995] delayed_job: running [pid 5019] Regards Kai -- You received this message because you

I have been working on this issue for almost 5 days and can not get past this error. Puppet Dashboard is installed via RPM from puppetlabs. I have tried versions 1.2.12, 1.2.9 and am currently on 1.2.1. Regardless of the version, I get the same exact error every time I run rake RAILS_ENV=production db:migrate. (in /usr/share/puppet-dashboard) rake aborted! no such file to load --

Puppet Dashboard 1.2.15 is a bugfix release of the 1.2 series of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.15.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com Please report feedback via the Puppet Labs Redmine site, using an affected

This release of Puppet Dashboard addresses CVE-2013-0277 and CVE-2013-0269. These are vulnerabilities that affect Ruby on Rails, specifically around YAML serialization and JSON handling. They expose vulnerable systems to SQL Injection, Denial of Service Attacks, and arbitrary YAML deserialization. Additionally, CVE-2013-0276 and CVE-2013-0263 affect vendored components of Puppet Dashboard, but by

Hi puppet users, We''ve got a puppet (0.24.8) implementation with two environments, called production and testing. We''ve also got a Puppet Dashboard (1.0) instance up and running, which is receiving and displaying reports from hosts in both of the environments. We would like to start using the dashboard as an external node classification tool, so I''ve taken the example

*Hello folks** **I have trying to install puppet dashboard on our ubuntu 10.04 setup but am currently stuck on the following problem.**after the installation and the db sync the application refuses import any reports. In the background job notifier i find error messages like this one below.** **Does anyone know how to proceed from here?** **bram** * *Importing report report-1540-1.yaml* at

followed the instruction for installing dashboard, and created user mysql -pmy_password -e "CREATE DATABASE dashboard CHARACTER SET utf8;CREATE USER ''dashboard''@''localhost'' IDENTIFIED BY ''my_password''; GRANT ALL PRIVILEGES ON dashboard.* TO ''dashboard''@''localhost'';" however, I keep getting

Hi guys, I have a strange situation. I''ve got 1 dashboard MySQL DB accessed from 3 different dashboard hosts. Strangely enough, 2 of them show the right node statuses, and the third one just shows all nodes as unresponsive. As far as I know, the status comes from the "nodes" table in the DB, so how can this happen? Is there some cache I need to clear? Is there another

Hi, I have 51 clients in puppet-dashboard – and when I tell it to delete a node – it simply hangs forever. If I try to just open / on the puppet-dashboard website – I get a proxy timeout (I have apache in front). I end up having to kill webrick and start it again – with the node NOT being deleted :( I have commented on an issue here - which seems to be about the same:

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

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

I''ve setup a new puppet master and I''m having trouble with running dashboard rake commands. Any advise on why I may be getting this error would be appreciated! Thanks, Thomas sh-4.1# pwd /usr/share/puppet-dashboard sh-4.1# sudo -u puppet-dashboard rake RAILS_ENV=production jobs:work /usr/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:247:in `to_specs'': Could not

Hi Puppet Users group, I have followed the guide to the puppet-dashboard DB "Preparing Schema" part, once I run " rake RAILS_ENV=production db:migrate --trace", it shows the following errors: (in /usr/share/puppet-dashboard) > rake aborted! > Mysql::Error: CREATE command denied to user ''dashboard''@''localhost'' for > table