similar to: puppetdb query not working as expected

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

Hi all, I''m setting up puppetdb to for storing facts et cetera. I installed puppetdb-1.3.0-1.el6.noarch.rpm on my puppetdb.local host (which is puppetized). This seems to work, service starts :). When I edit the settings on my puppetmaster (puppet.local), something goes wrong. I am following the guide [1]. I put the settings (storeconfigs = true, storeconfigs_backend=puppetdb) on my

Hi, When i m using Postgresql database with puppetdb in puppet 3.0.2, following error is coming. err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ''replace facts'' command for abcd.example.com to PuppetDB at puppet-DB.example.com:8081: Connection refused - connect(2) Can anyone have any solution regarding this? -- You received this

Greetings: I''m having trouble connecting to PuppetDB. When I execute *sudo puppet agent --test* on a client node, I receive the following: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for web1.mydomain.tld: Failed to find facts from PuppetDB at db1.mydomain.tld:8081: Connection refused -

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

Hello, I''m currently trying to deploy puppetdb to my environment but I''m having difficulties and am unsure on how to proceed. I have 1300+ nodes checking in at 15 minute intervals (3.7 million resources in the population). The load is spread across 6 puppet masters. I requisitioned what I thought would be a powerful enough machine for the puppetdb/postgres server. A machine

I''m trying to query puppetdb for a list of hosts maching a certain regex (on hostname) and only returns 2 facts (ipaddress and hostname) I''m trying to follow: http://docs.puppetlabs.com/puppetdb/latest/api/query/tutorial.html and I''m not even quite sure, wether or not, I should use a facts or a nodes, or a resources query ? I get some of the queries to return just

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",

Hi all, I''ve been looking at a potential problem, as documented here: http://projects.puppetlabs.com/issues/19241 To do with a leak within the KahaDB persistence layer of ActiveMQ. Specifically, there are reports of the db.data file growing unbounded: https://issues.apache.org/jira/browse/AMQ-3956 I''m hoping to find out information from other PuppetDB users to see if this is

Hi all, For months now I''ve been using Puppet with PuppetDB backend to manage my Nagios configs. We now have 1200+ services being checked and including servicedependency, host, hostdependency, command and other Nagios resources being managed, that''s about 3000 resources in total. Unfortunately this means the monitoring server takes about 8 minutes to perform a Puppet run.

Hi, I''m using PuppetDB with builtin backend, haven''t switched yet to postgresql, and I''m starting to see decrease in performance of my agent runs. I use PuppetDB solely because of exported resources support. How soon should I think about moving to PostgreSQL? How many clients does my master need to serve, so that PuppetDB in it''s default installation,

Is the module puppetdb from the forge still correct ? Every time I try to install puppetdb from the puppet module ("puppet module install puppetlabs/puppetdb"), i got a warning : *Warning: cprice404-inifile is deprecated; please update to puppetlabs-inifile* How may i install the puppetlabs-inifile instead of cprice404 ?? -- You received this message because you are subscribed to

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

Hi All, Has anyone figured out a nice way to restrict user access to puppetdb''s http web interface? Such as a .htaccess method or something similar? I would prefer something along those lines instead of setting up firewall rules. -Zane -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and

I''m working on configuring a master in a lab environment, using Puppet Open Source. My master is running RHEL 6. I want to use modules to manage the master itself as much as possible, so I can use puppet to bootstrap itself as I go forward and move into production. Using puppetlabs/puppetdb to configure puppetdb, I''ve overcome most of my issues but I have two questions. 1)

Hi All; I am using the PuppetDD 1.3 docs. I am attempting to run the following query: curl -H ''Accept: application/json'' -X GET http://localhost:8080/v2/resources--data-urlencode query@db_look Contents of db_look: ["=", "certname", "puppet-satellite"] However, I get no results with this... I also do not get an errors I do see this in the log

Hello, I would like to ask what to pay attention to, when someone wants to set up multiple PuppetDB instances (and point them to the same DB), and put them behind a proxy/load balancer, as mentioned in the documentation<http://docs.puppetlabs.com/puppetdb/1/scaling_recommendations.html#bottleneck-single-point-of-failure> . Can this cause some concurrency issues with the message queues?

Hi, I''m trying to use Puppet ability to export and collect resources using PuppetDB. My PuppetDB and Puppet Master are running on the same host and I used the PuppetDB puppet module to install PuppetDB and configure the Puppet master. Each time the puppet agent runs on a client, the facts and the catalog are being pushed in PuppetDB and I can query the PuppetDB server to get

Dear all, We have a few reasons to have various PuppetDBs (and Masters, one per cluster) in our datacenter and, eventually, there may be a need to share *only* a few exported resources between clusters, like a few ssh-keys or nagios tests. Is there a mechanism to pull and push some exported resources from one PuppetDB to another? I guess this could be done with the API, but has anybody tried it,

Hi Guys, I am new to the world of puppet. I have successfully configured puppet on centos 6 and am now trying to install puppetb on the same host. After the configuration when I try to run puppetd --test command on the client I get : [root@puppettest ~]# puppetd --test notice: Ignoring --listen on onetime run err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to