Bug 809314

Summary: unmatched entries in secure logwatch part
Product: [Fedora] Fedora Reporter: Ivana Varekova <varekova>
Component: logwatchAssignee: Jan Synacek <jsynacek>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: frank, jsynacek, kklic, richardfearn, varekova
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: logwatch-7.4.0-12.20120229svn100.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-19 06:58:53 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:
Embargoed:

Description Ivana Varekova 2012-04-03 05:15:52 UTC
Description of problem:
I found bunch of unmatched entries in logwatch log. They should be properly
parsed.

Version-Release number of selected component (if applicable):
logwatch-7.4.0-6.20110328svn50.fc16.noarch

How reproducible:
always
  
Actual results:
 **Unmatched Entries**
    groupmod: group changed in /etc/group (group nfsnobody/65534): 1 Time(s)
    passwd: gkr-pam: couldn't update the login keyring password: no old password was entered: 1 Time(s)
    pkexec: pam_systemd(polkit-1:session): Failed to create session: Invalid argument: 1 Time(s)
    pkexec: varekova: Executing command [USER=root] [TTY=unknown] [CWD=/home/varekova] [COMMAND=/usr/sbin/pk-device-rebind /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0]: 1 Time(s)
    su: pam_systemd(su-l:session): Failed to parse message: Message has only 3 arguments, but more were expected: 2 Time(s)
    su: pam_systemd(su:session): Failed to parse message: Message has only 3 arguments, but more were expected: 1 Time(s)
    userdel: delete user 'varekova': 1 Time(s)
    userdel: removed group 'varekova' owned by 'varekova': 1 Time(s)

Comment 1 Jan Synacek 2012-04-25 07:36:26 UTC
Could you please check if these are gone with the latest version? http://koji.fedoraproject.org/koji/taskinfo?taskID=4021262

Thank you!

Comment 2 Fedora Update System 2012-05-04 08:04:01 UTC
logwatch-7.4.0-11.20120229svn100.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/logwatch-7.4.0-11.20120229svn100.fc17

Comment 3 Fedora Update System 2012-05-09 08:26:27 UTC
logwatch-7.4.0-12.20120229svn100.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/logwatch-7.4.0-12.20120229svn100.fc16

Comment 4 Fedora Update System 2012-05-10 14:16:26 UTC
Package logwatch-7.4.0-12.20120229svn100.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing logwatch-7.4.0-12.20120229svn100.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-7541/logwatch-7.4.0-12.20120229svn100.fc16
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-05-19 06:58:53 UTC
logwatch-7.4.0-12.20120229svn100.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2012-05-26 07:03:24 UTC
logwatch-7.4.0-11.20120229svn100.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.