Issue #19640 has been reported by Stefan Heijmans.

----------------------------------------
Feature #19640: Puppet agent "Reopening logfiles" message
https://projects.puppetlabs.com/issues/19640

Author: Stefan Heijmans
Status: Unreviewed
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet version: 3.1.0
Keywords: 
Branch: 


After upgrading Puppet (opensource) 2.7.20 to 3.1.0, we notice that the puppet 
agent 
messsage 'Reopening log files' is not written any more in /var/log/messages 
when we
run it with the MCollective puppet agent. It does show up when running puppet 
agent as
a service but we don't use this option.

Puppet 3.1.0 run with MCollective puppet agent (runonce/runall)
<pre>
Mar  7 10:55:16 [server] puppet-agent[24958]: Finished catalog run in 11.90 
seconds
</pre>
Puppet 2.7.20 run with MCollective puppet agent (runonce/runall)
<pre>
Mar  7 12:04:09 [server] puppet-agent[25918]: Reopening log files
Mar  7 12:04:31 [server] puppet-agent[25918]: Finished catalog run in 10.58 
seconds
</pre>

Puppet 3.1.0 running as a service.
<pre>
Mar  7 10:44:07 [server] puppet-agent[23439]: Starting Puppet client version 
3.1.0
Mar  7 10:44:07 [server] puppet-agent[23439]: Reopening log files
Mar  7 10:44:26 [server] puppet-agent[23443]: Finished catalog run in 14.58 
seconds
</pre>


Would it be possible to bring this back as it is handy to see when the puppet 
agent starts and stops in /var/log/messages.



-- 
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://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to