similar to: is it possible to save dashboard inventory searches

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 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

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

I''m using Dashboard 1.2.10 on an Ubuntu 10.04 LTS system, and Puppet 2.7.19 When I do an inventory search, I get a blank screen. In the logs, I found the following: Processing NodesController#search (for X.X.X.X at 2012-10-05 08:44:57) [GET] Parameters: {"action"=>"search", "controller"=>"nodes",

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

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

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

I can delete a node in dashboard fine, but when I do a search with the Inventory Search the node shows up again and also then shows up under "Unreported". Any way to get rid of all references to the node? Thanks, -- Romeo -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

I''m having all sorts of trouble getting our new puppet-dashboard install to connect/get the facts/inventory from the puppet master. These are separate boxes, and I''m getting (testing): root@puppetdash puppet-dashboard]# curl -k -H "Accept: yaml" https://puppet:8140/production/facts/hero0304.rc.fas.harvard.edu Forbidden request:

I''m trying to connect multiple masters to one dashboard and I''m having trouble with Facter. I started out initially with one master connected to the dashboard and that one works perfectly fine. Then I added a second master by setting the reporturl to point to the dashboard. The new nodes appeared and it shows the run results without any problems. The issue I''m

I have a dashboard server sitting in my development lan and am able to pull inventory and file bucket information from my development Puppet Master server to the dashboard. I would like to be able to pull the facter inventory and filebucket from my Production Puppet Master server into the development dashboard server, that way I have one view for all my systems. There are firewall rules that

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, puppet-dashboard has been great for us, and I appreciate all the hard work from all the developers. I can''t however seem to enable facts or inventory browsing. I have generated, signed and retrieved the certs as per the README. Not sure what else I need to do to get them to display (or where it would be)? I also could not find any relevant info in settings.yaml. Any help is

Sorry for being off topic. am trying the following and yaml fails to construct the object: The inventory document, from Puppet dashboard inventory service, looks like: --- !ruby/object:Puppet::Node::Facts name: pirates.uis.example.com values: productname: VMware Virtual Platform kernelmajversion: "2.6" My code: class PuppetFacts(yaml.YAMLObject): yaml_tag =

This a feature release candidate (number 3) of Puppet Dashboard. If you''re wondering what happened to rc2, it was internal only. Our CI system found a few issues before we released it to the public. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download

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

I''m working on a system for auto-resigning certificates for our clients and Iv''e basically got it working .. but I notice that Puppet uses an inventory file and a serial # file that seem to be differently formatted than the openssl toolkit uses? The serial number file that puppet generates has a 4 digit number starting with 0000... but openssl tracks its serial numbers in a hex

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

Dear Fusion Inventory fellows, I've been thinking about working on adding power devices knowledge to inventory systems for years. Following the last Ubuntu Developer Summit, I know have an "excuse" to do so: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management My below proposition is related to the above blueprint. So please keep in mind that the

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