Well I tested now to put puppet_dashboard.rb in /etc/puppet/modules/ custom/lib/puppet/reports as well as in /etc/puppet/modules/custom/lib/ puppet/provider/reports (it seems to me as if the correct structure here is pretty important) but still there is no auto-aggregation after any puppetrun nor any new helpful error message. The Plugin is synced with the clients (although I think its not necessary) and I still get the "no report named puppet_dashboard" warning.
But after I put the file directly into site_ruby/1.8/puppet/reports, like Don told, the auto-aggregation seems to work just fine now :) But of course this isn't really a nice solution. Btw, how is the time created that the dashboard for the reports shows? All our servers run on CEST but the dashboard seems to use the WAT timezone (CEST -2 hours). The timestamps that appear in the report files are all correct. christian On 20 Jun., 18:05, Don Jackson <[email protected]> wrote: > I am having all the problems that the following two threads reported. > > Like tomholl reported, I was finally able to get reporting to work by copying > the puppet_dashboard.rb file into the directory site_ruby/1.8/puppet/reports > > And when I had previously attempted to specify libdir to be a colon separated > path, puppetmasterd died/crashed. > > I am running puppet version 25.5 on OpenBSD (4.6) (Yes, I built new packages > from the tip of OpenBSD port tree), and dashboard 1.0.0 > > I would definitely appreciate any advice as to what I am doing wrong…. > > Don > > On Dec 17, 2009, at 10:04 AM, tomholl wrote: > > > > > am still having some trouble getting this to work as per the > > README.markdown instructions. > > > I was able to get it working by copying the puppet_dashboard.rb into / > > usr/lib/ruby/site_ruby/1.8/puppet/reports > > > Setting the $libdir in puppet.conf seemed to work but I still kept > > getting "No report named 'puppet_dashboard' " errors after each > > successful catalog compile. > > > The reason I think the $libdir was getting set is that the output of > > 'puppetd --configprint libdir' and 'puppetmasterd --configprint > > libdir' is /opt/puppetdashboard/lib/puppet (where I put my test > > install) > > > Since I kept getting errors about not finding the report I ran > > 'puppetmasterd --configprint reports' and got an output of store. > > Once I found where the store file was and copied the > > puppet_dashboard.rb file into that location (/usr/lib/ruby/site_ruby/ > > 1.8/puppet/reports) everything worked. > > > So what am I missing? Why did I have to copy the report file over to / > > usr/lib/ruby/site_ruby/1.8/puppet/reports if my $libdir was set > > properly? > > On Jun 16, 2010, at 5:02 AM, Jon Choate wrote: > > > I am seeing similar issues. In my puppet.conf I set > > > reports = store, puppet_dashboard > > and libpath = /var/puppet/lib:$RAILS_ROOT/lib/puppet > > > (RAILS_ROOT being /opt/puppet-dashboard where I installed puppet dashboard) > > Using a combined path like this does not seem to work for libpath. It views > > the entire string as one path. Is this by design? > > > I then set libpath to just $RAILS_ROOT/lib/puppet > > > With these settings I still get the message that it can't find the report > > named 'puppet_dashboard'. I even tried linking the .rb files for the > > puppet_dashboard report to /var/puppet/lib and use the default libpath but > > that did not seem to help either. > > > Any idea? > > > On Mon, May 31, 2010 at 9:35 AM, christian <[email protected]> wrote: > > Hey, > > > 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`. > > > So how do I "add" that line? > > > If I try something like $libdir = $vardir/lib;/usr/local/puppet- > > dashboard/lib/puppet or : or , or "blank" instead of ; I always get > > this error message from the clients: > > "Could not prepare for execution: Got 1 failure(s) while initializing: > > change from absent to directory failed: Cannot create /var/lib/puppet/ > > lib,/usr/local/puppet-dashboard/lib/puppet; parent directory /var/lib/ > > puppet/lib,/usr/local/puppet-dashboard/lib does not exist" > > > I'm using Pupet 0.25.4 on Open Suse 11.1 and Dashboard 1.0.0 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
