similar to: Puppet Faces - REST

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

What is the right path for ruby gems on puppet master. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0 /opt/puppet/lib/gems/1.8/gems/hiera-puppet-0.3.0 Later when I updated to new version of hiera then it installed (via gem install) under /opt/puppet/lib/gems/1.8/gems/hiera-1.1.1

Hi I am new in Puppet and i have one error when i test Postgresql module in infrastructure mode. I''m using Puppet 3.1.0 in Debian squeeze or 6.0.7 i tape the next command puppetd -t -v and this is the error info: Retrieving plugin info: Loading facts in pe_version info: Loading facts in postgres_default_version info: Loading facts in iptables info: Loading facts in puppet_vardir

Hello, I am trying to extend the ''select'' action in the catalog face to also display the value of the ensure parameter for that resource, like so: puppet catalog select <host> <resource> --extra parameter=ensure I have two questions: 1) What is the general approach for extending the standard shipped faces, is it even suggested to change them ? 2) Am I correct in

I''ve been hitting this issue for a long time. well over a year and I guess it''s time to start pushing it to try to find the root cause. I''ve seen this reported several times in the past but I''ve never seen a resolution found for this exact problems. There are other root causes for pson errors that have been resolved, but not for the ones describing my

Does anyone know why i would get a module error for my ''base'' module that I''m not even including for a node? I''m explicitly NOT include the ''base'', yet puppet-client-t2 still errors when i pull it in. Snips from both are below. Any ideas why this would happen? Thanks, JJ ==== site.pp file [root@puppet-master-t1 puppet]# cat

Dear All, I''m very new to Puppet Enterprise.... I have the following setup so far: 1. Puppet Master (Puppet Ent) on Ubuntu with its own Agent 2. Puppet Agent on MAC Mountain Lion Everything looked ok but then I noticed this on the MAC (below), which suggested to me I had the wrong Agent? I''m a little confused on how to get the Puppet Ent Agent for MAC? Info: Retrieving

My install was working for a couple of months until I rebooted my puppet server. The clients do not report an error when I run puppet agent -t. I''ve attempted to remove certificates and renew. The clients get new certificates, but the console still does not update. Even the puppet server itself is not updating as a client. After reboot the only thing I have noticed that changed

Hello, First of all I am new to the Puppet technology. I am trying to get my puppet agent (windows) to reach my puppet master (Linux) server. In this tutorial: http://docs.puppetlabs.com/learning/agent_master_basic.html It claims to test your puppet agent you need to use the ''puppet agent --test'' command. My result when I tried this is: C:\Program Files (x86)\Puppet

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

Hello All, I wanted to create two two MySQL database with same user credential using Puppet-MySQL. How can I achieve this? Please find my script below. class mysql::vsdatabase { include mysql mysql::db { ''vidispine'': user => ''user'', password => ''user123'', host => ''db.<hostname>.com'', } } How can I add

I made two decisions this afternoon that are now related to each other. 1. Use more of the modules that exist in the Forge 2. Rebuild my monitoring server As I perused the various modules that help with managing monitoring packages my eyes fell upon a module that reported to be able to manage nagiosql, a setup that I had been planning on migrating my nagios monitoring to. So I installed

I have two different server type. Once is debian 6.0 squeeze and puppet version is "2.6.2". And other Ubuntu 12.04 and puppet version 2.7.11. Puppet master server is Ubuntu 12.04. I write something in /etc/crond.d/puppetcron which works specific time. Problem is if debian servers have any changes, don''t send mail me but ubuntu server send mail when every work like this:

Hi, I got the following error:- Error: Could not retrieve catalog from remote server: wrong header line format In puppet.conf file on puppetmaster, I added following lines - facts_terminus = inventory_active_record dbadapter = mysql dbname = dashboard dbuser = test dbpassword = test123 dbserver = puppet-master.com dbsocket =

Trying to understand how puppet reports errors Example of why I am asking the question (on a test setup environment) Created a base-1 node Created 2 slave nodes that inherit from base-1 Let''s call those slave1 and slave2 No errors. It all works. Created a base-2 node created a third slave that inherits from base-2. Let''s call that slave3 Get an error Could not retrieve

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

Hi all, first post here... reposting this from Stack Overflow as it didn''t get much traction there... I am using puppet to read a fact from facter, and based on that I apply a different configuration to my modules. Problem: the puppet agent isn''t seeing this fact. Running puppet agent --test interactively works as expected. Even running it non-interactively from a script

Has anyone taken a stab at putting together a Puppet module to install and/or manage SOGo <http://www.inverse.ca/english/contributions/sogo.html>-- a very fast and scalable collaboration suite (groupware) that offers calendaring, address book management & a full-featured WebMail client? With the help of someone on the SOGo user''s mailing list, I''ve been able to

Has anyone ever written rspec-puppet-based code to check an entire site, i.e. looping over all node names - with proper facts - to verify that the catalog for each node is OK? I haven''t seen any examples of this. /P -- 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

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 -