similar to: ANNOUNCE: Puppet 0.22.2 (grover)

Can anyone who''s having this problem please send details? I''m trying to reproduce it -- I''ve got 5 clients concurrently retrieving 200 10k files made of random binary, and I can''t get any corruption or memory growth at all. Is everyone experiencing the problem using Mongrel? Webrick? What versions of ruby? Are only big files affected? Small files?

I tried to install the ''mongrel'' gem tonight via puppet in an attempt to migrate from webrick to mongrel as described on the puppet site[1]. I added the following to my manifest: package { "rubygems": ensure => installed; "mongrel": ensure => installed, provider => gem, require => Package["rubygems"]; }

Hi all, Turns out there''s a small backward compatibility problem in 0.22.2. If you''ve got clients in older versions sending reports to a daemon running the newer version, you''ll run into a problem because I renamed the Puppet::Metric class to Puppet::Util::Metric. I''ve committed a fix to svn, but it''s not a big enough problem to require a new

Seems that blastwave is all about pkgutil now. Are there any plans to support this? Best, Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to

I''m having this issue where "puppetd -v -o" hangs (won''t return my prompt) when starting a daemon I wrote. If puppetd is running as a daemon a zombie process is created each time puppetd tries to start my daemon. Puppet detects when the daemon is down and starts it just fine. I''m using version 0.22.3 on RHEL 5. Here''s the class. I''ve

After upgrading my puppetmaster server to 0.22.2 using David''s src RPM''s for RHEL4 rebuilt for x86_64 i am getting the following error when puppetd attempts a configuration run. Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run Puppet::[1]Network::Client::Master: Invalid value ''nil'' for noop When puppetd is started the initial run is

Hi, I''ve just installed 0.22.2 and believe I''ve discovered a bug (or oversight). I have an exec like this: exec { "change-to-local-mirror": command => "sed -i ''s#\(KERNEL_REPO.*=\).*#\1 $mirror#'' ${rulefile}", path => "/usr/bin:/usr/sbin:/bin",

Hey folks, I''ve just uploaded an apache2 module[1] to our Google Code repository[2]. It''s based largely on the recipe available on the Puppet trac[3], but with a fair amount of modification and generalization... Basically, it provides abstractions for config file snippets, site definitions, and apxs modules -- and then "basic" and "debian"

I just realized that if you don''t have redhat-lsb on your (Fedora 7) box, all those lsb* facts don''t show up. Should I make redhat-lsb a requirement for the facter rpm to guard against that ? David

Ok, I''ve gone through all of the open tickets and assigned the ones I''m hoping to fix in grover. If you''ve got a bug that you are positive has to be fixed but is not marked for grover, please respond to this email with that bug info (please respond to the list, not directly to me). More importantly, if there''s a bug in that list that you can fix,

Hi all, The underlying assumption of membership in any community is that your participation is at worst neutral, and if possible positive. Communities, online or off, generally do what they can to protect themselves from detrimental influences, which is where policies, politeness, moderators, and all that come into play. Puppet''s community has been both fortunate and awesome,

This is in reference to David Schmitt''s writeup [1] I like that writeup a lot; I just had a few comments/clarifications: * Namespaces: For now, we just use a flat namespace for modules, i.e. you can''t have modules within modules, and you always know that in a fully qualified name ''foo::bar::baz'' that ''foo'' is the module name and

Hi, I''m starting to move over to Modules, which looks pretty clean and solid. Reading http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation, one thing that confuses me is how the client resolves the implicit file server resources. I''ve got a few different puppet master servers running on different ports, and my configuration re-defines $puppet_master_host and

I updated http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation to reflect how I intend to implement modules, and what that will look like from a user''s point of view. Comments/flames etc. welcome. David

Hello everyone, A long time ago, I posted the Stanford Best Practices and I''ve gone through and updated it today. I''d like to have people go through it and see if we can strip out some Stanford specific stuff and tag this as an official best practice. I think an official best practice will be important as more and more people consider making shareable modules, etc (mostly

Hello all, puppet hangs while trying to restart a daemon when the associated config file changes, here the log: Mar 19 11:30:04 ingentTest puppetd[27390]: Starting Puppet client version 0.22.0 puppetd[27390]: Starting configuration run puppetd[27390]: (/ingenttest/qualsevolnode/guaita[guaita]/File[/etc/guaita.conf]/content) synced puppetd[27390]:

On the module organization wiki, we''re got the following statement: To control access to the files in modules, the fileserver configuration can contain an explicit declaration of a ``modules`` module:: ... however, I thought the fileserver couldn''t define module or any section that is in the module paths. Has anyone tried this? And if it doesn''t work, is there

hi, is there a way to create the database (say development and or production) specified in database.yml with rake? thanks, Enrico -- "The only thing necessary for the triumph of evil is for good men to do nothing" Edmund Burke

Would it be possible to... ( I suppose that this is an enhancement request )... automatically do the following on a client-side manifest failure: 1. Wipe localconfig.yaml and state.yaml and try again (seems to fix most things for me) 2. Revert to a last known good configuration if all else fails. Thanks, Trevor _______________________________________________ Puppet-users mailing list

Greetings - Maybe I''m a bit slow, but I''ve been trying to understand how to use a module for the better part of a day and I''m not getting it. Here''s what I''ve done: Using puppet 0.23.2 1. Downloaded the shorewall module from David Schmitt''s git repo (Thanks David!!!!) and placed it in the directory /var/lib/puppet/modules (using the rpm