similar to: One Dashboard for Multiple Masters

I did a fresh install on Ubuntu 12.04 with apt packages from puppet labs. I have agents talking to my puppetmaster. Puppetmaster is running apache/passenger connected to puppetdb and puppet-dashboard is setup to use puppetdb but it is not able to see any reports submitted to puppetdb. When an agent connects to master I see : Info: ''replace facts'' command for hostname

Hi All, Puppet-dashboard appears to be having some trouble. Under inventory, it says: "Could not retrieve facts from inventory service: Permission denied - certs/dashboard.private_key.pem" When I run: curl -k -H "Accept: yaml" https://puppet:8140/production/facts/host.domain I get the expected dump of facts. Versions: puppet-dashboard is 1.1.0 (using passenger) puppet-master

I have a puppet master install which uses puppetdb. I also have puppet dashboard installed with the inventory service running. I want multiple puppet masters using a single puppetDB server. Puppetdb is installed on separate vm. How can I get the dashboard inventory to use the puppetdb server to get the inventory records? Where do I configure the dashboard inventory so it uses puppetdb? I

Hello, I am having problems with Puppet since upgrading to 3.0.0. When I call an inventory search I get a Error 400. I have used dashboard + Perl Oct 4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET /production/facts_search/search?facts.lsbdistcodename.eq=lenny Oct 4 08:58:43 puppet01 puppet-master[7008]: header too long ii facter

Hello Everyone, I am new to puppet and want to set puppet dashboard. I don''t have a database for puppet dashboard, My question is that can i use PuppetDB as database for puppet dashboard ?? If yes then please tell me how to configure it. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and

Hi, I''ve just been configuring my new Puppet 3.1.1 / Dashboard setup with Passenger to use PuppetDB for the inventory service. I configured it via the puppetdb forge module, and it all seems to be configured correctly as far as the docs describe. When I look at a node in the dashboard, under the inventory section, I just see: Could not retrieve facts from inventory service: 404

Greetings, we are trying to setup puppetdb, nut our clients get the following error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: Failed to submit ''replace facts'' command for lxa7t.unix.lan to PuppetDB at puppetdb:8081: Connection refused - connect(2) Info: Retrieving

Hello, I am currently trying to get the puppetdb dashboard and the puppet dashboard working on the same system. Puppet dashboard is working great but after "successfully" installing puppetdb following puppet''s opensource instructions the puppetdb dashboard just doesn''t seem to exist (according to some sites I should be able to get to it by going to

I finally got around to installing PuppetDB and connecting it to my Master. I even set up Nginx to act as a reverse proxy, and I can make API calls like a pro. The dashboard is nice, but I''m anxious to get at least the same functionality that Puppet Dashboard gave me. Namely, a quick look at recent catalog changes or run failures (is this even possible, since PuppetDB

Hi! Which database would you recommend to use mysql or postgresql for puppet? Estimated number of nodes 30000, they send reports every 30 minutes. Thanks -- 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. To unsubscribe from this group, send email to

I just set up the latest dashboard release candidate in hopes of trying out the new inventory service. After modifying the puppet- dashboard config to use the inventory service and after changing my auth.conf I gave it a whirl but ran into some issues.. I initially tried using fact_terminus = yaml and was able to do some queries via curl. I''m currently using storeconfigs so setting up

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

PuppetDB, a component of the Puppet Data Library, is a centralized storage daemon for auto-generated data. This initial release of PuppetDB targets the storage of catalogs and facts: * It’s a drop-in, 100% compatible replacement for storeconfigs * It’s a drop-in, 100% compatible replacement for inventory service * It hooks into your Puppet infrastructure using Puppet’s pre-existing

on my puppet master server (v 2.7.17 , both server and client version) , the puppet agent can''t connect to itself. other clients connected to this puppet server are working fine. the hostname is puppet.domain.com [root@puppet /]# cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet

Hello, I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. Dashboard v1.2 Puppet puppet-server.noarch 2.7.19-1.el6 SERVER: -bash-4.1$ cat

Hi there, I installed puppet-dashboard, which works just fine, and trying to activate *inventory-services *but get this error on the agent: err: Could not retrieve catalog from remote server: Error 400 on SERVER: > Please install the mysql adapter: `gem install activerecord-mysql-adapter` > (Could not find RubyGem mysql (~> 2.8.1) > on the master, these are the packages I got

I just upgraded the second half of a two node puppetmaster cluster and now I am having issues with puppet-dashboard report processing. If I have workers running on both servers, they try to process each others reports, but since the report data file is not there, it fails. I would have assumed this data was local, not in the database. Does anyone else have this issue, or have a suggestion

I have a small environment with a single puppetmaster and puppetdb on the same node that I get sporadic "Failed to submit ''replace facts'' command" errors from nodes. It isn''t consistent about which nodes are causing the error and I can''t find anything else going on at the same time on either the master or the agent that these errors happen. Here

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 been using PuppetDB as an ENC for a while, but I haven''t really utilized it for stored configs or anything. I was mostly interested in replacing Dashboard''s reporting capabilities, but PuppetDB doesn''t yet do anything (that I can see) with reports. So I''m currently looking into setting up a separate Foreman server. I saw the script mentioned