Hi folks, Thanks for the dashboard questions. I'm glad people are using dashboard and reporting these issues.
The dashboard installation instructions currently say to add the puppet_dashboard.rb's directory to your Puppet libdir. This fails due to http://projects.puppetlabs.com/issues/3094. This makes me sad as well so I'm working on resolving that issue. In the meantime, I'm updating the installation instructions with a work around, which is: symlink dashboard's puppet_dashboard.rb into your $libdir, typically to /var/lib/puppet/reports. The ultimate solution is to add an http reports processor to puppet-core that can be configured to point to dashboard (or any other http endpoint that accepts reports). No more modifying libdir or creating symlinks. Just a couple puppet settings and you're done. Yay. I've got code for this that is working its way into Puppet as we speak. Dashboard's (lack of) timezone support is an important issue. I don't have a fix right now but I'm working on it. I'll let you guys know when that's resolved. Rein Henrichs http://puppetlabs.com On Mon, Jun 21, 2010 at 2:11 AM, christian <[email protected]> wrote: > After I put puppet_dashboard.rb into site_ruby/1.8/puppet/reports as > Don told now the aggregations seems to work just fine. > But I guess it's supposed to work if you put that file in the correct > directory in your puppet-homedir...so there still seems to be some > unresolved problems. > > Btw, where does the dashboard get its time informaiton from? All our > server run with CEST but the dashboard shows all times in WAT (CEST -2 > hours). The time in the report-files themselves is 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]<puppet-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- 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.
