CloudLinux notification reporting problems with /var/lib/clamav mount point

Symptoms

Recently, CloudLinux systems may be sending a notification about /var/lib/clamav not being a valid mount point.  The email notification would look similar to this example below:

We have detected several CloudLinux configuration issues on your system.

You may ignore some or all issues if you know that they don't cause you
 any troubles or they are expected or already scheduled to be fixed 
 You may contact CloudLinux support to help to resolve issues that is
 hard to resolve youself 
 You may disable this cron checks permanently See docs for steps

See report below.

Check fs.enforce_symlinksifowner is correctly enabled in sysctl conf: 
 OK: fs.enforce_symlinksifowner = 1

Check UsePAM in /etc/ssh/sshd_config: 
 OK: Config is fine

Check fs.symlinkown_gid: 
 OK: Web-server user is protected by Symlink Owner Match Protection

Check existence of all user's packages: 
 OK: nonexistent user's packages aren't found

Check the validity of LVE limits on server: 
 OK: Valid LVE limits on server.

Check cagefs mount points exists: 
 FAILED: There are missing mount points: ['/var/lib/clamav']

Check cagefs users.enabled is directory: 
 OK: /etc/cagefs/users.enabled is fine

Check cagefs users.disabled is directory: 
 OK: /etc/cagefs/users.disabled is fine

Check cagefs disable.etcfs exists: 
 OK: /etc/cagefs/etc.safe/disable.etcfs exists

Check cagefs users can enter cagefs: 
 OK: Several tested users really can enter cagefs

Check cagefs proxy commands configs are parsable: 
 OK: Syntax looks fine. Files are parsable

Check cagefs virt.mp files syntax: 
 SKIPPED: No virt.mp files found

Description

CloudLinux is aware of the issue and plans to remove the following lines from the /etc/cagefs/cagefs.mp file in a future release

# next line is added by imunify360
!/var/lib/clamav

For reference, the case number is DEF-12669. You can monitor https://blog.cloudlinux.com/ for an update to this case.

Workaround

To keep this notification from happening you can edit /etc/cagefs/cagefs.mp and remove the two lines mentioned above, then run this command to reload the CageFS mount points:

cagefsctl --remount-all