Bug 666498 - XNTPD script includes lots of unmatched entries
Summary: XNTPD script includes lots of unmatched entries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: logwatch
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Karel Klíč
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-31 06:25 UTC by Frank Crawford
Modified: 2013-03-03 23:02 UTC (History)
5 users (show)

Fixed In Version: logwatch-7.3.6-59.fc14
Clone Of:
Environment:
Last Closed: 2011-02-02 19:35:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Patch for various ntpd messages. (1.92 KB, patch)
2010-12-31 06:25 UTC, Frank Crawford
no flags Details | Diff
Minor pdate to previous patch. (1.92 KB, patch)
2011-01-01 02:34 UTC, Frank Crawford
no flags Details | Diff
Patch against testing version (1.64 KB, patch)
2011-01-30 11:25 UTC, Frank Crawford
no flags Details | Diff

Description Frank Crawford 2010-12-31 06:25:53 UTC
Created attachment 471253 [details]
Patch for various ntpd messages.

Description of problem:
Lots of unmatched entries occur in the XNTPD script output.

Version-Release number of selected component (if applicable):
logwatch-7.3.6-58.fc14.noarch
ntp-4.2.6p3-0.1.rc10.fc14.x86_64

How reproducible:
Messages are in all logwatch output after starting up ntpd.

Additional info:
The attached patch clears up the messages.  Most of them are "event status messages" which should be treated as debug and ignored.  The interface messages have changed, so a new match for them.  Note that logwatch is confused about interface messages in that in one spot it ignores them, and later counts them up for the report.

Also, note that this is patch is based on the output from Fedora 14's default configuration, which appears to have not enabled any informational messages.

Comment 1 Frank Crawford 2011-01-01 02:34:16 UTC
Created attachment 471304 [details]
Minor pdate to previous patch.

This patch corrects a couple of other matches to suppress a few other unknown messages.

Comment 2 Karel Klíč 2011-01-13 17:43:18 UTC
Applied to Rawhide.

Comment 3 Karel Klíč 2011-01-18 10:04:52 UTC
I assume that the following line has been commented out in the patch by accident:

#        ($ThisLine =~ /Listening on interface .* Enabled/)


Is that right? Or, why was it commented out?

Comment 4 Frank Crawford 2011-01-18 10:57:24 UTC
It is deliberate.  Later on in the script there is another if statement that tests for the same string.

From what I can tell that was only used for old versions of ntpd, and I've also modified it a little anyway, as I found a could of old messages.

Comment 5 Frank Crawford 2011-01-18 10:59:19 UTC
(In reply to comment #4)
> From what I can tell that was only used for old versions of ntpd, and I've also
> modified it a little anyway, as I found a could of old messages.

That should be "couple of old message", and the updated patch I'm referring to will be against the rawhide version when I submit it.

Comment 6 Karel Klíč 2011-01-18 15:59:16 UTC
Ok, thanks.

Comment 7 Fedora Update System 2011-01-18 16:18:36 UTC
logwatch-7.3.6-59.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/logwatch-7.3.6-59.fc14

Comment 8 Fedora Update System 2011-01-18 21:39:26 UTC
logwatch-7.3.6-59.fc14 has been pushed to the Fedora 14 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: https://admin.fedoraproject.org/updates/logwatch-7.3.6-59.fc14

Comment 9 Frank Crawford 2011-01-30 11:25:29 UTC
Created attachment 476009 [details]
Patch against testing version

Kill some more messages against:
logwatch-7.3.6-59.fc14.noarch

Comment 10 Fedora Update System 2011-02-02 19:35:14 UTC
logwatch-7.3.6-59.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.


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