Issue #2739 has been updated by Jeff McCune.
Markus Roberts wrote:
> If you set debug or verbose logging goes to the console. This is apparently
> by design (at least, it's the documented behavior). This seems plausible
> since you had a full log from the console.
>
> Other than that, I've had no luck reproducing this; logging in general seems
> to be working so far as I can tell.
I'm not running with verbose logging or debug logging. I'm simply running with
@--logdest /var/lib/puppet/log/foo.log@ and noting that the log file is NOT
created, and nothing is then logged to syslog.
I'm running strictly with with --logdest :
<pre>
pup...@homer:~/puppet/server/init$ bash -x ./ntst-puppetmasterd-0.25.1rc2
--logdest /var/lib/puppet/log/foo.log
+ [[ puppet != puppet ]]
+ FACTER_NTST_PUPPET_VERSION=puppet-0.25.1rc2
+ FACTER_NTST_FACTER_VERSION=facter-1.5.7
+
PATH=/var/lib/puppet/puppet-0.25.1rc2/server/runtime/puppet-0.25.1rc2/sbin:/var/lib/puppet/puppet-0.25.1rc2/server/runtime/puppet-0.25.1rc2/bin:/var/lib/puppet/bin:/opt/csw/bin:/usr/bin
+ export PATH
+
RUBYLIB=/var/lib/puppet/puppet-0.25.1rc2/server/runtime/puppet-0.25.1rc2/lib:/var/lib/puppet/puppet-0.25.1rc2/server/runtime/facter-1.5.7/lib:
+ export RUBYLIB
+ puppetmasterd --confdir
/var/lib/puppet/puppet-0.25.1rc2/server/etc/puppet-0.25.1rc2 --logdest
/var/lib/puppet/log/foo.log
</pre>
Note:
<pre>
pup...@homer:~/puppet/server/init$ ls -l /var/lib/puppet/log/foo.log
/var/lib/puppet/log/foo.log: No such file or directory
</pre>
Here's my current configuration:
<pre>
[main]
# Where Puppet stores dynamic and growing data.
vardir = /var/lib/puppet/puppet-0.25.1rc2
# Where SSL certificates are kept.
ssldir = /var/lib/puppet/ssl
# JJM 2009-08-17 Environments
# Each environment will be a git clone on a specific branch.
[development]
manifest=$vardir/environment/development/manifests/site.pp
modulepath=$vardir/environment/development/modules
[testing]
manifest=$vardir/environment/testing/manifests/site.pp
modulepath=$vardir/environment/testing/modules
[production]
manifest=$vardir/environment/production/manifests/site.pp
modulepath=$vardir/environment/production/modules
[jmccune]
manifest=$vardir/environment/jmccune/manifests/site.pp
modulepath=$vardir/environment/jmccune/modules
[nliu]
manifest=$vardir/environment/nliu/manifests/site.pp
modulepath=$vardir/environment/nliu/modules
[puppetd]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
server = puppet.service.asp.ntst.private
# Environments will override some of these paths
[puppetmasterd]
manifestdir=$vardir/manifests
modulepath=$vardir/modules
certname = puppet.service.asp.ntst.private
templatedir=$vardir/templates
rundir = $vardir/run
pidfile = $vardir/run/puppetmasterd.pid
masterport = 8140
# Reports
reports = store,log
reportdir = /var/lib/puppet/reports
</pre>
----------------------------------------
Bug #2739: puppetmasterd 0.25.1rc2 is not logging anywhere
http://projects.reductivelabs.com/issues/2739
Author: Jeff McCune
Status: Accepted
Priority: Normal
Assigned to: Markus Roberts
Category: server
Target version: 0.25.1
Affected version: 0.25.1rc2
Keywords: logging
Branch:
Testing puppet 0.25.1rc2, I cannot convince the puppetmasterd process to log
anywhere.
Running @ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-solaris2.11]@
Messages are not being logged to syslog or to the
@/var/lib/puppet/log/puppetmasterd.log@ file when puppetmasterd is started with
@--logdest=/var/lib/puppet/log/puppetmasterd.log@
This is a critically important bug to me for auditing purposes.
Configuration file:
<pre>
[main]
# What syslog facility to use when logging to
# syslog. Syslog has a fixed list of valid facilities, and you must
# choose one of those; you cannot just make one up.
# The default value is 'daemon'.
syslogfacility = local4
# Where Puppet stores dynamic and growing data.
# The default value is '/var/puppet'.
vardir = /var/lib/puppet/puppet-0.25.1rc2
# The Puppet log directory.
# The default value is '$vardir/log'.
# logdir =
# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
# rundir =
# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = /var/lib/puppet/ssl
# JJM 2009-08-17 Environments
# Each environment will be a git clone on a specific branch.
[development]
manifest=$vardir/environment/development/manifests/site.pp
modulepath=$vardir/environment/development/modules
[testing]
manifest=$vardir/environment/testing/manifests/site.pp
modulepath=$vardir/environment/testing/modules
[production]
manifest=$vardir/environment/production/manifests/site.pp
modulepath=$vardir/environment/production/modules
[jmccune]
manifest=$vardir/environment/jmccune/manifests/site.pp
modulepath=$vardir/environment/jmccune/modules
[nliu]
manifest=$vardir/environment/nliu/manifests/site.pp
modulepath=$vardir/environment/nliu/modules
[puppetd]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is '$confdir/classes.txt'.
classfile = $vardir/classes.txt
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
server = puppet.service.asp.ntst.private
# Environments will override these paths
[puppetmasterd]
certname = puppet.service.asp.ntst.private
reportdir = /var/lib/puppet/reports
templatedir=$vardir/templates
manifestdir=$vardir/manifests
modulepath=$vardir/modules
rundir = $vardir/run
pidfile = $vardir/run/puppetmasterd.pid
masterport = 8140
# How to determine the configuration version. By default, it will be the
# time that the configuration is parsed, but you can provide a shell script
to override how the
# version is determined. The output of this script will be added to every
log message in the
# reports, allowing you to correlate changes on your hosts to the source
version on the server.
# The default value is ''.
# config_version =
</pre>
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
