mcelog: warning: record length longer than expected. Consider update

cool999

Active Member
Jan 18, 2010
31
0
56
I am getting these mails, please help me what to do..

/etc/cron.hourly/mcelog.cron:

mcelog: warning: record length longer than expected. Consider update.
 

stugster

Well-Known Member
Apr 16, 2002
75
0
306
Edinburgh, UK
cPanel Access Level
Root Administrator
A new server set up this week within our organisation is showing signs of this issue as well.

Linux ***.********.co.uk 2.6.32.2-xxxx-std-ipv4-64 #2 SMP Mon Jan 11 07:46:51 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

------------------
/etc/cron.hourly/mcelog.cron:

mcelog: warning: record length longer than expected. Consider update.
 

AdamDresch

Well-Known Member
Jun 22, 2006
80
0
156
Getting the same problem here.

etc/cron.hourly/mcelog.cron:

mcelog: warning: record length longer than expected. Consider update.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
Here's a discussion of the bug on RHEL site:

https://bugzilla.redhat.com/show_bug.cgi?id=625761

Your kernel doesn't appear to be a standardized RHEL or CentOS kernel, so I have no way to know what to suggest here for which mcelog to use. As such, you can try to downgrade mcelog or upgrade mcelog to see if either works to resolve the errors, since the current version of mcelog that you are using isn't compatible with whatever kernel that happens to be.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
You'd have to remove the rpm and then find a lower version of the rpm:

Code:
rpm -qa | grep mcelog
rpm -e mcelogrpmname.rpm
wget http://somepathtothelowerversionrpm
rpm -ivh mcelogolder.rpm
You'd replace the mcelogrpmname.rpm with the name you obtain from running the "rpm -qa | grep mcelog" command, you'd replace http://somepathtothelowerversionrpm with the rpm you find online that matches your CentOS distribution and architecture, and you'd replace mcelogolder.rpm with the name of that older rpm you'd placed onto your machine.

If you want to paste the output for the existing rpm on your machine so we know which one it happens to be, it's possible I could try to track down the rpm for you if you aren't able to locate the older rpm which bugzilla mentions as well in that link I previously provided.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
Since you are running 0.9pre-1.30 version, it might be that you need the 0.9pre-1.29 version instead. It's hard to know because of your custom kernel that isn't a stock CentOS or RedHat Enterprise one. As such, if 0.9pre-1.29 will work, here's how to uninstall the current version and install the older one:

Code:
rpm -e mcelog-0.9pre-1.30.el5
wget http://mirrors.gigenet.com/centos/5.6/os/x86_64/CentOS/mcelog-0.9pre-1.29.el5.x86_64.rpm
rpm -ivh mcelog-0.9pre-1.29.el5.x86_64.rpm
If this does not work, you might have to search online to find a newer or even older rpm for mcelog. Alternatively, you could ask your provider to boot you into a non-customized CentOS or RedHat Enterprise kernel.
 

cPanelTristan

Quality Assurance Analyst
Staff member
Oct 2, 2010
7,607
40
248
somewhere over the rainbow
cPanel Access Level
Root Administrator
This would be a RedHat and CentOS issue which is vendor specific for the OS. Specifically, the log would be impacted by a customized kernel. The RedHat bug report indicates that this falls with the OS - https://bugzilla.redhat.com/show_bug.cgi?id=625761

This means that RedHat or CentOS would need to resolve the issue on their side. You may wish to contact them for further assistance.