Hi all,
Just updated my ClamAV to version 99.3 on my up-to-date CentOS 7.4
server:
Updated:
clamav.x86_64 0:0.99.3-1.el7
clamav-data.noarch 0:0.99.3-1.el7
clamav-filesystem.noarch 0:0.99.3-1.el7
clamav-lib.x86_64 0:0.99.3-1.el7
clamav-scanner.noarch 0:0.99.3-1.el7
clamav-scanner-systemd.noarch 0:0.99.3-1.el7
clamav-server.x86_64 0:0.99.3-1.el7
clamav-server-systemd.noarch 0:0.99.3-1.el7
clamav-update.x86_64 0:0.99.3-1.el7
After installation I checked the status of ClamAV:
[root@server1 ~]# systemctl status clam*
● [email protected] - Generic clamav scanner daemon
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled;
vendor preset: disabled)
Active: active (running) since Sat 2018-02-03 12:34:10 CET; 28s ago
Main PID: 32468 (clamd)
CGroup: /system.slice/system-clamd.slice/[email protected]
└─32468 /usr/sbin/clamd -c /etc/clamd.d/scan.conf
Feb 03 12:34:09 server1.hartings.se clamd[32468]: ELF support enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: Mail files support
enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: OLE2 support
enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: PDF support enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: SWF support enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: HTML support
enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: XMLDOCS support
enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: HWP3 support
enabled.
Feb 03 12:34:09 server1.hartings.se clamd[32468]: Self checking every
600 seconds.
Feb 03 12:34:10 server1.hartings.se systemd[1]: Started Generic clamav
scanner daemon.
● clam-freshclam.service - freshclam scanner
Loaded: loaded (/usr/lib/systemd/system/clam-freshclam.service;
enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-01-28 15:29:46 CET; 5 days
ago
Main PID: 1380 (freshclam)
CGroup: /system.slice/clam-freshclam.service
└─1380 /usr/bin/freshclam -d -c 4
Feb 03 03:30:15 server1.hartings.se freshclam[1380]:
--------------------------------------
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: Received signal:
wake up
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: ClamAV update
process started at Sat Feb 3 09:30:15 2018
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: Your ClamAV
installation is OUTDATED!
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: Local version:
0.99.2 Recommended version: 0.99.3
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: DON'T PANIC! Read
http://www.clamav.net/documents/upgrading-clamav
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: main.cld is up to
date (version: 58, sigs: 4566249, f-level: 60, builder...gmgr)
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: daily.cld is up
to date (version: 24280, sigs: 1843172, f-level: 63, bui... neo)
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: bytecode.cld is
up to date (version: 319, sigs: 75, f-level: 63, builder: neo)
Feb 03 09:30:15 server1.hartings.se freshclam[1380]:
--------------------------------------
Hint: Some lines were ellipsized, use -l to show in full.
[root@server1 ~]#
I checked the installed packages and ongoing processes:
[root@server1 ~]# rpm -qa | grep clam
clamav-0.99.3-1.el7.x86_64
clamav-data-0.99.3-1.el7.noarch
clamav-scanner-0.99.3-1.el7.noarch
clamav-lib-0.99.3-1.el7.x86_64
clamav-server-0.99.3-1.el7.x86_64
clamav-filesystem-0.99.3-1.el7.noarch
clamav-scanner-systemd-0.99.3-1.el7.noarch
clamav-server-systemd-0.99.3-1.el7.noarch
clamav-update-0.99.3-1.el7.x86_64
[root@server1 ~]# rpm -qa | grep fresh
[root@server1 ~]#
[root@server1 ~]# ps -ef | grep fresh
clamupd+ 1380 1 0 Jan28 ? 00:00:12 /usr/bin/freshclam -d
-c 4
root 1705 1288 0 12:40 pts/1 00:00:00 grep --color=auto
fresh
root 32196 32191 0 12:00 ? 00:00:00 /bin/bash
/usr/share/clamav/freshclam-sleep
[root@server1 ~]#
Nothing seems to be wrong. Why am I getting the warning messages:
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: Your ClamAV
installation is OUTDATED!
Feb 03 09:30:15 server1.hartings.se freshclam[1380]: Local version:
0.99.2 Recommended version: 0.99.3
Any comments?
BTW, I did not update /etc/clamd.d/scan.conf when updating the ClamAV
packages - just used the old version; but this could not be the
reason, could it?
Updating : clamav-scanner-0.99.3-1.el7.noarch
8/44
warning: /etc/clamd.d/scan.conf created as
/etc/clamd.d/scan.conf.rpmnew
Thanks for your input!
_______________________________________________
clamav-users mailing list
[email protected]
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
