similar to: Sourcing reports from different locations.

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

I downloaded the puppet-dashboard.git from http://github.com/puppetlabs/puppet-dashboard and did the installation in my ubuntu lucid puppet server following the steps in "Installation". Now I can run it fine using the WEBrick like this root@sys-ubuntu { ~/git/puppet-dashboard }$ ./script/server -e production => Booting WEBrick => Rails 2.3.5 application starting on

Hi I installed puppet on centos for the first time yesterday. the default installation via YUM didnt install any modules i am using apache and mysql for the webserver and database. my question is there no way to install the modules if i am behind a proxy? [root@puppet ~]# puppet --version 3.3.2 [root@puppet conf.d]# cat /etc/*release* CentOS release 6.4 (Final) CentOS release 6.4 (Final) CentOS

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

Hello, I use Centos 5x with rpmforge for install puppet. It''s update''s itself. Today system update puppet to 2.7.x version. Puppen agent updates ok. But passenger start old version(2.6.x). Then I start puppetmaster init script (it''s start WEBrick) started new version. Apache vhost: RackAutoDetect On DocumentRoot

Hi, Iam a newbie to puppet, iam trying to set my local puppet master and dashboard running on same server. Iam also using https to connect to dashboard. I can launch the dashboard on https://IP fine but i see only one report on the webpage, When i tried to import all the previous reports iam getting this error # cd /usr/share/puppet-dashboard/ ]# sudo -u puppet-dashboard rake

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

Hello, I did make a stupid fault: not commiting changes to version control :-( After the installation of puppet-dashboard, I added a recipe to add report = true to puppet config files on clients. Now all Puppet clients don''t update because of an error... What can be the various reasons for an ''400'' error?? I guess it has something to do with rights. Jun 28 09:52:36 pm

Hello Puppet Users ! We encounter a problem with the dashboard on this URI : /reports/changed The /reports works fine with ~130000 reports (up to 3 months and auto-cleaning with rake reports:prune job) I make a reports:prune:orphaned, juste in case, but without any success. The most recent change on the server was the puppetmaster upgrade from 3.0.2 to 3.1.0. Here is the dashboard error log

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

I''ve installed Puppet and am installing Dashboard on CentOS 6. I''m running into an ''undefined method'' when installing the dashboard. To install Puppet Open Source, I ran: > rpm -ivh

I''m playing around with foreman for the moment. I can''t seem to figure out how to make the dashboard look like in this screenshot http://theforeman.org/wiki/foreman/Screenshots#Dashboard In order for those statistics to work what should be done? I have activated the rrdgraph reports in puppetd, uncommented the line ":rrd_report_url: report/" in config/settings.yaml

Howdy, I''ve been getting this issue for about a month in dashboard. All our nodes poll on a cronjob between 00:00 and 01:00 daily, but one node has been getting this as a failed task for a while, with the yaml files building up on the server. Outside of this one cronjob, other puppet runs on the same node are running just fine. The backtrace on dashboard is: Importing report

Hey, Just wondering if anyone else has noticed this. I''m using thin+puppetmasterd+nginx. If i add a host, sign it''s key, run puppetd successfully on it all is good, as expected. If i then revoke/clean the key on the master server, leave the box running, startup another host set the hostname to be the same as the old, generate new keys/have them signed. The original box is still

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

Hi all, I''ve just installed puppet in my ubuntu gutsy 7.10 linux using gem: # sudo gem install puppet Then, I made a basic site.pp manifest and following the InstallationGuide I ran: $ sudo puppetmasterd --mkusers Could not configure for running; got 1 failure(s) What error? I managed to get an error message on /var/log/daemon.log Jan 30 16:22:13 acero puppetmasterd[13800]:

I updated some of my gems, and I think it may be the reason I am getting the following error when the agents try to retrieve a catalog. err: Could not retrieve catalog from remote server: Error 400 on SERVER: The single-table inheritance mechanism failed to locate the subclass: ''Host::Managed''. This error is raised because the column ''type'' is reserved for

I left my new puppetmasterd running last night. came in with a stack trace below. A number of questions: 1. Where did /Settings come from? 2. Is there a way to dump the contents of the catalog to understand? 3. I want to change the perms for all that stuff 4. puppetd is not running on this host, does puppetmasterd act like a puppetd? notice: Compiled catalog for inst01.corp.631h.metaweb.com

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 all, I''ve tried to run ''puppetrun'', but there seems something unconfigured regarding the certificates. The reverse way (puppetd pulls the config from puppetmasterd) works fine. The namespaceauth.conf on the client (where puppetd runs) is configured as follows: [puppetrunner] allow *.abc.net (also tried the calling host: puppet1.abc.net) But when I call