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
peterongley wrote:
SO, I followed the links to manually download the update but the disk image that is downloaded WILL NOT OPEN on my iMac and nothing I have tried will allow me to mount the disk image and instal it. HELP????
It's not a disk image - it just happens to have an img extension. You don't open it or mount it on the Mac.
Instead you go to system->settings->update in the admin web ui and click on the "install firmware" control. That will open a window that lets you select the file. It will then be uploaded to the NAS, and after verification it will install. You'll then get a pop-up telling you to reboot the NAS.
If this is too hard for you, then just wait a bit longer. Netgear should be pushing the release out through check-for-updates fairly soon.
StephenB wrote:Instead you go to system->settings->update in the admin web ui and click on the "install firmware" control. That will open a window that lets you select the file. It will then be uploaded to the NAS, and after verification it will install. You'll then get a pop-up telling you to reboot the NAS.
Thanks for your help. The .img file extension had me fooled inti thinking it was a **bleep** image, (I can't imagine why).
I have done as you suggested and gone in through the system page and tried to do a manual firmware update. All I am getting is a blue spinning wheel as the system tries to upload the file but nothing happens. Eventually RAIDar just gives up. I guess I will have to wait until the update is registered on the server and my system recognises that it needs to be updated.
Once again, thanks for taking the time to answer my question.
peterongley wrote:
All I am getting is a blue spinning wheel as the system tries to upload the file but nothing happens.You uploaded the arm binary???
I suggest checking that your OS partition isn't full. Download the entire log zip file from the logs page in the web ui.
Then open volume.log, and scroll down to the section that starts with === df -h ===
=== df -h === Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 1.1G 2.7G 29% / tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 7.7M 1.9G 1% /run tmpfs 962M 12M 950M 2% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
The /dev/md0 line is the OS partition. Normally it is 20-30% full. Let us know what yours is.
StephenB wrote:You uploaded the arm binary???
I suggest checking that your OS partition isn't full. Download the entire log zip file from the logs page in the web ui.
Thanks for your reply.
Yes I downloaded the arm binary file.
Checked the log as suggested. It is currently at 37%
Maybe reboot the NAS and try the upload again.
StephenB wrote:Maybe reboot the NAS and try the upload again.
Thanks StepenB!!! Who would have thought the old, "Try turning it off and turning it back on again," suggestion would work??
I restarted the NAS and the binary file uploaded immediately, withing a matter of seconds. The NAS then needed to be rebooted twice before the firmware installed itself, but now everything is looking like it has worked.
Thanks for your support. I just wish Netgear would make these things simple and easy for non-expert users like myself......
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
