![]() ![]() This directive allows you to change the database owner. ![]() # By default when started freshclam drops privileges and switches to the # This option allows you to save the process identifier of the daemon Always enabled when LogFileMaxSize is enabled. # Specify the type of syslog messages - please refer to 'man syslog' # Use system logger (can work together with UpdateLogFile). # log rotation (the LogRotate option) will always be enabled. # and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes). # You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes) UpdateLogFile /var/log/clamav/freshclam.log # Path to the log file (make sure it has proper permissions) # Default: hardcoded (depends on installation options) # Please read the nf(5) manual before editing this file. Your network may be down or none of the mirrors listed in /etc/nf is working. Nonblock_connect: connect(): fd=5 errno=101: Network is unreachableĬan't connect to port 80 of host db. (IP: 2400:cb00:2048:1::6810:b98a)ĬlamAV update process started at Tue Aug 7 21:14:16 2018ĬlamAV update process started at Tue Aug 7 21:14:28 2018ĬlamAV update process started at Tue Aug 7 21:14:34 2018 Clueless on what needs to be fixed or replaced with these corrupted headers. I'm having the same issues as everyone else. There is no general problem with clamav reading the virus databases on x86_64 EL7. * both before and after running freshclam. * with or without the zlib-1.2.686 package installed In any case, I can install clamav on a test EL7 VM and run clamscan successfully and without error: Ldd /usr/sbin/clamd|grep libz should show you something like If your clamd packages are 64 bit (which they must be unless you got them from somewhere other than EPEL) then they aren't using the 32 bit zlib. The 32bit version of zlib on your will only be used if you have other i686 packages or some non-packaged 32 bit pieces of software that need it, and then only by those packages or that software. The problem discussed in this ticket is restricted to 32bit EPEL6. You may be having similar errors (because those errors just indicate that a CVD file couldn't be parsed) but that does not mean that the underlying issue is the same. I'm relatively certain that you are having a different problem. WARNING: cli_cvdload: Corrupted CVD headerĪs you can see, it downloads daily.cvd but fails to parse/load it. WARNING: Incremental update failed, trying to download daily.cvd WARNING: getpatch: Can't download daily-24612.cdiff from db.LT. Main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr) WARNING: Local version: 0.100.0 Recommended version: 0.100.1 WARNING: Your ClamAV installation is OUTDATED! ClamAV update process started at Thu Jul 12 03:59:02 2018 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |