Clamav Antivirus not working anymore after update

Hope anybody can help: A few days ago there was un update of the Clamav plugin and I run it. Since then it doesn't work anymore. It shows in the Dashboard that it is enabled but not running.

I use Putty to take a look and got the following after running: systemctl status clamav-daemon

● clamav-daemon.service - Clam AntiVirus userspace daemon
Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/clamav-daemon.service.d
└─extend.conf
Active: failed (Result: exit-code) since Tue 2020-02-25 12:51:01 CET; 35min ago
Docs: man:clamd(8)
man:clamd.conf(5)
https://www.clamav.net/documents/
Main PID: 697 (code=exited, status=1/FAILURE)
Feb 25 12:50:26 CoolerMasterNAS systemd[1]: Starting Clam AntiVirus userspace daemon...
Feb 25 12:50:26 CoolerMasterNAS systemd[1]: Started Clam AntiVirus userspace daemon.
Feb 25 12:51:01 CoolerMasterNAS clamd[697]: Tue Feb 25 12:51:01 2020 -> !LOCAL: Socket file /var/run/clamav/clamd.ctl could not be bound: Permission denied
Feb 25 12:51:01 CoolerMasterNAS systemd[1]: clamav-daemon.service: Main process exited, code=exited, status=1/FAILURE
Feb 25 12:51:01 CoolerMasterNAS systemd[1]: clamav-daemon.service: Unit entered failed state.
Feb 25 12:51:01 CoolerMasterNAS systemd[1]: clamav-daemon.service: Failed with result 'exit-code'.
root@CoolerMasterNAS:/var/run/clamav#

I strongly believe it had to do with the update so I looked for others having the same issue but I found no other posts related to this.

Any ideas?
Thanks

Thanks for the response votdev,

The /var/run/clamav directory turns out to be empty...

It seems something went wrong with the permissions?

Thanks votdev,

I have installed OMV 4 a long time ago and keep it updated through the OMV management only and regularly. I assume this means I am using the latest clamav.
There is nothing else on this server than OMV which is Debian based as I understood and I don't see Apparmor in the Plugins so I assume I am not using it.

This morning I tried to scan and got the following message which confirms there is no clamd.ctl in the directory /var/run/clamav/. Question is why not?

a putty into the /var/run reveals;

drwxr-xr-x 2 root root 40 Feb 25 12:50 clamav

-----------------------------------------------------------------------------------------------------------------------------
Please wait, scanning shared folder <GedeeldeMappen> ...

ERROR: Could not connect to clamd on LocalSocket /var/run/clamav/clamd.ctl: No such file or directory

----------- SCAN SUMMARY -----------
Infected files: 0
Total errors: 1
Time: 0.000 sec (0 m 0 s)
Done ...

----------------------------------------------------------------------------------------------------------------------------

Going through some other Clamav posts, I figured out that I have Apparmor installed and it is enabled;

root@CoolerMasterNAS:~# cat /sys/module/apparmor/parameters/enabled
Y

Checking the status of it however, doesn't work;

root@CoolerMasterNAS:~# sudo aa-status
sudo: aa-status: command not found

root@CoolerMasterNAS:~# ps auxZ | grep -v '^unconfined'
LABEL USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND

root@CoolerMasterNAS:~# sudo aa-unconfined
sudo: aa-unconfined: command not found

root@CoolerMasterNAS:~#

So, it seems I am having a deeper problem with Apparmor that causes the Clamav issues... I think!

Thanks for the Quick Response again!

I have deinstalled the clamav plugin and reinstalled but nothing helps.

Can I do a refresh of the latest OMV install without having to re-setup the entire server?

I just run another update of OMV 4 and noticed it did not update anything. So all is already up-to-date. I will continue to battle this and when I find a solution post it as a closure to this thread.

SOLVED:

First removed clamav Plugin from OMV
Then removed clamav using the terminal using "apt-get purge clamav-daemon"

Then reinstalled plugin and left it alone for an hour.

Then I found a response from you on May 26 2019 that sudgested to have ALL the users have privileges the Shared Folder that I wanted to scan...

Now it is running... thanks for the help!!