similar to: PuppetDB Cannot Find Postgresql Driver

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

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 LLVM developers, I have successfully installed LLVM 2.9 on an ubuntu linux box, with a LLVM-based frontend support of gcc and g++. After installing successfully vmkit I have tried running my java applications, but it failed. I have installed the latest stable release of vmkit (0.29) using the introduction text of the LLVM website. The application does consist of two programs. The first

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 all, I am trying to setup puppet master and puppetdb on same node using puppetdb module. When I try to run puppet agent -t, I see following erorr notice: Unable to connect to puppetdb server (ip-10-172-161-25.us-west-1.compute.internal:8081): SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed notice: Failed to connect to puppetdb; sleeping 2

PuppetDB is operating fine, but I can''t figure out how to disable it from listening globally on TCP 1099 or 58722 How do I disable them from listening globally without having to resort to iptables? $ lsof -i -n -P | grep java | grep LISTEN java 30115 puppetdb 22u IPv6 119118 0t0 TCP *:1099 (LISTEN) java 30115 puppetdb 23u IPv6 117236 0t0 TCP *:58772

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 installed JGR library both on ubuntu 7.10 and 7.04 on 7.10 all went fine, but on 7.04 I recived massage: Exception in thread "main" java.lang.NoClassDefFoundError: org/rosuda/JRI/RMainLoopCallbacks at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at

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

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

Hello, I am currently trying to get the puppetdb dashboard and the puppet dashboard working on the same system. Puppet dashboard is working great but after "successfully" installing puppetdb following puppet''s opensource instructions the puppetdb dashboard just doesn''t seem to exist (according to some sites I should be able to get to it by going to

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 -

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

rpcclient $> adddriver "Windows NT x86" "HP CLJ 8500 - PCL":NULL:NULL:NULL:NULL:NULL:NULL:NULL result was NT_STATUS_UNSUCCESSFUL rpcclient $> adddriver "Windows 4.0" "HP CLJ 8500 - PCL":NULL:NULL:NULL:NULL:NULL:NULL:NULL Printer Driver HP CLJ 8500 - PCL successfully installed. rpcclient $> This is HEAD, bang up-to-date. I'm trying to figure it

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

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:

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

Fresh install on a brand new box (Dell Precision 3500) of 5.6. I install Sun java-1.6.0_26-b03, Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) Then ln -s /usr/lib/jvm/java-1.6.0-sun-1.6.0.26.x86_64/jre/lib/amd64/libnpjp2.so /usr/lib64/mozilla/plugins about:plugins shows java enabled (oddly enough, I seem to have flash, 32-bit, in the 32 bit libs, and that doesn't show; guess

When I run openssl s_client -host puppet -port 8081 -CAfile /etc/puppet/ssl/certs/puppet.fqdn I get Verify return code: 21 (unable to verify the first certificate). If I run the same command, but use port 8140 to connect to puppet, I get a return code of 19 (which is correct). I believe that, if I fix this SSL problem then it would fix my main problem which is : Report processor failed:

Hi everyone I''m currently trying to install Puppetdb on my puppet master server (on Suse 11 SP2 64bits) using the Source method<http://docs.puppetlabs.com/puppetdb/1.3/install_from_source.html>and I can''t figure out why it is not working. It''s seems to be stuck at the begining of the rake install I have Facter in version 2.0.0 # facter -v 2.0.0 I installed