lfd on System Integrity checking detected a modified system file

[mockingbird]

I know this s been covered before ad nauseum, but I could not find an answer for my issue.

I must have done the update two weeks ago, yet I keep receiving emails from LFD with this message:

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/da: FAILED
/bin/da: FAILED

Surely, some internal database within DA should have the corrected md5sum values by now, but evidently they do not.

I have automatic updates disabled, perhaps this is the reason? I would like to keep automatic updates disabled. So is there a way to force a refresh on the md5sum values so that the error goes away?

Thanks

 

[Richard G]

Normally restarting both DA and csf/lfd should stop the issue.
I normally get those messages only once after an update.

Als check if you have this line in the /etc/csf/csf.pignore file.
exe:/usr/local/directadmin/directadmin

 

[mockingbird]

Normally restarting both DA and csf/lfd should stop the issue.
I normally get those messages only once after an update.

Als check if you have this line in the /etc/csf/csf.pignore file.
exe:/usr/local/directadmin/directadmin

Thanks very much.

I issued:

service directadmin restart
csf -r

...I'll let you know if this fixes it.

I want to avoid adding da to the ignore file... The frequency is once per day -- so I will do it if it comes down to it, but I want to know first if this is something I should let the admins of DA know about.

 

[Richard G]

csf -r

Should be normally csf -ra to restart both csf and lfd.

I want to avoid adding da to the ignore file...

DA as such should not be needed but the line I gave is in there by default after a DA installation below the datatasq which is also in there.

However once a day is not a big deal indeed, but if nothing change, it should not pop up.
We don't have that issue so it's a bit odd that it's coming back in your case.