Bug 158155 - Kernel log parsing fails
Kernel log parsing fails
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-19 03:41 EDT by Adam Huffman
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-27 07:23:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Huffman 2005-05-19 03:41:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Fedora/1.0.4-2 Firefox/1.0.4

Description of problem:
The kernel parsing in logwatch doesn't seem to be working:

--------------------- Kernel Begin ------------------------

 egrep: module: No such file or directory

 ---------------------- Kernel End -------------------------

egrep is installed in /bin

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

How reproducible:
Always

Steps to Reproduce:
1. Logwatch runs via cron
2. Read logwatch mail
3.
  

Actual Results:  Kernel log parsing doesn't work

Expected Results:  Kernel log parsing should work

Additional info:
Comment 1 Maxim Britov 2005-05-23 04:51:55 EDT
I found trouble with:
/etc/log.d/conf/services/kernel.conf
contains: *Remove = locate module

For me I fix it by change /etc/log.d/scripts/shared/remove:
from: system("/bin/egrep -vi @ARGV");
to: system("/bin/egrep -vi \"@ARGV\"");
Comment 2 Paul Howarth 2005-05-26 08:29:25 EDT
The change suggested in Comment #1 is now in upstream CVS (see
http://www2.logwatch.org:81/tabs/anoncvs/ for how to access this).
Comment 3 Ivana Varekova 2005-06-27 07:22:18 EDT
This bug is fixed in the last version (logwatch-6.1.2-1).

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