- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: msg "Your ClamAV installation is OUTDATED!" is issued each time freshclam is run
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
High level details from my RN314 are below
RN314 Details
As you can see from the details above the AV is updating without issue since 6.10.4 Hotfix 1 was installed.
However when I login via SSH to check fresclam I note the following
root@xxxxxReadyNASReadyNAS:~# 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: inactive (dead) since Fri 2021-04-23 13:28:51 AEST; 19h ago Process: 29578 ExecStart=/usr/bin/freshclam --quiet (code=exited, status=0/SUCCESS) Main PID: 29578 (code=exited, status=0/SUCCESS) Apr 23 13:27:49 xxxxxReadyNASReadyNAS freshclam[29578]: Your ClamAV installation is OUTDATED! Apr 23 13:27:49 xxxxxReadyNASReadyNAS freshclam[29578]: Local version: 0.100.2 Recommended version: 0.103.2 Apr 23 13:27:49 xxxxxReadyNASReadyNAS freshclam[29578]: DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav Apr 23 13:27:49 xxxxxReadyNASReadyNAS freshclam[29578]: main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr) Apr 23 13:27:58 xxxxxReadyNASReadyNAS freshclam[29578]: Downloading daily-26148.cdiff [100%] Apr 23 13:28:08 xxxxxReadyNASReadyNAS freshclam[29578]: daily.cld updated (version: 26148, sigs: 3971965, f-level: 63, builder: raynman) Apr 23 13:28:08 xxxxxReadyNASReadyNAS freshclam[29578]: bytecode.cld is up to date (version: 333, sigs: 92, f-level: 63, builder: awillia2) Apr 23 13:28:49 xxxxxReadyNASReadyNAS freshclam[29578]: Database updated (8536959 signatures) from database.clamav.net (IP: 104.16.219.84) Apr 23 13:28:50 xxxxxReadyNASReadyNAS freshclam[29578]: Clamd successfully notified about the update. Apr 23 13:28:51 xxxxxReadyNASReadyNAS systemd[1]: Started ClamAV virus database updater.
This all looks normal with the execption of
Your ClamAV installation is OUTDATED! Apr 23 13:27:49
Local version: 0.100.2 Recommended version: 0.103.2 Apr 23 13:27:49
DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
My questions which I hope the community may be able to help, knowing this is not normal
- How does the system update ClamAV?
- Is there an action I can take to update ClamAV?
Many thanks in advance...
@B_L @dingjs1421 and @StephenB you guys have been great in the past helping me. Any advice?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @scrjs
The ClamAV version in the latest 6.10.4 firmware and the upcoming 6.10.5 firmware is 0.100.2. It works well in ReadyNAS device so far.
It is not recommaned to upgrade the ClamAV engine manually. ReadyNAS engineering team will be looking into the plan of upgrading it to the latest version in the future firmware release.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @scrjs
The ClamAV version in the latest 6.10.4 firmware and the upcoming 6.10.5 firmware is 0.100.2. It works well in ReadyNAS device so far.
It is not recommaned to upgrade the ClamAV engine manually. ReadyNAS engineering team will be looking into the plan of upgrading it to the latest version in the future firmware release.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: msg "Your ClamAV installation is OUTDATED!" is issued each time freshclam is run
@B_L wrote:Hi @scrjs
The ClamAV version in the latest 6.10.4 firmware and the upcoming 6.10.5 firmware is 0.100.2. It works well in ReadyNAS device so far.
It is not recommaned to upgrade the ClamAV engine manually. ReadyNAS engineering team will be looking into the plan of upgrading it to the latest version in the future firmware release.
Hi @B_L ,
Sincerly thank you for the prompt response, I was wondering if this needed action on my part and you have clearly indicated that this will be resolved in future firmware updates for which I am more then happy to wait.