Issue #2739 has been updated by Jeff McCune.
Also, I don't know if you'd like this as another ticket, but I have: <pre> [puppetmasterd] reports = store,log </pre> In the server configuration, and I see nothing coming through into syslog from the report processor. Am I correct in my expectation to see some reporting related messages in the following syslog output: <pre> Oct 20 18:31:47 homer puppetmasterd[8921]: [ID 702911 daemon.notice] Caught TERM; calling stop Oct 20 18:31:56 homer puppetmasterd[9618]: [ID 702911 daemon.notice] Reopening log files Oct 20 18:31:56 homer puppetmasterd[9618]: [ID 702911 daemon.notice] Starting Puppet server version 0.25.1 Oct 20 18:32:07 homer puppetmasterd[9618]: [ID 702911 daemon.warning] (Scope(Class[package::zsh])) operatingsystem=Solaris kernelrelease=5.11 message='not configured to manage zsh' Oct 20 18:32:07 homer puppetmasterd[9618]: [ID 702911 daemon.warning] (Scope(Class[security::solaris])) message='services were not configured. unknown operatingsystemrelease' operatingsystemrelease=5.11 Oct 20 18:32:08 homer puppetmasterd[9618]: [ID 702911 daemon.notice] Compiled catalog for homer.asp.ntst.private in 0.90 seconds Oct 20 18:32:14 homer puppetmasterd[9618]: [ID 702911 daemon.notice] DEPRECATION NOTICE: Files found in modules without specifying 'modules' in file path will be deprecated in the next major release. Please fix module 'py-ntst' when no 0.24.x clients are present Oct 20 18:32:14 homer puppetmasterd[9618]: [ID 702911 daemon.notice] DEPRECATION NOTICE: Files found in modules without specifying 'modules' in file path will be deprecated in the next major release. Please fix module 'ntst-puppet' when no 0.24.x clients are present </pre> The client is successfully uploading the report, and I see the following entry in the yaml: <pre> --- !ruby/object:Puppet::Transaction::Report host: homer.asp.ntst.private logs: - !ruby/object:Puppet::Util::Log level: :info message: Applying configuration version '1256077927' source: Puppet tags: - info time: 2009-10-20 18:32:12.606113 -04:00 </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 -~----------~----~----~----~------~----~------~--~---
