Hide Forgot
Description of problem: Just updated to RHEL 6.1, and now I get the following email every hour: /etc/cron.hourly/mcelog.cron: read: No such device Seems like this Fedora bug made its way to RHEL 6.1 ? This is going to be a pain reading every hour! Version-Release number of selected component (if applicable): kernel-2.6.32-131.0.15.el6.x86_64 mcelog-1.0pre3_20101112-0.6.el6.x86_64
(In reply to comment #0) > Description of problem: > > Just updated to RHEL 6.1, and now I get the following email every hour: > > /etc/cron.hourly/mcelog.cron: > > read: No such device > > Seems like this Fedora bug made its way to RHEL 6.1 ? This is going to be a > pain reading every hour! Ouch. I thought that only happened on startup of the mcelog process. I'll see what I can do about getting out a hotfix ... P.
I'm seeing other errors here too: After a "sudo yum update" upgrade to RHEL 6.1, mcelogd doesn't even show in chkconfig. I've verified this on three different machines. As such, it isn't started after a reboot.
(In reply to comment #2) > (In reply to comment #0) > > Description of problem: > > > > Just updated to RHEL 6.1, and now I get the following email every hour: > > > > /etc/cron.hourly/mcelog.cron: > > > > read: No such device > > > > Seems like this Fedora bug made its way to RHEL 6.1 ? This is going to be a > > pain reading every hour! > > Ouch. I thought that only happened on startup of the mcelog process. I'll see > what I can do about getting out a hotfix ... > > P. Hi - what version of mcelog are you running? I just ran an overnight test and didn't see any unusual emails.... [root@intel-s3e37-03 ~]# service mcelogd start Starting mcelog daemon [root@intel-s3e37-03 ~]# [ OK ] [root@intel-s3e37-03 ~]# [root@intel-s3e37-03 ~]# [root@intel-s3e37-03 ~]# [root@intel-s3e37-03 ~]# mail No mail for root [root@intel-s3e37-03 ~]# date Mon May 23 19:47:06 EDT 2011 Then this morning ... [root@intel-s3e37-03 ~]# mail No mail for root [root@intel-s3e37-03 ~]# rpm -q mcelog mcelog-1.0pre3_20101112-0.6.el6.x86_64 [root@intel-s3e37-03 ~]# date Tue May 24 06:31:29 EDT 2011 [root@intel-s3e37-03 ~]#
I'm running mcelog-1.0pre3_20101112-0.6.el6.x86_64 ... but the problem seems to have stopped now. The upgrade from the old to the new didn't leave the service chkconfig'ed, but once I've manually started the service, I too can't get the errors I was seeing before
(In reply to comment #5) > I'm running mcelog-1.0pre3_20101112-0.6.el6.x86_64 ... but the problem seems to > have stopped now. The upgrade from the old to the new didn't leave the service > chkconfig'ed, but once I've manually started the service, I too can't get the > errors I was seeing before Okay -- the service should have stayed on. That sounds like a bug. I'll try the upgrade path and make sure there isn't something odd going on. P.
Looking at this more, I see that every reboot I get these emails. Not sure why that matters as the script runs every hour.
I have this problem to. Looks like the same issue as Fedora was/is having: https://bugzilla.redhat.com/show_bug.cgi?id=540477 https://bugzilla.redhat.com/show_bug.cgi?id=595930
Joshua, unfortunately you will likely get this mail every reboot (for now). But the issue of mcelog not staying chkconfig'd during startup is a bug. Can you cut-and-paste the text of the message you are currently seeing with the latest mcelog? Thanks, P.
Here it is, from mcelog-1.0pre3_20101112-0.6.el6.x86_64: /etc/cron.hourly/mcelog.cron: read: No such device
(In reply to comment #10) > Here it is, from mcelog-1.0pre3_20101112-0.6.el6.x86_64: > > /etc/cron.hourly/mcelog.cron: > > read: No such device Joshua, can you send me the vendor and model of the system you're using? I cannot reproduce this internally on a variety of systems. P.
they are model SUN FIRE X2250
Joshua, this is likely fixed by BZ 699592 which does a refresh of the mcelog codebase. Upstream resolved this issue in between the refreshes and early reports from testing is that we no longer see the hourly emails. If you still see this after 6.2, please open up a new BZ. FYI, P. *** This bug has been marked as a duplicate of bug 699592 ***
Can you open up bug #699592 to public viewing so we can track this? Looks like F14 is about to get an update to fix this, so surely RHEL6.1 will be too (bug #595930)? Thanks