similar to: Writing your own functions

Hello! I''ve been trying to use facts from Facter in a custom function. I''ve been following Matthew''s entry in the wiki (http://www.reductivelabs.com/trac/puppet/wiki/WritingYourOwnFunctions). What i''m seeing is that Facter[''fqdn''].value is always returning the fqdn of the puppetmaster host. I was expecting the fqdn of the client host.

I''m working with a pretty simple config at the moment to track down some issues I''m seeing with custom facts and plugins. I have factsync = true (default locations) and I have a simple fact in /var/lib/puppet/facts/ (actually it''s David''s netmask plugin) my pp file I''m testing with contains only: notice "netmask: ${netmask}" puppet -v

Hi there, just to be sure: http://reductivelabs.com/trac/puppet/wiki/WritingYourOwnFunctions says that "The file name is derived from the name of the function that Puppet is trying to run." Is this still true? I ask because I currently write a set of math functions (min,max, plus, minus and so). My first try was to create a math.rb, where I had: module Puppet::Parser::Functions

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

Hello there. Just to let you know i have just put in production mode puppet on 41 freeBSD 4.7 virtual servers (yes not real servers but "jailed ones"). I had some little problems with facter at first but i have manualy upgraded the servers that where affected by the little "facter does not read his facts" problem i had. I should have missed something in my deploiement.

Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted:

Hi all, i'' m trying to configure puppet to use rails with postgresql. I'' m having troubles to make it work. Got no error when running puppetmasterd but nothing is being populated in the DB. Is anybody using puppet with postgres ? my config (in puppet.conf) [rails] dbadapter = postgresql dbname = mydb dbserver = localhost dbuser = user dbpassword = password

I have some facter file to distribute before running puppet on the platform. The problem is : how can i send the facter local.rb file so the rest of the .pp file take into account the new facts created ? ex: i have sudopath as a facter fact and one sudoers class that need that sudopath to work. How do you model that ? it seems puppet would have to rerun after the new local.rb is downloaded

Anyone ever migrated the puppetca to a different host? What are the steps that are involved?

I just updated to 0.22.2 and am running into a strange issue. I''m starting puppetmaster, and seeing this in my error log: err: /puppetconfig/reporting/File[/Library/Puppet/Generated/Server/var/reports]/ensure: change from absent to directory failed: Cannot create /Library/Puppet/Generated/Server/var/reports; parent directory /Library/Puppet/Generated/Server/var does not exist err:

Hi all, One of the major new features in the upcoming release is that Puppet now uses a graph library internally to handle resource relationships. The big benefit to all of you is that you can use this library to turn these graphs into images. The trick, right now, is adding --graph when you run puppetd. This creates .dot files, which can then be interpreted by the

Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file

Hi all, This has theoretically been a high priority for a long time, and I''m finally going to get it done, I think. Here''s my plan, and I''d appreciate any comments you might have on it. Currently, sections only have meaning internally, in that one can call ''config.use(section)'' to create any directories needed for that section. Additionally,

hi,all. I found a interesting problem. first ,a new node run the puppetd to connect the puppet server, then was treated as "default" node. that''s right. Then I add the new node''s hostname in a node define. and run the puppetd ,is still get the default manifests file. But when I restart the pupppuetmaster, then it can get the new manifests file to correspond

This has been a much-requested feature, and is now a reality (in svn trunk): There is a new option, --ignoreimport, that will (surprisingly) ignore import statements. This is really only useful when using -- parseonly in a commit hook, and note that you''ll have to add the option to --parseonly, none of the puppet executables will add it for you. You should be able to

I was wondering if there would be any benefit to the general community if I made available a debian and ubuntu repository of up to date puppet packages. I have the infrastructure in place anyway for my work (pbuilder + falcon), and can quite easily run up a vhost on a VM somewhere. Debian Etch (4.0) for example has puppet 0.20.1, and will never get a newer version. Ubuntu Feisty has a newer

Hi there, I have a problem I don''t know how to solve. Let''s say you have two services, applications, whatever that communicate with each other, and they establish a shared password or key to authenticate to the other part. This happens with DHCP/DNS (I think is called dynamic zone update, the DHCP server updates the DNS zone with information from the dynamically configured

For anyone that has experienced the odd End of file or Cannot describe errors, we''ve found that switching to Mongrel has fixed this problem for us. We''re currently running 5 instance of puppetmaster under mongrel (with the apache proxy in front) and things are going great. For more information on setting up Mongrel, visit:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi *! How do you monitor when the last puppet transaction was successful on a node? I''m searching for something easy like a timestamp, so I can put a nagios watch on this. Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb,