similar to: puppet dashboard stopped updating

Hello, I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. Dashboard v1.2 Puppet puppet-server.noarch 2.7.19-1.el6 SERVER: -bash-4.1$ cat

I just upgraded the second half of a two node puppetmaster cluster and now I am having issues with puppet-dashboard report processing. If I have workers running on both servers, they try to process each others reports, but since the report data file is not there, it fails. I would have assumed this data was local, not in the database. Does anyone else have this issue, or have a suggestion

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

I''m trying to connect multiple masters to one dashboard and I''m having trouble with Facter. I started out initially with one master connected to the dashboard and that one works perfectly fine. Then I added a second master by setting the reporturl to point to the dashboard. The new nodes appeared and it shows the run results without any problems. The issue I''m

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

Hi all, I hope somebody can help me with something. We have a rather large number of netbooted nodes that we are running "puppet apply" via a script and a cron job every 30 minutes I was wondering if there is a way to configure puppet apply, to also send any reports to our dashboard server that is being used for our normal puppet clients and what would be the way to go about doing

I did a fresh install on Ubuntu 12.04 with apt packages from puppet labs. I have agents talking to my puppetmaster. Puppetmaster is running apache/passenger connected to puppetdb and puppet-dashboard is setup to use puppetdb but it is not able to see any reports submitted to puppetdb. When an agent connects to master I see : Info: ''replace facts'' command for hostname

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

the puppetmaster conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl reports = store, http, foreman reporturl = http://localhost:3000/reports/upload [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig the puppet client conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet

Hello, I have another quick one about puppet dashboard. We are using the Debian one for Squeeze (1.0.4) and as the database has significantly grown, if/when we click on a list of unresponsive nodes to check them, the web interface sits there doing nothing then the puppetmaster process starts timing out for all nodes compiling their catalogs. Has anyone got a workaround for this? Does it involve

Hello, I''m trying to get puppet-dashboard installed on a CentOS 6.3 machine running puppet v3.0.1. I''m following the puppet-dashboard documentation here: http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html In the documentation page linked above, it says: Puppet uses SSL certificates to control who can make requests to the puppet > master, so Dashboard has

Hello Everyone, I am new to puppet and want to set puppet dashboard. I don''t have a database for puppet dashboard, My question is that can i use PuppetDB as database for puppet dashboard ?? If yes then please tell me how to configure it. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and

Using 1.0.4 release on Solaris 10 with Ruby 1.8.7. Starting the server in production mode works fine until I request a page from the web browser then I get the following errors on the console. I''m running as user puppet (have also tried as user root but same output). All files are owned by user/group puppet/puppet. I have dropped and recreated the database multiple times just to see if

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

This is a maintenance release of Puppet Dashboard. This release resolves issues #7405, #9101, #8878, and #8803. 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

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

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

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

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

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