Hello all,
I've recently been looking into various methods for configuring meaningful
logging from my puppet 3.6 master/agent nodes. I've typically gone the
route of grep'ing through syslog on both master/agents and I'd like
something a little more robust and user friendly for other who may
On 8/26/14 10:34 AM, Mike Reed wrote:
Hello all,
I've recently been looking into various methods for configuring
meaningful logging from my puppet 3.6 master/agent nodes. I've
typically gone the route of grep'ing through syslog on both
master/agents and I'd like something a little more robust
kOn Tue, Aug 26, 2014 at 10:34 AM, Mike Reed mjohn.r...@gmail.com wrote:
I suppose I have two questions:
1. Is there a simple way to push messages to a file other than
/var/log/syslog on an Ubuntu machine?
I think the rsyslog Ramin mentioned is a good way to filter.
2. Is there a
Hey Will and Ramin,
Thank you both for taking the time to explain your configurations.
I suspect I'll roll with the central logging option via rsyslog/syslog and
go from there. Splunk sounds like a great tool to use for parsing as well
as PuppetDB for more advanced visualization features.
Here it is in almost all it's glory (comments removed and server domain
changed...):
[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = /etc/puppet/ssl
runinetrval = 600
pluginsync=true
[agent]
classfile = /classes.txt
localconfig = /localconfig
I think this line
logdest = /var/log/puppet/puppet.log
is the same as starting the daemon with --logdest
I believe you are logging to /var/log/puppet/puppet.log
Remove that line and I think it will log to syslog
On Sat, May 5, 2012 at 8:04 AM, John Kennedy skeb...@gmail.com wrote:
Here it
On Thu, May 3, 2012 at 8:07 AM, Bernd Adamowicz bernd.adamow...@esailors.de
wrote:
You should try
** **
debug = true
verbose = true
** **
in your agent and/or master configurations. Some more hints on monitoring
and on Nagios/Icinga checks
Is your daemon started with a different --logdest=/path/file specified?
On Fri, May 4, 2012 at 7:45 AM, John Kennedy skeb...@gmail.com wrote:
On Thu, May 3, 2012 at 8:07 AM, Bernd Adamowicz
bernd.adamow...@esailors.de wrote:
You should try
** **
debug = true
Nope...
Thanks,
John
John Kennedy
On Fri, May 4, 2012 at 8:08 PM, Michael Baydoun indymicha...@gmail.comwrote:
Is your daemon started with a different --logdest=/path/file specified?
On Fri, May 4, 2012 at 7:45 AM, John Kennedy skeb...@gmail.com wrote:
On Thu, May 3, 2012 at 8:07 AM,
Can you post your full puppet.conf? Redact anything sensitive.
On Fri, May 4, 2012 at 9:27 PM, John Kennedy skeb...@gmail.com wrote:
Nope...
Thanks,
John
John Kennedy
On Fri, May 4, 2012 at 8:08 PM, Michael Baydoun indymicha...@gmail.comwrote:
Is your daemon started with a different
@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von John Kennedy
Gesendet: Mittwoch, 2. Mai 2012 18:49
An: puppet-users@googlegroups.com
Betreff: [Puppet Users] Puppet logging
Hello all,
I am trying to write a script that will check logs for puppet errors to use in
a nagios check. I am
Hello all,
I am trying to write a script that will check logs for puppet errors to use
in a nagios check. I am checking /var/log/messages (RHEL6) but when puppet
runs on its 30 minute interval, nothing gets written to messages. I have
also looked at /var/log/puppet/puppet.log but that does not
Do you have reports=log in your puppet.conf?
On Wed, May 2, 2012 at 12:49 PM, John Kennedy skeb...@gmail.com wrote:
Hello all,
I am trying to write a script that will check logs for puppet errors to
use in a nagios check. I am checking /var/log/messages (RHEL6) but when
puppet runs on its 30
I am running puppet-0.24.8 with passenger-2.2.2, apache-2.2.3 on RHEL
5.2. I have two nodes, one x86_64 and one ppc64, that have the client
running and they are checking in regularly as expected. I have a
minimal site.pp file which defines the owner, group and permissions on
several files.
14 matches
Mail list logo
