How do I quiesce a puppetmaster before reconfiguring it?

[Larry Fast]

If I need to do any maintenance on my puppetmaster I would like to ensure that I don't break any partially completed puppet runs. Is there any way to quiesce the puppetmaster before shutting down the service?

I run my puppetmaster on top of apache passenger. If I execute "service httpd stop" it breaks all incomplete puppet runs. Is there another way that I should stop the service so that the puppetmaster can properly wind down?

[Trevor Vaughan]

Try 'service httpd graceful'

On Sat, Feb 8, 2014 at 6:45 PM, Larry Fast <lfas...@gmail.com> wrote:

If I need to do any maintenance on my puppetmaster I would like to ensure that I don't break any partially completed puppet runs. Is there any way to quiesce the puppetmaster before shutting down the service?

I run my puppetmaster on top of apache passenger. If I execute "service httpd stop" it breaks all incomplete puppet runs. Is there another way that I should stop the service so that the puppetmaster can properly wind down?

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7cc18c28-5e60-493b-b732-beefa4a91959%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvau...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

[JuanBrein]

service httpd graceful will help. I would highly recommend you to have a dev / prd environment for your puppetmaster as well. Vagrant is very helpful for that. Having auto provisioned puppet masters is really helpful as it allows you to test new puppet master upgrades and configuration changes.

Cheers

Juan

[Larry Fast]

graceful-stop seems to be a modest improvement but its not a panacea.  AFAIK it only ensures that open connections are not dropped.  A puppet run seems to involve multiple connections. At best this only completes individual transactions before shutdown.   Also, when I look at this problem in a bit more detail, the puppetmaster doesn't seem to know if there are active puppet runs still in progress.

So the best I could hope for is a way to block new puppet runs from starting and then waiting a reasonable length of time before halting the service.  Is there anything in the puppetmaster arsenal that could allow it to run without allowing new puppet runs to start?