similar to: Help with scaling puppetdb/postgres

I have multiple puppetdb severs pointed at the same database. Would setting gc-interval to 0 disable it on the extra puppetdb nodes? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4DEyx0IXbLsJ. To post to this group, send email to

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

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

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

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

I''ve configured puppet to use storedconfigs and puppetDB, If I start the puppet master using the init script puppetmaster I get a permission denied error when a node connects: Master: [root@puppet ~]# service puppetmaster start Starting puppetmaster: [ OK ] Node: [root@puppet-slave ~]# puppet agent --test err: Could not retrieve catalog from remote

I auto-upgraded puppet (as usual) using "yum upgrade -y", and now all agents are getting error 400. # puppet --version 3.0.0 On agent (any!) # puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for build6.[censored]: Failed to find facts from PuppetDB at abyss.[censored]:8081:

Hi, Since the below is a little long, I put my question at the top: how do I troubleshoot awful exported resources performance in puppet and is there anything I can tweak to get it to run under 10 minutes in larger environments? I have a fairly modest environment (118 nodes, but prod will be at least twice as large). I''m trying to move my distributed nagios setup to one based on

I''m getting more and more "execution expired" as systems checking and hit puppetdb for the first time (switching from a mysql instance). The command queue isn''t long (1-5, if anything, all the time), and ym master itself seems to be dealing well enough. I have seen the collection time growing higher and higher though. This is a ~2K node deployment, and one of the few

Hi everyone; I was just wondering if anyone has any opinion/information on the pros and cons of using the built-in HSQLDB vs Postgres. Thanks! Bee -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to

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

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.

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

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''

trying to deploy puppetdb , puppet server is RHEL 6.1 , [root@puppet ~]# rpm -qa|grep puppet puppetdb-0.9.1-2.el6.noarch puppet-dashboard-1.2.9-1.el6.noarch puppet-server-2.7.17-1.el6.noarch puppetdb-terminus-0.9.1-2.el6.noarch puppet-2.7.17-1.el6.noarch on the clients, got an error for puppetdb , client1 :~ # puppet agent --test err: Could not retrieve catalog from remote server: Error 400

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

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

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