Is the failure of mcelog an imporant security issue?

I was listing the daemons (journalctl --all) and i have noticed that mcelog are disabled and shouting down, I dispaly the satus and this is the result:

● mcelog.service - Machine Check Exception Logging Daemon
Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2019-11-16 12:57:50 MST; 4h 9min ago
Process: 850 ExecStart=/usr/sbin/mcelog --ignorenodev --daemon --foreground (code=exited, status=1/FAILURE)
Main PID: 850 (code=exited, status=1/FAILURE)
CPU: 4ms

Nov 16 12:57:49 localhost.localdomain systemd[1]: Started Machine Check Exception Logging Daemon.
Nov 16 12:57:50 localhost.localdomain mcelog[850]: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.
Nov 16 12:57:50 localhost.localdomain mcelog[850]: CPU is unsupported
Nov 16 12:57:50 localhost.localdomain systemd[1]: mcelog.service: Main process exited, code=exited, status=1/FAILURE
Nov 16 12:57:50 localhost.localdomain systemd[1]: mcelog.service: Failed with result ‘exit-code’.

For what i read about this daemond this nofify some important problems, I haven’t got a problem in my dialy workflow. I only want to know what means this internal problem in my machine

I have the same messages and state with mcelog. I think I disabled this service to avoid the failed state. sudo systemctl disable mcelog.service

Apparently it is deprecated and the recommended replacement is called rasdaemon.

You can install rasdaemon on Fedora with sudo dnf install rasdaemon and enable it: sudo systemctl enable rasdaemon.service.

I will be giving this a try.


Does this work in parallel with mcelog? or is it required to remove mcelog?

Right now, rasdaemon seems to work fine, I’ve just disabled mcelog, but not removed it.