Description of problem: mcelog.cron is sending this warning at each hourly run: /etc/cron.hourly/mcelog.cron: mcelog: warning: 18446744073709551600 bytes ignored in each record mcelog: consider an update Version-Release number of selected component (if applicable): mcelog-0.9pre1-0.1.fc12.x86_64
This was reported in RHEL5 Bug 501512, But I guess that fix wasn't carried over to F12...
I am also seeing this on Fedora 11 since last night's update. mcelog-0.7-4.fc11.x86_64
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
This problem was addressed some time ago. Please try a newer version of Fedora. This bug will not be addressed in an older version of Fedora because it only generates a harmless error.
There are still problems with it. On a new Fedora 14 box I get an email every hour with: /etc/cron.hourly/mcelog.cron: read: No such device
On Fedora 14, I'm getting occasionally the emails that Matt described. Oddly, when I run "/usr/sbin/mcelog --ignorenodev --filter" by hand, it doesn't give any errors. I think that perhaps I only get the error message the first time /etc/cron.hourly/mcelog.cron runs after booting, but I would have to pay more attention over time to know for sure.
It won't give you an error because it only happens the very first time after boot. There's a bug in the upstream kernel. I've reported it to Andi and he's kludged upstream mcelog for the moment. Today, I'm going to open an upstream BZ and remind him that the kernel actually needs fixing without a hack.
Bitten by this bug too. From: Cron Daemon <root> To: root Subject: Cron <root@kovinek> run-parts /etc/cron.hourly /etc/cron.hourly/mcelog.cron: read: No such device $ rpm -qf /etc/cron.hourly/mcelog.cron mcelog-1.0-0.1.pre3.fc14.x86_64 Jon, do you have the upstream kernel bug number handy?
I'm still getting regular emails. Has there been any progress on the upstream bug? Thanks.
I'll give this some more love.
*** Bug 676799 has been marked as a duplicate of this bug. ***
I am also still getting regular emails. mcelog-0.9pre1-0.1.fc13.x86_64 kernel-2.6.35.12-88.fc14.x86_64
Fedora 15 has resolved this issue for me.
*** Bug 718448 has been marked as a duplicate of this bug. ***
I submitted 718448 as my search for prior bug didn't consider "hourly" (my bad, apologies). Now that Michael has flagged it as a dupe of this bug and I see 1) the F14 messages are identical to my messages and 2) it has been noted that F15 seems to have it resolved. I'd like to ask if 1) is it fixed in F15 or just happens to be working (some other change indirectly fixed it) and 2) if it is a bug fix, can it be ported to F14? Thanks, Paul
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
(In reply to comment #15) > I submitted 718448 as my search for prior bug didn't consider "hourly" (my bad, > apologies). > > Now that Michael has flagged it as a dupe of this bug and I see 1) the F14 > messages are identical to my messages and 2) it has been noted that F15 seems > to have it resolved. > > I'd like to ask if 1) is it fixed in F15 or just happens to be working (some > other change indirectly fixed it) and 2) if it is a bug fix, can it be ported > to F14? > Paul, I've taken ownership of the mcelog package in Fedora. To answer your question: F14 is the same version that is in F15. Both should be fixed. P.
Prarit: Thanks for answering my question Paul
(In reply to comment #18) > Prarit: > > Thanks for answering my question > > Paul Just an FYI -- new packages were pushed for F15 and F16 this morning. mcelog-1.0-0.3.6e4e2a00.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mcelog-1.0-0.3.6e4e2a00.fc15 P.