Bug 578806 - does not properly parse temperature changes reported by smartd
Summary: does not properly parse temperature changes reported by smartd
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: logwatch
Version: 5.5
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: David Kutálek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-01 12:33 UTC by Hannes Schulz
Modified: 2013-04-12 20:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-29 11:16:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
This patch fixes the problem for me. (862 bytes, patch)
2010-04-01 12:41 UTC, Hannes Schulz
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:1217 0 normal SHIPPED_LIVE logwatch bug fix update 2012-08-29 15:15:59 UTC

Description Hannes Schulz 2010-04-01 12:33:37 UTC
Description of problem:
logwatch does not properly parse temperature changes reported by smartd.

Version-Release number of selected component (if applicable):
logwatch-7.3-8.el5
smartmontools-5.38-2.el5

How reproducible:


Steps to Reproduce:
1. Start smartd when disk has been idle for some time (i.e. is cool).
2. Heavily use disk.
3. check for lines like "smartd[3785]: Device: /dev/sg2, Temperature changed +2 Celsius to 34 Celsius (Min/Max 32/34!) " in /var/log/messages.
4. run "logwatch --range Today --print"


Actual results:
Logwatch report contains the lines:

 **Unmatched Entries**
 Device: /dev/sg2, Temperature changed +2 Celsius to 34 Celsius (Min/Max 32/34!)


Expected results:
Temperature change properly incorporated in section "Temperature Changes" 


Additional info:
This only occurs for positive temperatur changes.

Comment 1 Hannes Schulz 2010-04-01 12:41:09 UTC
Created attachment 403966 [details]
This patch fixes the problem for me.

One-liner to properly parse temperature changes which contain a plus sign.

Comment 2 Karel Klíč 2010-04-12 11:46:52 UTC
The upstream fixed the regular expression in the same way.

This is a candidate for fastrack.

Comment 4 RHEL Program Management 2011-01-11 20:29:34 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2011-01-11 23:02:15 UTC
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Comment 6 RHEL Program Management 2011-05-31 13:22:56 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2011-09-23 00:12:56 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 12 errata-xmlrpc 2012-08-29 11:16:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-1217.html


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