similar to: 0.20.1 deb from the site not quite working

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

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

Are exec resources triggered by notify events supposed to be run once for every event received or only run once per run irregardless of the number of resources that notified it? It seems to me that it gets run twice no matter how many resources triggered it. consider the following class: class dhcp { $prefix = "/usr/local/etc/dhcpd" $dhcpd_conf = "$prefix/dhcpd.conf"

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

I might have the terminology wrong, but how to a give new puppet providers to the puppet clients? I''m thinking a provider is the thing the puppet client uses to implement a task that the master has given it. Am I way off here? Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

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 turned on reporting the other day and I''m seeing alot of these when puppet runs. Especially during times when nothing is going on (middle of the night etc) Tue Dec 11 12:34:48 -0500 2007 //base/puppet/puppet::client/Service[puppet]/ensure (notice): ensure changed ''stopped'' to ''running'' It''s also quite odd that puppet when it runs it thinks

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?

I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and

I''m just starting a roll out of Puppet and I''m seeing a problem on maybe 25% of client nodes. The symptoms are that the clients stop updating. In the Puppetmaster log, I''m seeing things like: Feb 9 20:10:23 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9 20:40:41 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9

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

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,

We''re still intermittantly getting these messages in syslog on various different systems: Feb 14 17:32:10 server-dev puppetd[20363]: Could not call puppetreports.report: #<EOFError: end of file reached> Feb 14 17:32:10 server-dev puppetd[20363]: Reporting failed: end of file reached Anyone else ever see stuff like this?

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,

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

I have the error err: Invalid argument - /var/lib/puppet/state/ puppetdlock appearing on one of my servers. I have plenty of disk and plenty of inodes. The daemon is not running. I run it manually using /usr/sbin/puppetd --verbose --no-daemonize --onetime --server=xxx --fqdn=yyy There is no file /var/lib/puppet/state/puppetdlock and there is a root writable directory /var/lib/puppet/state