similar to: Could not describe errors

Hello folks, I''ve blended/updated the Glossary of Terms (<http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms>). It seems the definition of "manifests" is a bit different amongst members. Some people consider a "manifest" to be a configuration file written in puppet, e.g. any .pp file. But at my organization, we''ve considered the totality

What is everyone''s experience with Puppet on Ubuntu? Does it work as expected? Any caveats or oddities? -- DK -- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University

I think some conventions are in order to help with the documentation work. (1) As suggested by someone else earlier, I think we need a clear way to mark areas needing fixes with FIXMEs. (2) Topics under discussion or drafting should indicate such, perhaps at the top of the document, with a reference to the thread. On page comments should have a clearly designated area at the bottom of the

Anyone using the rrdgraph report on the puppetmaster on Debian stable? I''m trying to get this working and not getting far. I even took rrdtool and librrd0-dev from backports and I still get the same problem. It seems that the rrdfiles are being somewhat created, but nevertheless, the puppetmaster isn''t happy and keeps spewing: err: Report rrdgraph failed: Could not create

Hello >From my understanding, modules are not autosearched. So, if I have: include ssh ... then puppet will look for a module names ssh and class named ssh defined in /modules/ssh/init.pp Moreover, if I have: include ssh::global ... then Puppet will for class global defined in /modules/ssh/init.pp or /modules/ssh/global.ss. Is that correct? Or am I leaving out some imports

So I am beginning the long process of learning puppet... and it seems that I am missing some vital things. My systems are RHEL-4, and i have installed the puppet/facter/puppetmasterd from dlutter@redhat.com''s archive. [root@canopus puppet]# rpm -qa | egrep ''puppet|facter'' | sort facter-1.3.6-1.el4 puppet-0.22.2-1.el4 puppet-server-0.22.2-1.el4 on the client I

I just built new puppet rpm''s for Fedora (puppet-0.22.1-2) that fix the lockdir problem that many of you have encountered. The packages should show up on a mirror near you very soon. Unfortunately, I am having trouble getting to my buildsystem that I use for the RHEL versions of the RPM; I made the source rpm available on my people page[1] If you need the RPM for RHEL, you need to

What happened with the Mongrel effort? -- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University

I just discovered something interesting: node server.example.org { class A { ... } } The above doesn''t do anything. node server.example.org { include A class A { ... } } The above works. I was under the impression that classes defined within a node were assumed to be part of that node. I learned something new today. -- Digant C Kasundra

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:

Hello everyone, I''ve been working on an internal best practices document that also tackled giving proper terms to things that were at the time uncoined. But looks like we have a bit of a merge problem as other terms have been floating around that seem to conflict with some terms we''ve been using internally at my organization. I''m hoping we can discuss and

I''ve published the tarballs and whatever bad packages my publishing system knows how to create; look for more official debs, sun packages, and rpms in the near future, hopefully. Note that this is mostly a bug-fix release, and I expect it to be a pretty painless upgrade for most everyeone (but please, test before upgrading). Here''s the changelog: Compile times now

-----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,

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

Is there a way to tell the puppetmaster that I want to import all modules rather than listing each one individually?

Was file bucketing changed as part of this release or is this a bug? When I look in my bucket folder I see: drwxr-xr-x 2 puppet puppet 4096 Mar 17 00:04 5222e054e7bc6248f2e9b9146f75aff5 drwxr-xr-x 2 puppet puppet 4096 Mar 17 00:04 3255ad7efedebfd3eccbba74845002a1 drwxr-xr-x 2 puppet puppet 4096 Mar 17 00:04 f8569b1c57819072c37b36bd3814e328 drwxr-xr-x 2 puppet puppet 4096 Mar

file { "/var/log/syslog": target => "/var/log/messages" } generates the following error: err: //henson/stanford/syslog/file=/var/log/syslog: Failed to retrieve current state: undefined method `should'' for false:FalseClass

Hello, I am currently experiencing a bit of a quandry with how to specify default configuration applications to generic nodes. Here is an example setup: Classes: Class A Class B inherits Class A Class C inherits Class B Problem: I have unique hosts (nodes) X and Y and a bunch of other standard hosts. I would like X and Y to be able to override attributes in Class C (thus inherit class C) but

In the normal override method, you can change the value of a parameter, but can you unset a parameter? file { "/etc/somefile": mode => 644, owner => "dude" } File ["/etc/somefile"] { mode => unset } ??

Hello Puppet users, I had talked with Luke about this scenario and was wondering how others would/are handling something like this. Imagine a scenario where all servers will have a specific postfix configuration except for a server or two or three. So, you want to define a file "/etc/postfix/main.cf" and specify the source from your dist tree. But for those exceptional servers,