Author Topic: Latest updates have created a huge list of MD5 Checksum errors on CWP  (Read 471 times)

0 Members and 1 Guest are viewing this topic.

Offline
***
I have just run the latest updates as directed by the CWP admin dashboard. I installed the updates and now have a huge list of MD5 checksum errors sent to my email.

Should i be worried about these, or is this just an overly sensitive security software complaint?

The MD5 Checksum errors are listed below;


Time:     Wed May  1 08:00:42 2019 +1000

The following list of files have FAILED the md5sum comparison test. This means that the file has been changed in some way. This could be a result of an OS update or application upgrade. If the change is unexpected it should be investigated:


/usr/bin/bootctl: FAILED
/usr/bin/busctl: FAILED
/usr/bin/c++: FAILED
/usr/bin/cc: FAILED
/usr/bin/coredumpctl: FAILED
/usr/bin/cpp: FAILED
/usr/bin/cpupower: FAILED
/usr/bin/g++: FAILED
/usr/bin/gcc: FAILED
/usr/bin/gcov: FAILED
/usr/bin/hostnamectl: FAILED
/usr/bin/journalctl: FAILED
/usr/bin/localectl: FAILED
/usr/bin/loginctl: FAILED
/usr/bin/machinectl: FAILED
/usr/bin/pango-list: FAILED
/usr/bin/pango-view: FAILED
/usr/bin/rsync: FAILED
/usr/bin/systemctl: FAILED
/usr/bin/systemd-analyze: FAILED
/usr/bin/systemd-ask-password: FAILED
/usr/bin/systemd-cat: FAILED
/usr/bin/systemd-cgls: FAILED
/usr/bin/systemd-cgtop: FAILED
/usr/bin/systemd-coredumpctl: FAILED
/usr/bin/systemd-delta: FAILED
/usr/bin/systemd-detect-virt: FAILED
/usr/bin/systemd-escape: FAILED
/usr/bin/systemd-firstboot: FAILED
/usr/bin/systemd-hwdb: FAILED
/usr/bin/systemd-inhibit: FAILED
/usr/bin/systemd-loginctl: FAILED
/usr/bin/systemd-machine-id-setup: FAILED
/usr/bin/systemd-notify: FAILED
/usr/bin/systemd-nspawn: FAILED
/usr/bin/systemd-path: FAILED
/usr/bin/systemd-run: FAILED
/usr/bin/systemd-stdio-bridge: FAILED
/usr/bin/systemd-tmpfiles: FAILED
/usr/bin/systemd-tty-ask-password-agent: FAILED
/usr/bin/timedatectl: FAILED
/usr/bin/udevadm: FAILED
/usr/bin/x86_64-redhat-linux-c++: FAILED
/usr/bin/x86_64-redhat-linux-g++: FAILED
/usr/bin/x86_64-redhat-linux-gcc: FAILED
/usr/sbin/arpd: FAILED
/usr/sbin/bridge: FAILED
/usr/sbin/ctstat: FAILED
/usr/sbin/devlink: FAILED
/usr/sbin/dmfilemapd: FAILED
/usr/sbin/dmsetup: FAILED
/usr/sbin/dmstats: FAILED
/usr/sbin/genl: FAILED
/usr/sbin/halt: FAILED
/usr/sbin/ifstat: FAILED
/usr/sbin/init: FAILED
/usr/sbin/ip: FAILED
/usr/sbin/kexec: FAILED
/usr/sbin/lnstat: FAILED
/usr/sbin/makedumpfile: FAILED
/usr/sbin/mkdumprd: FAILED
/usr/sbin/nstat: FAILED
/usr/sbin/poweroff: FAILED
/usr/sbin/reboot: FAILED
/usr/sbin/rtacct: FAILED
/usr/sbin/rtmon: FAILED
/usr/sbin/rtstat: FAILED
/usr/sbin/runlevel: FAILED
/usr/sbin/shutdown: FAILED
/usr/sbin/ss: FAILED
/usr/sbin/tc: FAILED
/usr/sbin/telinit: FAILED
/usr/sbin/udevadm: FAILED
/usr/sbin/vmcore-dmesg: FAILED
/bin/bootctl: FAILED
/bin/busctl: FAILED
/bin/c++: FAILED
/bin/cc: FAILED
/bin/coredumpctl: FAILED
/bin/cpp: FAILED
/bin/cpupower: FAILED
/bin/g++: FAILED
/bin/gcc: FAILED
/bin/gcov: FAILED
/bin/hostnamectl: FAILED
/bin/journalctl: FAILED
/bin/localectl: FAILED
/bin/loginctl: FAILED
/bin/machinectl: FAILED
/bin/pango-list: FAILED
/bin/pango-view: FAILED
/bin/rsync: FAILED
/bin/systemctl: FAILED
/bin/systemd-analyze: FAILED
/bin/systemd-ask-password: FAILED
/bin/systemd-cat: FAILED
/bin/systemd-cgls: FAILED
/bin/systemd-cgtop: FAILED
/bin/systemd-coredumpctl: FAILED
/bin/systemd-delta: FAILED
/bin/systemd-detect-virt: FAILED
/bin/systemd-escape: FAILED
/bin/systemd-firstboot: FAILED
/bin/systemd-hwdb: FAILED
/bin/systemd-inhibit: FAILED
/bin/systemd-loginctl: FAILED
/bin/systemd-machine-id-setup: FAILED
/bin/systemd-notify: FAILED
/bin/systemd-nspawn: FAILED
/bin/systemd-path: FAILED
/bin/systemd-run: FAILED
/bin/systemd-stdio-bridge: FAILED
/bin/systemd-tmpfiles: FAILED
/bin/systemd-tty-ask-password-agent: FAILED
/bin/timedatectl: FAILED
/bin/udevadm: FAILED
/bin/x86_64-redhat-linux-c++: FAILED
/bin/x86_64-redhat-linux-g++: FAILED
/bin/x86_64-redhat-linux-gcc: FAILED
/sbin/arpd: FAILED
/sbin/bridge: FAILED
/sbin/ctstat: FAILED
/sbin/devlink: FAILED
/sbin/dmfilemapd: FAILED
/sbin/dmsetup: FAILED
/sbin/dmstats: FAILED
/sbin/genl: FAILED
/sbin/halt: FAILED
/sbin/ifstat: FAILED
/sbin/init: FAILED
/sbin/ip: FAILED
/sbin/kexec: FAILED
/sbin/lnstat: FAILED
/sbin/makedumpfile: FAILED
/sbin/mkdumprd: FAILED
/sbin/nstat: FAILED
/sbin/poweroff: FAILED
/sbin/reboot: FAILED
/sbin/rtacct: FAILED
/sbin/rtmon: FAILED
/sbin/rtstat: FAILED
/sbin/runlevel: FAILED
/sbin/shutdown: FAILED
/sbin/ss: FAILED
/sbin/tc: FAILED
/sbin/telinit: FAILED
/sbin/udevadm: FAILED
/sbin/vmcore-dmesg: FAILED


Offline
*
Re: Latest updates have created a huge list of MD5 Checksum errors on CWP
« Reply #1 on: April 30, 2019, 11:38:05 PM »
That's normal behaviour after performing a yum update. You might want to set up a custom log address in CSF (which sends these emails) so that they're logged for reference but you're not continually bothered by them.

Offline
***
This means just the files showed are binary different from before.
If you did run "yum update" this is completely normal.

You should be concerned only if you have not changed anything in your server.
But still csf does these updates automatically, alone, and causes such warnings.

But these warnings are completely important to keep your eyes watching your server.

Regards,
Netino

Offline
***
I figured it was probably nothing to worry about.

None of the other control panels I have used have done this before.

Offline
*
So, if it's updating something, then csf MD5 Checksum will report it. It's nice because we'll be aware about something changes in our system