Yay, glad to see Signature Checking potentially saved your bacon. But this is a really bad thing - if one file is corrupt, you need to figure out WHY it’s corrupt. Possibly a failing drive?
… or a failing memory module somewhere in the system. There are several levels of memory in the average system, and you could be seeing the failure of a cache module, a drive controller cache, on on-disk memory buffer, or a bad hard drive itself.
The ‘fire and forget’ way to solve it is to replace the system wholesale and image the drive onto a new drive. Imaging the drive onto a new drive would probably be a good idea anyway, since problems like this (once they start) usually only get worse.
I do find it odd that the one file on my system that’s seemingly got corrupt has to do with logins! Hmmm.
Anyway I’ve run the rereshsignatures command, I guess there’s no way to tell what may or may not have gone on?
(I use fail2ban and the FreePBX server’s ports aren’t exposed to the world.)
Thanks all