they do run as a daemon
pretty much always the same 70 and they don't all run at the same
time. Many do, but not all.
On Tue, May 8, 2012 at 9:03 AM, Arnau Bria wrote:
> On Tue, 8 May 2012 05:35:34 -0700 (PDT)
> Tim Lank wrote:
>
>> how do I troubleshoot this error that
how do I troubleshoot this error that occurs for about 12% of the
puppet clients (~70 out of ~550.)
--
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 grou
you want it and
how you want it vs. hundreds or thousands every hour. I agree, this
would be way too much noise and why I didn't like the idea of tagmail.
I only want a summary once in a while, not a constant flow of them.
On Mon, Oct 4, 2010 at 9:32 PM, Daniel Pittman wrote:
>
; $lastcol) {
if (("$column[$colcounter]" eq "\\") &&
("$column[$colcounter+1]" eq "\"")) {
$colcounter++;
}
else {
print RECONSTRUCTED "$column[$colcounter]";
$colcounter++;
}
}
print RECONSTRUCTED
This is not working (no username/password prompt when directing my
browser to the site). How do I troubleshoot this (where are the
access logs, etc...?)
On Thu, Sep 30, 2010 at 2:00 PM, Igal Koshevoy wrote:
> On Thu, Sep 30, 2010 at 3:58 AM, Tim Lank wrote:
>> puppet-users:
>&
puppet-users:
I've got puppet-dashboard 1.0.3-3 setup using the rpm from here:
http://yum.puppetlabs.com/base/
Everything seems to work fine using the instructions from here:
http://github.com/reductivelabs/puppet-dashboard
I'm trying to setup basic security with the .htaccess file described
in
default
- class
- main
- returns
- notice
time: 2010-09-24 15:23:21.563504 -04:00
version: 1285356077
On Fri, Sep 24, 2010 at 2:44 PM, Tim Lank wrote:
> debugging your exec's for one. The exec may return something that is
> functionall
hings yet so I may not be able to provide a good solid set of
use cases for you.
On Fri, Sep 24, 2010 at 2:34 PM, Nigel Kersten wrote:
> On Fri, Sep 24, 2010 at 11:29 AM, Tim Lank wrote:
> > It would be great to have it configurable, so that it could be off by
> > default for th
be a very desirable thing.
Please provide the patch# you are referring to for the on_failure stderr.
On Fri, Sep 24, 2010 at 2:10 PM, Nigel Kersten wrote:
> On Fri, Sep 24, 2010 at 10:08 AM, Tim Lank wrote:
> > Thanks. Can you elaborate on the puppet's reports? All I see
- notice
time: 2010-09-24 13:53:17.465847 -04:00
version: 1285350797
I see that the source command string is there, but the stdout (and err) of
the ps command does not appear in the yaml. Is there a way to turn this on
so it ends up in here?
On Fri, Sep 24, 2010 at 1:08 PM, Tim Lank wrote:
ther in a coherent and
readable manner for each individual client.
On Fri, Sep 24, 2010 at 12:55 PM, Patrick wrote:
>
> On Sep 24, 2010, at 3:52 AM, Tim Lank wrote:
>
> puppet-users:
>
> I'm trying to find a way to obtain the stdout (and stderr) output from
> individual pupp
puppet-users:
I'm trying to find a way to obtain the stdout (and stderr) output from
individual puppet client configuration runs. I'd like a central storage of
this information if possible.
In short, I'd like to know what the client exactly did with the
configuration that it was sent. Ideally
12 matches
Mail list logo
