Bug 919311 - running /etc/cron.daily/0logwatch spins up drive
Summary: running /etc/cron.daily/0logwatch spins up drive
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: logwatch
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 454582
TreeView+ depends on / blocked
 
Reported: 2013-03-08 03:09 UTC by Peter Backes
Modified: 2013-06-25 07:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-25 07:15:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Peter Backes 2013-03-08 03:09:41 UTC 
Description of problem:
since about a week or two, the automatic (or a manual) run of /etc/cron.daily/0logwatch spins up disks that have no mounted partitions and that have been put to sleep with hdparm -y

Version-Release number of selected component (if applicable):
logwatch-7.4.0-23.20130102svn127.fc18.noarch

How reproducible:
always

Steps to Reproduce:
1. add disk
2. put disk to sleep with eg hdparm -y /dev/sdb
3. run /etc/cron.daily/0logwatch
  
Actual results:
disk spins up

Expected results:
disk status unaffected
Comment 1 Peter Backes 2013-03-09 06:07:25 UTC 
apparently caused by mdadm --examine --scan being invoked in /usr/share/logwatch/scripts/services/mdadm
Comment 2 Peter Backes 2013-03-09 06:18:29 UTC 
Workaround: yum downgrade logwatch

It currently downgrades to 7.4.0-18.20120619svn110.fc18.noarch which has no /usr/share/logwatch/scripts/services/mdadm
Comment 3 Peter Backes 2013-03-09 06:42:06 UTC 
Filed upstream bug: https://sourceforge.net/tracker/?func=detail&aid=3607400&group_id=312875&atid=1316824
Comment 4 Peter Backes 2013-06-21 19:17:46 UTC 
Better workaround: Append the following line to /etc/logwatch/conf/logwatch.conf

Service = "-mdadm"
Comment 5 Jan Synacek 2013-06-25 07:15:25 UTC 
(In reply to Peter Backes from comment #4)
> Better workaround: Append the following line to
> /etc/logwatch/conf/logwatch.conf
> 
> Service = "-mdadm"

Not a workaround, it's just a matter of configuration. Closing this as NOTABUG.
Note You need to log in before you can comment on or make changes to this bug.