NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Antivirus scanner definition file update failed
ReadyNAS 212 OSversion 6.10.3 Since a couple of days (starting July 5th) my virus definition file update failes.. stating check internet-connection ; my internet connection is fine because the rea...
I kept getting errors while executing command: 'systemctl status clamav-freshclam.service' ; see below
root@Geldrop:~# systemctl status clamav-freshclam.service
● clamav-freshclam.service - ClamAV virus database updater
Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2020-12-23 14:33:45 CET; 15s ago
Process: 6263 ExecStart=/usr/bin/freshclam --quiet (code=exited, status=1/FAILURE)
Main PID: 6263 (code=exited, status=1/FAILURE)Dec 23 14:33:45 Geldrop systemd[1]: Starting ClamAV virus database updater...
Dec 23 14:33:45 Geldrop freshclam[6263]: ClamAV update process started at Wed Dec 23 14:33:45 2020
Dec 23 14:33:45 Geldrop freshclam[6263]: main.cvd is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
Dec 23 14:33:45 Geldrop freshclam[6263]: daily.cld is up to date (version: 26026, sigs: 4328586, f-level: 63, builder: raynman)
Dec 23 14:33:45 Geldrop freshclam[6263]: bytecode.cvd is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
Dec 23 14:33:45 Geldrop systemd[1]: clamav-freshclam.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 14:33:45 Geldrop systemd[1]: Failed to start ClamAV virus database updater.
Dec 23 14:33:45 Geldrop systemd[1]: clamav-freshclam.service: Unit entered failed state.
Dec 23 14:33:45 Geldrop systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'.The following I did after reading the following web-page (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974):
stopping clamav: 'systemctl stop clamav-daemon'stopping clamav freshclam: 'systemctl stop clamav-freshclam'
adjusting member 'usr.bin.freshclam' in dir: /etc/apparmor.d ; adding 'capability dac_override,' and 'capability chown,'
capability setgid,
capability setuid,
capability dac_override,
capability chown,removing all file from dir: '/var/lib/clamav' (bytecode ; daily ; main ; mirrors ; antivir)
starting clamav : 'systemctl start clamav-daemon'
starting clamav freshclam: 'systemctl start clamav-freshclam'
starting 'clamav freshclam' takes a while (about 2 minutes, I guess) and afterwards it looks like the normal databased-updater is working again.... lets see what happens the coming days...
regards
ReadyNAS 202, Firmware 6.10.3, 2x 1TB
Hello. I will just say again since I run a daily CRON job my issue is resolved for me. Lets call it a workaround:
- login to your NAS as root via ssh
- 'crontab -e'
- e.g. add: '0 4 * * * /usr/bin/freshclam' - this will execute freshclam daily at 4 a.m.
Focusing on the error message "freshclam[5119]: [LibClamAV] mpool_malloc(): Can't allocate memory (262144 bytes)." I did some investigation. The default SWAP-partition is 512 MB and according to several fora on the internet small.
RAM No hibernation With Hibernation Maximum 256MB 256MB 512MB 512MB 512MB 512MB 1024MB 1024MB 1024MB 1024MB 2048MB 2048MB RAM No hibernation With Hibernation Maximum 1GB 1GB 2GB 2GB 2GB 1GB 3GB 4GB 3GB 2GB 5GB 6GB 4GB 2GB 6GB 8GB 5GB 2GB 7GB 10GB 6GB 2GB 8GB 12GB 8GB 3GB 11GB 16GBSo I added a swap-file of 512 MB so the total swap-space became 1024MB and will see if CLAMAV will be updated correctly by the default update-process (the first time it did, so fingers crossed).
So if this additional SWAP-file works, maybe it is an idea to add SWAPD package to the installation and therefor is no need to add a pre-defined SWAP-file :-)
rgds Hans
HansRL wrote:
Focusing on the error message "freshclam[5119]: [LibClamAV] mpool_malloc(): Can't allocate memory (262144 bytes)." I did some investigation. The default SWAP-partition is 512 MB and according to several fora on the internet small.
So I added a swap-file of 512 MB
The memory allocation error is a clue. But that added swap file reduces the OS partition by 512 MB (and it is also rather small). You don't want a full OS partition either, so you do need to be careful here.
Perhaps a better strategy is to look at the services you have running on the NAS, and disable the ones you don't actually need. Also, if you have NFS running you could reduce the number of threads. Similarly remove apps that aren't needed.
My own RN202 (which has never had this failure) has SMB, RSYNC, uPNP, HTTP, HTTPS, SSH, and AntiVirus services enabled. The others are all disabled. All Cloud servers are off. The only app installed is Plex.
Your remark Stephan makes sense that is why I only added a SWAP-file of 512 MB, so my OS-partition is now only used for 49%.
And that is why I mentioned SWAPD-service, because according to the description this will add SWAP-space is needed and release it again when not needed anymore.I saw the usage of the pre-defined SWAP-partition and it was used for more then 500 MB (at least the times I checked it), so almost nothing left. After I added the SWAP-file the usage of both SWAP-spaces did not exceed a total use of 550/560 MB.
rgds Hans
chrhei wrote:ReadyNAS 202, Firmware 6.10.3, 2x 1TB
Hello. I will just say again since I run a daily CRON job my issue is resolved for me. Lets call it a workaround:
- login to your NAS as root via ssh
- 'crontab -e'
- e.g. add: '0 4 * * * /usr/bin/freshclam' - this will execute freshclam daily at 4 a.m.
This suggestion worked for me and got my updates running again. At least for the past 48 hours. I have not had a problem. We'll see how long it lasts.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
