Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
$ sudo tail /var/log/messages
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)
Jan 30 13:47:58 www kernel: EDAC MC0: CE row 3, channel 0, label "": Corrected error (Socket=0 channel=1 dimm=1)

As you can see, this is logging at a phenomenal rate, I don't know about EDAC though. From what I understand this is indicating a faulty stick of RAM possibly, does this seem likely?

I understand this is little to go one, what else can I do to shed some light on this? This is a live server so I can't reboot it or take it down easily bare in mind.

share|improve this question
    
I have a second problem relating to this one; How can I stop this from being logged 100 times a second? This box is writing about 2MBs of logs a second, which is quite a lot! For the moment I have stopped rsyslogd. Is there another way though as other processes wont be able to log anything now? –  jwbensley Jan 31 '12 at 10:33
    
rsyslog rate limiting might help. –  Luis Bruno Jan 31 '12 at 13:09

1 Answer 1

up vote 1 down vote accepted

I wish my servers' ECC chips were supported by the EDAC code I'm running! Try dmidecode -t memory to see the ECC hardware you have.

In your logs you're getting a notification from an ECC chip; If your chip hadn't been supported (like mine!) you'd get silent ECC corrections. In your case, the ECC correction happened and you also got notified, because you have support.

I'd go and change that memory stick at first. On the other hand, you might have a faulty channel, or a faulty processor core. I've once diagnosed such a problem with memtest86.org (the original memtest86 has SMP support, try it memtest86+).

Disable ECC in BIOS, boot memtest86 using a floppy/USB stick, and see if a bunch of addresses get flagged, all in a row: might be a memory channel problem if that happens.

share|improve this answer
1  
in my case i use software from the hardware vendor (dell), i use OMSA to diagnostic the hardware issue (memory, etc), no need to reboot to check like memtest, you can check when the server is running. –  chocripple Jan 30 '12 at 15:46

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.