Bug 550873 - Unmatched entries in logwatch output for named
Summary: Unmatched entries in logwatch output for named
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: logwatch
Version: 11
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Karel Klíč
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-27 21:44 UTC by Richard Fearn
Modified: 2013-03-03 22:59 UTC (History)
4 users (show)

Fixed In Version: logwatch-7.3.6-50.fc12
Clone Of:
Environment:
Last Closed: 2010-02-24 06:03:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Example unmatched entries from /var/log/messages (431 bytes, text/plain)
2009-12-27 21:44 UTC, Richard Fearn 		no flags Details
patch to make named script ignore "no valid XX resolving..." and "not insecure resolving..." messages (794 bytes, patch)
2009-12-27 22:20 UTC, Richard Fearn 		no flags Details | Diff
patch to make named script ignore "must-be secure resolving...", "no valid XX resolving..." and "not insecure resolving..." messages (856 bytes, patch)
2010-01-04 16:09 UTC, Richard Fearn 		no flags Details | Diff
Updated patch for DNSSEC complaints. (944 bytes, patch)
2010-01-16 07:22 UTC, Frank Crawford 		no flags Details | Diff
Show Obsolete (2) View All

Description Richard Fearn 2009-12-27 21:44:02 UTC 
Created attachment 380560 [details]
Example unmatched entries from /var/log/messages

Description of problem:

The following entries aren't matched:

  "no valid DS resolving..."
  "no valid KEY resolving..."
  "no valid RRSIG resolving..."
  "not insecure resolving..."

(An example of each entry from /var/log/messages is attached.)

Version-Release number of selected component (if applicable):

logwatch-7.3.6-44.fc11.noarch
Comment 1 Richard Fearn 2009-12-27 22:20:35 UTC 
Created attachment 380562 [details]
patch to make named script ignore "no valid XX resolving..." and "not insecure resolving..." messages

I don't think these messages are important so I've patched my named script to ignore them (patch attached). This eliminates all four types of entry from my logwatch email.
Comment 2 Richard Fearn 2010-01-04 16:09:44 UTC 
Created attachment 381577 [details]
patch to make named script ignore "must-be secure resolving...", "no valid XX resolving..." and "not insecure resolving..." messages

Updated patch which also matches "must-be-secure resolving..." messages
Comment 3 Frank Crawford 2010-01-15 11:01:22 UTC 
Fairly obviously, these are related to the addition of DNSSEC to bind, and in particular 'dnssec-validation yes;' added recently.  The same issue is found in Fedora 12 with versions:

bind-9.6.1-13.P2.fc12.i686
logwatch-7.3.6-48.fc12.noarch
Comment 4 Frank Crawford 2010-01-16 07:22:06 UTC 
Created attachment 384766 [details]
Updated patch for DNSSEC complaints.

There is also an additional line warning about failed DNSSEC validation that should be either suppressed or tabulated.  At present I'm saying suppress, as such lines should be handled by the dnssec module.
Comment 5 Fedora Update System 2010-02-05 08:46:01 UTC 
logwatch-7.3.6-50.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/logwatch-7.3.6-50.fc12
Comment 6 Fedora Update System 2010-02-06 00:03:37 UTC 
logwatch-7.3.6-50.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update logwatch'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1530
Comment 7 Fedora Update System 2010-02-24 06:03:00 UTC 
logwatch-7.3.6-50.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 8 Richard Fearn 2010-04-21 21:44:11 UTC 
Also fixed from logwatch-7.3.6-50.fc13 onwards
Note You need to log in before you can comment on or make changes to this bug.