I'm already running with pluginsync=true, so I just stuck puppet_dashboard.rb into one of my modules:

> find . -name puppet_dashboard.rb -print
./modules/puppet/lib/puppet/reports/puppet_dashboard.rb

And pluginsync does its magic. I don't touch libpath or anything like that. I'm not 100% clear if I need the dashboard script on the nodes (I don't think so...), puppetmasters, or what, but this worked for me when I was fighting through the same problem so I said why question it; then the deployment of the file is in puppet so if I build a new puppetmaster it gets pushed out like it should, automagically.

I do puppet my masters though. If you didn't, this trick probably won't work for you. You can always puppet them with --noop -- you'll still do pluginsync in non--noop mode and only actually apply --noop to the puppet configuration itself.


On 06/16/2010 07: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 <christ...@cust.in
<mailto:christ...@cust.in>> 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 puppet-users@googlegroups.com
    <mailto:puppet-users@googlegroups.com>.
    To unsubscribe from this group, send email to
    puppet-users+unsubscr...@googlegroups.com
    <mailto:puppet-users%2bunsubscr...@googlegroups.com>.
    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 puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
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 puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to