NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
No antivirus updates since upgrade to 6.6.1
Since upgrading to OS 6.6.1 from 6.6.0 last weekend, I have not had any antivirus updates. Also, there is nothing in log showing that it's trying to update the AV definitions....
Similar behavior here. Upgraded from 6.6.0 to 6.6.1 on 01/11/17, got antivirus update on 01/12/17, but nothing since then.
After the upgrade I noticed ctscand was no longer running and clamd was running. Presumably Netgear switched antivirus vendors. However clamd stopped running on 01/13/17. Here was the most recent entry in the syslog:
Jan 13 06:15:24 Netgear-RN202 clamd[1247]: SelfCheck: Database status OK.
After that, nothing further from clamd. I noticed, however, something called freshclam is running:
root 2111 3.8 0.3 10304 6540 ? Ss 06:40 0:12 /usr/bin/freshclam --quiet
Also tried rebooting, and disabling, then re-enabling, virus checking from ReadyNAS admin page. clamd still not running, and no antivirus updates.
I tried running :
'sudo freshclam' as admin user, and the server appeared to perform an update, though the admin gui did not show the update.
After a server restart, it did show the update on the gui....
From terminal several hours later, I see the following though :
$ sudo service clamav-freshclam status
● clamav-freshclam.service - ClamAV virus database updater
Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; static; vendor preset: disabled)
Active: inactive (dead) since Sat 2017-01-14 22:30:31 WET; 6s ago
Process: 2236 ExecStart=/usr/bin/freshclam --quiet (code=exited, status=0/SUCCESS)
Main PID: 2236 (code=exited, status=0/SUCCESS)
I can start it with :
sudo service clamav-freshclam start
and status comes back :
clamav-freshclam.service - ClamAV virus database updater
Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; static; vendor preset: disabled)
Active: inactive (dead) since Sat 2017-01-14 22:30:31 WET; 6s ago
Process: 2236 ExecStart=/usr/bin/freshclam --quiet (code=exited, status=0/SUCCESS)
Main PID: 2236 (code=exited, status=0/SUCCESS)
Jan 14 22:30:22 MegaNAS systemd[1]: Starting ClamAV virus database updater...
Jan 14 22:30:22 MegaNAS freshclam[2236]: ClamAV update process started at Sat Jan 14 22:30:22 2017
Jan 14 22:30:22 MegaNAS freshclam[2236]: main.cvd is up to date (version: 57, sigs: 4218790, f-leve
l: 60, builder: amishhammer)
Jan 14 22:30:23 MegaNAS freshclam[2236]: Downloading daily-22892.cdiff [100%]
Jan 14 22:30:23 MegaNAS freshclam[2236]: Downloading daily-22893.cdiff [100%]
Jan 14 22:30:27 MegaNAS freshclam[2236]: daily.cld updated (version: 22893, sigs: 1360574, f-level:
63, builder: neo)
Jan 14 22:30:27 MegaNAS freshclam[2236]: bytecode.cvd is up to date (version: 285, sigs: 57, f-leve
l: 63, builder: bbaker)
Jan 14 22:30:31 MegaNAS freshclam[2236]: Database updated (5579421 signatures) from database.clamav
.net (IP: 193.1.193.64)
Jan 14 22:30:31 MegaNAS freshclam[2236]: Clamd successfully notified about the update.
Jan 14 22:30:31 MegaNAS systemd[1]: Started ClamAV virus database updater.
So this appears to have kicked things off again, but I expect the daemon to stop again... any ideas anyone?
sudo? That's superfluous when logged in to SSH as root. sudo is used to run commands as if you were the root user.
Can you send in your logs (see the Sending Logs link in my sig)?Hi mdgm,
Thanks for your reply - I have sent on the logs, as requested. I tend to use sudo where possible to avoid using root user for everything... Just a practise I use in my own work to avoid mistakes.
I checked again this morning, and the daemon is dead again...
Kind Regards,
goodrip12
It appears that my server has updated definitions today, so I guess my problem has sorted itself out somehow...
clamav-freshclam is a timer service, so it should not be running all the time. You can check `systemctl status clamav-freshclam.timer` to see if the timer is active, or `systemctl list-timers` to see when it is scheduled to run next.
Here's what I get on my system:
# systemctl status clamav-freshclam.timer ● clamav-freshclam.timer - Anti-Virus Definition Update Timer Loaded: loaded (/lib/systemd/system/clamav-freshclam.timer; static; vendor preset: enabled) Active: active (running) since Sat 2017-01-14 12:40:51 PST; 2 days ago Jan 14 12:40:51 Netgear-RN202 systemd[1]: Stopped Anti-Virus Definition Update Timer. Jan 14 12:40:51 Netgear-RN202 systemd[1]: Stopping Anti-Virus Definition Update Timer. Jan 14 12:40:51 Netgear-RN202 systemd[1]: Started Anti-Virus Definition Update Timer. # systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES Sat 2017-01-14 06:56:32 PST 2 days ago Sat 2017-01-14 12:40:51 PST 2 days ago clamav-freshclam.timer clamav-freshclam.service Mon 2017-01-16 18:49:36 PST 1h 35min left Mon 2017-01-16 14:49:36 PST 2h 24min ago radar.timer radar.service Tue 2017-01-17 06:42:33 PST 13h left Mon 2017-01-16 06:42:33 PST 10h ago apt-update.timer apt-update.service Tue 2017-01-17 06:54:33 PST 13h left Mon 2017-01-16 06:54:33 PST 10h ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service Tue 2017-01-17 07:00:33 PST 13h left Mon 2017-01-16 07:00:33 PST 10h ago logtruncate.timer logtruncate.service Sat 2017-01-21 06:44:32 PST 4 days left Sat 2017-01-14 06:44:32 PST 2 days ago rn-update.timer rn-update.service 6 timers listed. Pass --all to see loaded but inactive timers, too.
Looks as though it should have run 2 days ago, but didn't.
Maybe yours started but never finished? `systemctl status clamav-freshclam.service` should help determine that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
