![]() ![]() You can check if your VM has a swap file using the command: # cat /proc/swaps ![]() If your virtual machine doesn't have a swap file then you should create one. Some times service providers create a virtual machine without any swap file. Jun 19 21:22:52 el8p18 kernel: Out of memory: Killed process 2007089 (clamd) total-vm:3093760kB, anon-rss:1779240kB, file-rss:0kB, shmem-rss:0kB, UID:981 pgtables:5816kB oom_score_adj:0Ĭreate a Swap File if your VM Doesn't Have One We recommend a minimum of at least 4 GB of server memory (sometimes more depending on how many additional services you have running): // AlmaLinux/Centos/RockyLinux/CloudLinux/RHEL If the server is running low on free memory sometimes the out of memory killer (OOM Killer) will kill the ClamAV daemon. Total used free shared buff/cache available You can check the free memory of the server using the command: free -m (look at the free column): # free -m The most common problem is not enough free memory for the ClamAV daemon. Then press the Update button to save the page. To disable the secondary fallback scanner go to Warden -> Settings -> Scanner Settings -> Scanner backup template -> set it to None. How to Disable the Clamscan Fallback Scanner Look below for how to disable the clamscan secondary fallback scanner if you don't want Amavis to fall back to it. Clamscan is not suitable for scanning large amounts of mail because the ClamAV signatures have to be loaded into memory for every scan (This is what causes the high load on the server). Clamd is the highly efficient daemon version of ClamAV while clamscan is the inefficient non-demonized version. Note that the clamscan binary is NOT the same as clamd. ![]() By default Amavis will fall back to the secondary clamscan binary when the ClamAV daemon is down or having problems. Normally high server load is caused by the clamscan binary when the ClamAV daemon is down. RHEL/Almalinux/CloudLinux/RockyLinux clamdtop -config-file=/etc/clamd.d/nfĭebian/Ubuntu clamdtop -config-file=/etc/clamav/nf Monitoring the ClamAV Daemon Memory and CPU UsageĪdministrators can use the clamdtop command to monitor ClamAV daemon memory and CPU usage statistics from the command line: ![]() To view the logs on the command line:ĪlmaLinux/Centos/RockyLinux/RHEL/CloudLinux tail -f /var/log/clamd.scanĭebian/Ubuntu tail -f /var/log/clamav/clamav.log You can view the ClamAV deamon logs under Warden -> Logs -> Anti-virus Logs. You can view the current ClamAV configuration using the clamconf command: clamconf You can click on the Active or Inactive in the status column to get more information.Ĭheck the Status of the ClamAV Daemon From the Command LineĪlmaLinux/Centos/RockyLinux/RHEL/CloudLinux systemctl status systemctl status clamav-daemonĬhecking the Current Configuration From the Command Line You can check the ClamAV daemon status under the Anti-virus line in the Services dashboard widget. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |