Issue #2739 has been updated by Jeff McCune.

Luke Kanies wrote:
> Are you sure you're actually logging local4 somewhere?  When I've seen this 
> happen, it's usually because I'm not writing that facility anywhere.

Yes.  puppetd on the same host is successfully logging to local4, just not 
puppetmasterd

<pre>
[jmcc...@homer]/var/scratch/jmccune/ntst-puppet/runtime/puppet-0.25.1rc2/lib/puppet/reports%
 tail /var/log/local4.log
Oct 20 17:13:08 homer puppetd[6680]: [ID 702911 local4.info] Caching catalog 
for homer.asp.ntst.private
Oct 20 17:13:11 homer puppetd[6680]: [ID 702911 local4.info] Applying 
configuration version '1256073186'
Oct 20 17:13:11 homer puppetd[6680]: [ID 702911 local4.notice] 
(//syslog::common/File[/etc/syslog.conf]/checksum) checksum changed 
'{md5}5c1f4fdd8a4344cb1b4194f425a2b7bd' to 
'{md5}c575820be326a6ba6f7b5bc6a97ea3b4'
Oct 20 17:13:11 homer puppetd[6680]: [ID 702911 local4.info] 
(Filebucket[/var/lib/puppet/clientbucket]) Adding 
/etc/syslog.conf(c575820be326a6ba6f7b5bc6a97ea3b4)
Oct 20 17:13:11 homer puppetd[6680]: [ID 702911 local4.info] 
(//syslog::common/File[/etc/syslog.conf]) Filebucketed /etc/syslog.conf to 
puppet with sum c575820be326a6ba6f7b5bc6a97ea3b4
Oct 20 17:13:11 homer puppetd[6680]: [ID 702911 local4.notice] 
(//syslog::common/File[/etc/syslog.conf]/content) content changed 
'{md5}c575820be326a6ba6f7b5bc6a97ea3b4' to 'unknown checksum'
Oct 20 17:13:11 homer puppetd[6680]: [ID 702911 local4.info] 
(//syslog::common/File[/etc/syslog.conf]) Scheduling refresh of Service[syslog]
Oct 20 17:13:11 homer last message repeated 1 time
Oct 20 17:13:14 homer puppetd[6680]: [ID 702911 local4.notice] 
(//syslog::common/Service[syslog]) Triggering 'refresh' from 2 dependencies
Oct 20 17:13:15 homer puppetd[6680]: [ID 702911 local4.notice] Finished catalog 
run in 5.03 seconds
</pre>
----------------------------------------
Bug #2739: puppetmasterd 0.25.1rc2 is not logging anywhere
http://projects.reductivelabs.com/issues/2739

Author: Jeff McCune
Status: Accepted
Priority: Urgent
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to