Bug 1299181

Summary: logwatch puppet-agent unknown entries
Product: Red Hat Enterprise Linux 7 Reporter: Vadym Chepkov <vchepkov>
Component: logwatchAssignee: Jan Synacek <jsynacek>
Status: CLOSED ERRATA QA Contact: Martin Frodl <mfrodl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: isenfeld, mfrodl, vchepkov
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: logwatch-7.4.0-29.20130522svn140.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 03:30:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1289485, 1313485    

Description Vadym Chepkov 2016-01-17 03:51:10 UTC
logwatch puppet service doesn't recognize puppet-agent log entries:

# grep puppet-agent /var/log/messages|tail -5
Jan 17 01:22:42 holder puppet-agent[12914]: Applied catalog in 7.14 seconds
Jan 17 01:52:39 holder puppet-agent[13530]: Applied catalog in 5.65 seconds
Jan 17 02:22:41 holder puppet-agent[14149]: Applied catalog in 6.51 seconds
Jan 17 02:52:39 holder puppet-agent[14765]: Applied catalog in 5.48 seconds
Jan 17 03:22:40 holder puppet-agent[15835]: Applied catalog in 5.42 seconds

# logwatch --service puppet:

--------------------- Puppet Begin ------------------------ 

 **Unmatched Entries**
     Applied catalog in 5.71 seconds: 1 Time(s)
     Applied catalog in 5.49 seconds: 2 Time(s)
     Applied catalog in 5.63 seconds: 1 Time(s)
     Applied catalog in 5.44 seconds: 1 Time(s)
     Applied catalog in 6.82 seconds: 1 Time(s)


logwatch-7.4.0-28.20130522svn140.el7.noarch

Comment 3 Jan Synacek 2016-03-16 13:59:49 UTC
What puppet version do you use?

Comment 4 Vadym Chepkov 2016-03-16 17:38:16 UTC
puppet-agent-1.3.5-1.el7.x86_64

Comment 9 errata-xmlrpc 2016-11-04 03:30:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2312.html