search for: puppet_dashboard

Hi all. I''m unable to integrate puppet dashboard as I keep getting the following error: No report named ''puppet_dashboard'' Relevant configuration (names changed to protect the innocent).. ==== /etc/puppet/puppet.conf [puppetd] libdir=$vardir/lib libdir=/var/www/puppet-dashboard/lib/puppet [puppetmasterd] reports = puppet_dashboard storeconfigs = true dbadapter = mys...

..., I''m exploring puppet-dashboard right now and I want to get the live aggregation running. But somehow I''m already failing at the puppet.conf entries ;) The Dashboard readme says: ### Live report aggregation To enable report aggregation in Puppet Dashboard, the file `lib/puppet/ puppet_dashboard.rb` must be available in Puppet''s lib path. The easiest way to do this is to add `RAILS_ROOT/lib/puppet` to `$libdir` in your `puppet.conf`, where `RAILS_ROOT` is the directory containing this README. Then ensure that your puppetmasterd runs with the option `--reports puppet_dashboard`. S...

I am currently using puppet in testing, on a centos 6.4 machine running puppet-master, puppet-agent, dashboard, and foreman. The manifest for the puppet matser machine in empty, like so: node ''puppet'' { } However, when the pupper agent runs, it always deleted the dashboard report module, which I keep restoring: from the log: Debug:

...nning } err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target "Service[]" versus this: $service_name = "httpd" service { "$servicename": ensure => running } err: /Stage[main]/Puppet_dashboard::Service/Service[undef]/ensure: change from stopped to running failed: Could not start Service[undef]: Execution of ''/sbin/service undef start'' returned 1: at /etc/puppet/ environments/testing/modules/httpd/manifests/service.pp:26 -- You received this message because you are su...

Hi i have the running i both sides, client and server sides the puppet 0.25.4 Get this error on server side: puppetmasterd[5363]: Report puppet_dashboard failed: wrong Content-Length format And receive this error on my client side: warning: Value of ''preferred_serialization_format'' (pson) is invalid for report, user default (b64_zlib_yaml) I am getting any reports on my /var/lib/puppet/reports. -- Marley Bacelar Project Fedora...

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

...e master. No change. No helpful information in the master log. I''m running the master with: /usr/sbin/puppetmasterd --no-daemonize --debug --logdest console --verbose --trace and some relevant puppet.conf portions on the master: storeconfigs = true thin_storeconfigs = true reports = log,puppet_dashboard reportfrom = root syslogfacility = user # Remote Inventory Service facts_terminus = rest inventory_server = tv-puppetma1.techtarget.com # fqdn of master inventory_port = 8140 The exact behavior I''m seeing is that when I run puppetd on the node, all works well up to seeing "debug: c...

An error I managed to hit today, trying to migrate puppet dashboard from 1.2.2 to 1.2.4 (after upgrading the master to puppet 2.7.9 seemed to prevent the dashboard from importing new reports). I''m trying to re-run it now, but as you might guess, the DB is pretty huge and the process takes a while to execute. Executed from the puppet-dashboard directory: sudo rake db:migrate

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.