Description of problem: Plugin iostat_ios regularly loses track of its state. In munin-node.log the following lines are logged: [8468] Error output from iostat_ios: [8468] Magic number checking on storable file failed at ../../lib/Storable.pm (autosplit into ../../lib/auto/Storable/_retrieve.al) line 380, at /etc/munin/plugins/iostat_ios line 218 [8468] Service 'iostat_ios' exited with status 255/0. The only remedy I have found so far is deleting the state file (/var/lib/munin/plugin-state/iostat-ios.state). Version-Release number of selected component (if applicable): munin-node-1.4.4-1.fc12.noarch How reproducible: I'm not sure. It happened last night around the time logrotate was running. Looking at the munin graphs, the last time the graphing stopped was also on a Sunday around the time logrotate runs. Steps to Reproduce: 1. 2. 3. Actual results: iostat_ios stops producing data for graphing. Expected results: iostat_ios keeps producing data for graphing. Additional info: I increased the rotation in logrotate to 15 days. If this is related to logrotate, somehow, I will know more next Sunday.
I am not seeing this here on any of my test machines. ;( Is selinux enabled? Any selinux denials?
SELinux is enabled (enforcing, targeted), but I can't find any messages for last Sunday.
Sorry, I was looking at the wrong machine. The machine in question has SELinux disabled (permissive, targeted). Nevertheless, there is nothing in the logs giving any clues.
Well, I can't see how it would be logrotate. That only moves the logs. It's got to be something messing with: /var/lib/munin/plugin-state/iostat-ios.state Do you have any kind of tmpwatch or other cron job that removes things in /var/lib ? Or any other cron jobs that would affect /var/lib?
First of all, this week's cron run hasn't disturbed iostat_ios. There is only one cron job running weekly. It's raid-check (part of mdadm) and it puts some strain on sdb and sdc (about 40k blocks/s read for one hour). Sdb2 and sdc2 make up md1 in raid1 which is where /var is located. Could it be that iostat_ios is not getting hold of /var/lib/munin/plugin-state/iostat-ios.state in timely fashion due to the high load on the block devices? Munin shows me that the disk utilization and consequently i/o wait are peaking while raid-check is running.
I suppose it's possibly, but that seems pretty odd. I have a machine here that has a raid-check on it, and it hasn't seen any issues with ios state getting messed up. ;( What kernel are you running on the machine? Perhaps it's some odd issue with your hardware being overstressed by the check?
It's running kernel 2.6.32.9-70.fc12.i686. It's a rather old machine (AMD Athlon(tm) XP 1800+, 1500 MHz 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge 00:08.0 SATA controller: Initio Corporation INI-1623 PCI SATA-II Controller (rev 02 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) The RAID array is running on the built in PATA controller.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.