Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685832 - named log has changed but logwatch doesn't reflect this
Summary: named log has changed but logwatch doesn't reflect this
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: logwatch
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-06 08:36 UTC by Michal Žejdl
Modified: 2019-03-06 08:56 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
patch which removes hex matching (deleted)
2019-03-06 08:36 UTC, Michal Žejdl
no flags Details | Diff

Description Michal Žejdl 2019-03-06 08:36:09 UTC
Created attachment 1541242 [details]
patch which removes hex matching

Description of problem:

7.6 introduced bind with a different logging

named[26409]: validating @0x7fd2ec06bd50: szn-broken-dnssec.cz DNSKEY: no valid signature found (DS)
yum[26684]: Updated: 32:bind-9.9.4-72.el7.x86_64
named[27023]: validating szn-broken-dnssec.cz/DNSKEY: no valid signature found (DS)

current logwatch is using match of \@0x[[:xdigit:]]+: to ignore such records, so it stopped working



Version-Release number of selected component (if applicable):
logwatch-7.4.0-35.20130522svn140.el7_5.noarch


How reproducible:
always

Steps to Reproduce:
just run named as a recursive resolver and enjoy very long logwatch reports

Expected results:
lines ignored as in 7.5


Note You need to log in before you can comment on or make changes to this bug.