Displaying 20 results from an estimated 10000 matches similar to: "Trying to setup puppetdbquery on puppet-3.0.0-rc5"
2013 May 27
2
Puppetdbquery 1.1.0, now featuring hiera backendception
I just released dalen-puppetdbquery 1.1.0, one cool new feature in this
release is a hiera backend.
So if you have a puppet class that takes a list of hosts as a parameter you
can now fill it using dynamic data from a puppetdb query. No need anymore
to modify the module itself or create a wrapper class around it to do the
puppetdb query in.
It requires another hiera backend to be active at the
2013 Jan 24
5
Searching for Nodes
Hello All,
I''m reviewing switching to puppet from chef and am trying to identify how
to port the various features.
I have hit a stumbling block searching for nodes. In Chef i could search
for a node by role, but I am lost as how to do this with puppet and classes.
Example:
I want my load-balancing node to look for all application server nodes and
grab their ip address (and hostname
2013 Feb 19
1
Functions for PuppetDB
Is this the best option for accessing puppetdb data from modules?
http://forge.puppetlabs.com/dalen/puppetdbquery
Any other recommendations?
--
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 this
2013 Apr 29
2
checking puppet run status of node A during puppet run of node B
I have some middleware where the successful configuration of node B is
dependent on the successful configuration of node A. Node B must pull
additional information from node A during its configuration. Is there any
built in functionality in puppet for checking the completion status of
other nodes? Right now my intent is to write a custom function to query
the puppetdb which is storing
2013 May 06
3
Announce: PuppetDB 1.3.0 Available
PuppetDB 1.3.0 is now available for download! This is a backward
compatible feature release of PuppetDB.
=============
## Downloads ##
=============
Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb
Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/
# Documentation
2013 Jan 07
3
Error: Could not retrieve catalog from remote server: execution expired
Hi everyone,
I recently ran into an issue where my puppetmaster can''t run puppet on
itself. It errors out with the following:
Error: Could not retrieve catalog from remote server: execution expired
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
I''m running Puppet 3 with passanger and puppetdb (hsql). I''ve tried
restarting
2013 May 24
6
Puppet/Nagios/PuppetDB slow performance
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.
2013 Sep 02
4
puppetdb - getting a list of specific facts for specific hosts?
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
2013 Feb 20
1
Announce: Module puppetlabs/postgresql 2.1.0 Available
A new release of the puppetlabs/postgresql module is now available on the Forge:
https://forge.puppetlabs.com/puppetlabs/postgresql/2.1.0
Changelog
========
This release is primarily a feature release, introducing some new
helpful constructs to the module.
For starters, we''ve added the line `include
''postgresql_conf_extras.conf''` by default so extra parameters not
2012 Jul 12
11
Announce: PuppetDB 0.9.2 Available
PuppetDB 0.9.2 is the third beta release on the road to 1.0. Changes
include new features and bug fixes. For details on changes
in this release, please see the release notes below.
# Downloads
Available in native package format at
http://yum.puppetlabs.com
http://apt.puppetlabs.com
Source (same license as Puppet): http://github.com/puppetlabs/puppetdb
Available for use with Puppet
2013 Oct 07
6
Force Fact within manifest
I have a requirement where I want a Fact to be stored in PuppetDB during
the manifest run and not during the initial fact gathering phase.
I know I can, in my manifests, create a file in /etc/facter/facts.d or I
can write a Ruby script that will then be distributed by plugin sync. But
both of these methods will only publish the fact during the initial phase
of the puppet agent run. What I
2012 Oct 04
4
Puppet 3.0 + Inventory search
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
2012 May 18
24
Announce: PuppetDB 0.9.0 (first release) is available
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
2013 May 14
1
PuppetDB Cannot Find Postgresql Driver
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
2013 Jul 25
9
Not collecting exported resources without storeconfigs
# cat /etc/redhat-release
CentOS release 6.4 (Final)
# puppet --version
3.2.3
# rpm -q puppetdb
puppetdb-1.3.2-1.el6.noarch
I am now receiving "Not collecting exported resources without storeconfigs"
for my opsview module. It was working fine on puppet 2.7 with
Activerecord/MySQL. I am still new to puppetdb so maybe I am missing
something. This is from puppet.conf:
storeconfigs
2012 Jul 06
4
puppetdb listening on ipv6 port 8081 , not ipv4
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
2013 Aug 23
3
puppet-ls with Puppet 3.2
Dear all,
I would like to find out if a files is managed by puppet. To do that I
tried the puppet-ls script.
But I get the error:
./puppet-ls
grep: /var/lib/puppet/client_data/catalog/*.yaml: No such file or directory
In the head of the script I can read "# tested on 0.25". It is the latest
version I could download.
Does somebody use this script with puppet 3.x?
Is there an
2012 Jun 29
5
puppetmaster init script - bug ?
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
2012 Nov 05
9
puppetdb postgresql Connection refused
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
2012 Jun 12
1
puppetdb indicated only facts were replaced, no sign of catalog
Dear all,
I have this setup on Ubuntu 12.04 and using puppetmaster/puppet 2.7.14 and
puppetdb/puppetdb-terminus 0.9.0 from puppetlabs.
My puppetmaster also run puppetdb. I also use hiera in this setup.
hadoop4 is puppetmaster and hadoop02 is puppet client.
puppet node status hadoop4.west.net
hadoop4.west.net
Currently active
Last catalog: 2012-06-05T23:23:33.159Z
Last facts: