similar to: Does Puppet ensure that a service is up and running?

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:

I''m still tinkering, moving over code from CFE to Puppet in a test environment. One item I did with CfE was manage services. If something wasn''t running, it was restarted. Puppet''s service integration makes this easy. The flip side, is how do you guarantee Puppet''s running? I pulled some tricks with CfE to ensure it was always running. I made CfE a direct

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

I''m sure everyone has read and committed the Puppet Best Practice to memory by now (I joke). One of the things I''ve written in there deals with trailing commas, which I adopted from the way I used to do multiline in Perl, but I''ve noticed that most people don''t tend to do that in Puppet. Should I revise this or should we all start using the trailing commas?

Is there a way to specify on a per-object basis that Puppet should merely report that an object needs to be updated without actually performing the update? This would make it possible to detect changes to critical objects (e.g. config files) that Puppet shouldn''t try to fix automaticaly. -- Jos Backus jos at catnook.com

--On Monday, May 14, 2007 9:16 PM -0700 Jos Backus <jos@catnook.com> wrote: > ObPuppet: we ramping up our deployment this week to around 200 hosts. So > far everything has been going smoothly. We don''t have nearly as many and yet, we see occasional errors ("End of file reached") which seems to indicate the network cutting out. I can''t imagine what would

Anybody else experience the need to restart puppetmasterd before a node can register itself. I''ve been cleaning up my installation here on client nodes and every once and a while I find myself needing to restart the puppetmaster daemon. A client node attempts to connect and never does. A restart fixes things. There doesn''t seem to be anything useful in the error messages

Hi all, Can someone pls help me on how to make this bash script? I want to monitor a process, and then when the process (for some reason) dies, the script will start the process again. Thank you, -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 18:39:44 up 10:21, 2.6.16-1.2111_FC5 GNU/Linux Let's use OpenOffice. http://www.openoffice.org

With both puppet-0.23.0 and 0.23.1 if I setup just the configuration file puppet.conf, none of the puppetd options seem to get parsed. I first noticed this when monit failed to start/stop services due to the lack of a pid file being generated (and mine is not in one of the usual places). I''m sure that something like the patch attached but I bet it breaks other assumptions :-) Cheers,

Hi all, I''ve just rewritten the Puppet introduction from scratch: https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I think it''s better, but I''m not convinced it''s a whole heckuva lot better. Comments are very much appreciated, especially if you can recommend a better approach to the document. I tried to organize it how I have been giving

OK. I thought I would start by looking at how cron.rb in the puppet lib/type works because what I''m trying to accomplish is similar. However, when looking through that, it wasn''t immediately obvious to me how or when the resulting cron file was getting written out. Is this getting stored up in some instance var or something? Maybe getting sent to standard out and some

Hi, I was wondering if there is any of getting the gem package provider to run non-interactively? When upgrading mongrel it fails because it gets prompted for which version to install: Attempting remote update of mongrel Select which gem to install for your platform (x86_64-linux) 1. mongrel 1.1.1 (ruby) 2. mongrel 1.1.1 (jruby) 3. mongrel 1.1.1 (mswin32) 4. mongrel 1.1 (mswin32) 5.

I just started digging into puppet and it looks like puppet is using a pull model. You have a master server and clients talk to it to get config info. Is anyone out there using a push model? If not, why not? Are there security reasons you would use one over the other? It seems that cfengine also uses a push model, so I wondered if this is a "standard" or if there are specific

Quick and dirty: --- lib/facter.rb (revision 203) +++ lib/facter.rb (working copy) @@ -989,6 +989,18 @@ %x{/usr/sbin/scutil --get LocalHostName} end end + Facter.add(:interfaces) do + confine :kernel => :linux + setcode do + %x{/sbin/ifconfig -a -s}.split($/)[1..-1].collect {|line|

How about adding a --no-detach option (to be used in combination with --daemon) to rsync so it can be run under Dan Bernstein's daemontools' supervise? If there's interest I'll provide a patch. -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/

I''d like to keep the desired and current states of a machine regarding it''s configuration. Sometimes a chain of administrative commands is needed to get a special thing (re)configured on a machine, e.g. reconfig of a suncluster. This cannot be done with puppet in an easy way. In the majority of cases, these commands change appropriate files, which reflect the current

This patch updates the files under popt/ to the latest vendor drop. The only change is the inclusion of a FreeBSD-specific patch to popt.c. This is needed in case somebody decides to build rsync on that platform without using the port. I'm not happy about the wording in popt/README.rsync so I may change it. The patch is available at http://www.catnook.com/rsync-popt-1.5.1.patch Comments

I''ve been watching the thread where Luke is having to spend time defending his position about documentation. Can we get off that? From my perspective, Luke, I''m glad you have documented as much as you have. I''m one of the few who have been a little stymied by what documentation is available, but in no way do I believe berating you for your lack of documentation is a