On May 26, 2011, at 1:14 PM, Douglas Garstang wrote:
> On Wed, May 25, 2011 at 1:19 PM, Brian Gupta wrote:
> Douglas,
>
> I have to concur with disconnect, now that we are using Foreman, many
> of the things we setup in the past to catch these things are now
> redundant. I don't know why you "do
On Wed, May 25, 2011 at 1:19 PM, Brian Gupta wrote:
> Douglas,
>
> I have to concur with disconnect, now that we are using Foreman, many
> of the things we setup in the past to catch these things are now
> redundant. I don't know why you "don't like" Foreman, but I have to
> say along with our ini
On 05/25/2011 01:12 PM, Douglas Garstang wrote:
> I probably waste quite a bit of time each week restarting the puppet client,
> and logging systems, and tailing the messages file, to see if my puppet
> changes worked. Is there a better way? How do people normally do this?
>
> Sure, I can use pupp
Douglas,
I have to concur with disconnect, now that we are using Foreman, many
of the things we setup in the past to catch these things are now
redundant. I don't know why you "don't like" Foreman, but I have to
say along with our initial decision to use puppet, and managing our
configs with versi
Foreman can email error reports automatically. (Without having to use the
GUI..) IIRC you can also make it email actions (changes) - if not, it
shouldn't be that hard to add.
We use nagios to check puppet's state file for age - if it is too old,
puppet hasn't run. Between those two, afaict, we're
On Wed, May 25, 2011 at 10:40 AM, Brian Gupta wrote:
> On Wed, May 25, 2011 at 1:29 PM, Douglas Garstang
> wrote:
> > On Wed, May 25, 2011 at 10:22 AM, Brian Gupta
> > wrote:
> >>
> >> Basically the ways I know of:
> >>
> >> 1) Don't run puppet as a daemon, but run it out of cron every X mins.
>
It depends on how you use it. In our environment, we don't leave the Puppet
daemon running. We only do on-demand runs... that way changes only happen
when we push them out.
Your mileage obviously may vary, but if you're looking for tight control,
that's something to consider.
--
Nathan Clemons
ht
On Wed, May 25, 2011 at 1:29 PM, Douglas Garstang
wrote:
> On Wed, May 25, 2011 at 10:22 AM, Brian Gupta
> wrote:
>>
>> Basically the ways I know of:
>>
>> 1) Don't run puppet as a daemon, but run it out of cron every X mins.
>> 2) Setup a cronjob that checks if puppet is running and restart it i
On Wed, May 25, 2011 at 10:35 AM, Nathan Clemons wrote:
> Mcollective hides successes and only shows you failures, keeping the signal
> to noise ratio very high.
>
> If you run puppet without daemonizing, anything that causes the config to
> not be applied successfully is going to show up as an er
Mcollective hides successes and only shows you failures, keeping the signal
to noise ratio very high.
If you run puppet without daemonizing, anything that causes the config to
not be applied successfully is going to show up as an error.
--
Nathan Clemons
http://www.livemocha.com
The worlds larges
On Wed, May 25, 2011 at 10:26 AM, R.I.Pienaar wrote:
>
>
> - Original Message -
> > Basically the ways I know of:
> >
> > 1) Don't run puppet as a daemon, but run it out of cron every X mins.
> > 2) Setup a cronjob that checks if puppet is running and restart it if
> > not.
> > 3) Setup a
>-Original Message-
>From: puppet-users@googlegroups.com
>[mailto:puppet-users@googlegroups.com] On Behalf Of Brian Cully
>Sent: Wednesday, May 25, 2011 11:16 AM
>To: puppet-users@googlegroups.com
>Subject: Re: [Puppet Users] Client updates
>
>On May 25, 2011, at 1
On Wed, May 25, 2011 at 10:26 AM, Nathan Clemons wrote:
> Mcollective with mc-puppet should work if you patch it to not daemonize
> (you'll need to adjust the timeouts as well, of course). Errors running will
> bubble up to the list of nodes that failed the run.
>
>
Failed both for syntax erro
On Wed, May 25, 2011 at 10:22 AM, Brian Gupta wrote:
> Basically the ways I know of:
>
> 1) Don't run puppet as a daemon, but run it out of cron every X mins.
> 2) Setup a cronjob that checks if puppet is running and restart it if not.
> 3) Setup a nagios job that checks to see if puppet is runnin
- Original Message -
> Basically the ways I know of:
>
> 1) Don't run puppet as a daemon, but run it out of cron every X mins.
> 2) Setup a cronjob that checks if puppet is running and restart it if
> not.
> 3) Setup a nagios job that checks to see if puppet is running
> 4) Presuming you
Mcollective with mc-puppet should work if you patch it to not daemonize
(you'll need to adjust the timeouts as well, of course). Errors running will
bubble up to the list of nodes that failed the run.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
Basically the ways I know of:
1) Don't run puppet as a daemon, but run it out of cron every X mins.
2) Setup a cronjob that checks if puppet is running and restart it if not.
3) Setup a nagios job that checks to see if puppet is running
4) Presuming you are managing your puppet code in some sort o
On Wed, May 25, 2011 at 10:16 AM, Brian Cully wrote:
> On May 25, 2011, at 1:12 PM, Douglas Garstang wrote:
>
> > I probably waste quite a bit of time each week restarting the puppet
> client, and logging systems, and tailing the messages file, to see if my
> puppet changes worked. Is there a bet
On May 25, 2011, at 1:12 PM, Douglas Garstang wrote:
> I probably waste quite a bit of time each week restarting the puppet client,
> and logging systems, and tailing the messages file, to see if my puppet
> changes worked. Is there a better way? How do people normally do this?
I use mo
I probably waste quite a bit of time each week restarting the puppet client,
and logging systems, and tailing the messages file, to see if my puppet
changes worked. Is there a better way? How do people normally do this?
Sure, I can use puppetrun or mcollective to cause puppet to do a config run
on
20 matches
Mail list logo
