search for: giridharagopal

I am attempting to install PuppetDB from source. I am a bit confused however, is lein required? 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit

...tart the puppetdb daemon 5. On your puppetmaster(s), install the new puppetdb-terminus package 6. On your puppetmaster(s), start the puppetmaster daemon 0.9.2 ===== Many thanks to the following people who contributed patches to this release: * Jason Ashby * Kushal Pisavadia * Erik Dalén * Deepak Giridharagopal * Nick Lewis * Matthaus Litteken * Chris Price Notable features: * Allow more advanced storeconfigs queries Now, when using PuppetDB, your puppet manifests can use "and" and "or" in collection queries: File <<| mode == 0755 or content == "bar" |>&g...

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

I have a node that has some bad stored configs (namely the wrong ssh host keys) that I''m trying to clear out. Looking around it seems I''m supposed to do: puppet node clean foo.example.com However, that keeps bailing out because it''s trying to open a SQLite3 db where stored configs are normally kept, but my stored configs are kept in puppetdb (http://pastie.org/7814483

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

...s.com/puppetdb # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello # 1.0.1 Changelog ============== Many thanks to the following people who contributed patches to this release: Deepak Giridharagopal Nick Lewis Matthaus Litteken Chris Price Fixes: (#16180) Properly handle edges between exported resources This was previously failing when an edge referred to an exported resource which was also collected, because it was incorrectly assuming collected resources would always be marked as NOT expor...

I just installed PE, and notice that it does not use either stored config nor puppetdb. It uses the activerecord to store facts in a mysql db. Why puppetlabs let us to use these but they do not use them in their enterprise version? Thanks. Hai T. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

...ppetdb server, start the puppetdb daemon 5. On your puppetmaster(s), install the new puppetdb-terminus package 6. On your puppetmaster(s), start the puppetmaster daemon 0.11.0 Change Log ========= Many thanks to the following people who contributed patches to this release: Kushal Pisavadia Deepak Giridharagopal Nick Lewis Moses Mendoza Chris Price Notable features: Additional database indexes for improved performance Queries involving resource (type,title) or tags without much additional filtering criteria are now much faster. Note that tag queries cannot be sped up on PostgreSQL 8.1, as it doesn...

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

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

...# See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello ============================ ## PuppetDB 1.3.0 Release Notes ## ============================ Many thanks to following people who contributed patches to this release: * Branan Purvine-Riley * Chris Price * Deepak Giridharagopal * Ken Barber * Matthaus Owens * Moses Mendoza * Nick Fagerlund * Nick Lewis Notable features: * Report queries The query endpoint `experimental/event` has been augmented to support a much more interesting set of queries against report data. You can now query for events by status (e.g. `su...

Hi everyone, Me again regarding puppetdb, I have the following warning message: "Jun 13 12:49:15 puppetmaster puppet-master[28444]: Ignoring invalid UTF-8 byte sequences in data to be sent to PuppetDB" Do I have to worry? Regards, JM -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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,

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:

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

...Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello # Changelog 1.1.0-rc4 ========= Many thanks to the following people who contributed patches to this release: * Chris Price * Deepak Giridharagopal * Jeff Blaine * Ken Barber * Kushal Pisavadia * Matthaus Litteken * Michael Stahnke * Moses Mendoza * Nick Lewis * Pierre-Yves Ritschard Notable features: * Enhanced query API A substantially improved version 2 of the HTTP query API has been added. This is located under the /v2 route. Detail...

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

Hello everyone, Just getting my first puppet master set up and I am having a problem that I just do not know how to get past. For some reason, my certificate store keeps getting corrupted. Basically what happens is that the server will issue itself a valid certificate (after removing the ''bad'' cert) and will run just fine. When I start puppetDB (I am pretty sure it happens

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