similar to: My updated remotefile

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

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 community, We are running puppetmaster 0.22.3 with 45 servers attached and we are seeing a lot of messages that say: (err): Could not describe /ssh/sshd_config.RedHat: End of file reached: We were seeing a lot of this with 0.22.1 as well. Interestingly, during the stretch where we were running 0.22.2 (most of April until 2 days ago) we didn''t see this error at all or very

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

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

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

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

Hello folks, I''ve finally figured out how to get the Wiki to notify of changes. Luke is going to work on getting a proper link in the header but for now, make sure you are logged in and then if the page you want to watch is at: <http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms> then in your browser URL, substitute "notification" for "wiki":

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

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:

Hi, I''m exploring Puppet and have hit a rather weird problem. The puppetmaster server is running CentOS4, fully updated, with puppet installed from the dlutter RPM repo, version 0.20.0-1.el4. I tried adding the remotefile function definition from http://reductivelabs.com/projects/puppet/documentation/installation.html in /etc/puppet/manifests/utils/remotefile.pp but when I start

Howdy, Found out about this project while looking for via ONLamp''s FreeBSD build system article. After finding cfengine a tad arcane, this project seems like a good fit for my setup. I''m still at the tinkering phase, but I envision this thing bootstrapping and maintaining several FreeBSD installs which have different CPU''s and packages. The Good News:

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

I tried using $name in this manner: remotefile { "/etc/auto_direct.local": mode => 644, source => "solall/$name" } (The remotefile function is handy, BTW) When I use $name here, instead of specifying the actual path to the file (solall/etc/auto_direct.local), puppetd ends up making /etc/auto_direct.local an empty directory. Shouldn''t $name

Hi, I had a working puppet setup using version 0.22 until the ruby security patch bit me. I tried upgrading server and clients to 0.24.1 however my old manifests don''t seem to work anymore. When I run puppetd on the client I see lots of messages like: err: //Node[waterbuck]/yumupdater/Remotefile[/etc/cron.hourly/yumupdater]/File[/etc/cron.hourly/yumupdater]/ensure: change from absent

Hi all, I''ve just implemented a [crude] manifest to apply a set authorized_keys file to the root account of a puppet client. class rootssh_test { file { "/root/.ssh/authorized_keys": owner => root, group => root, mode => 0600, content => template("rootssh_test") } } The template has two ssh id_rsa lines in. When the client applies

Hello Puppeteers! Stanford University Information Technology Services is looking for Unix Systems Administrators. Stanford University not only uses Puppet, but does what it can to contribute to the betterment of Puppet, and we''re looking for good candidates to fulfill our open positions, and I''d love for those new hires to be Puppeteers! So if you are interested, please

Hi everyone, I got a basic puppetmaster setup, which works well for Linux. I''ve setup a basic function: define remotefile($owner = root, $group = root, $mode, $source, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Given the following: file { "/my/file": source => "puppet://server/path/to/some/file", ensure => absent } Puppet will copy /my/file to the host. What I was hoping was that ensure => absent would trump a source file. However, if we change the above slightly like this: file { "/my/file": source =>