Re: [clamav-users] ClamAV 1.2.1, 1.1.3, 1.0.4, 0.103.11 patch versions published

[Kevin O'Connor via clamav-users]

Thank you, Robert,
I'm not sure how I managed to misread 1.0.3 for 0.103. My apologies.
Kevin

On Wed, Oct 25, 2023 at 5:15 PM Robert M. Stockmann via clamav-users <
clamav-users@lists.clamav.net> wrote:

> On Wed, 25 Oct 2023, Kevin O'Connor via clamav-users wrote:
>
> > Date: Wed, 25 Oct 2023 16:34:46 -0400
> > From: Kevin O'Connor via clamav-users 
> > To: ClamAV users ML 
> > Cc: Kevin O'Connor 
> > Subject: Re: [clamav-users] ClamAV 1.2.1, 1.1.3, 1.0.4,
> > 0.103.11 patch versions published
> >
> > Hi Micah,
> >
> > I'm assuming that this is the report of an updated 0.103.11:
> >
> > $ /usr/sbin/clamd --version
> >
> > ClamAV 1.0.3/27072/Wed Oct 25 07:45:37 2023
> >
> > Is that correct?.. it was difficult to tell from the links.
> >
> clamav 0.103.11 does report this :
>
> $ clamdscan --version
> ClamAV 0.103.11/27072/Wed Oct 25 09:45:37 2023
> $ /usr/sbin/clamd --version
> ClamAV 0.103.11/27072/Wed Oct 25 09:45:37 2023
>
> >
> > On Wed, Oct 25, 2023 at 2:13 PM Micah Snyder (micasnyd) via clamav-users
> <
> > clamav-users@lists.clamav.net> wrote:
>
> > > Read this online at:
> > > https://blog.clamav.net/2023/10/clamav-121-113-104-010311-patch.html
> <https://blog.clamav.net/2023/10/clamav-121-113-104-010311-patch.html>
> > > <https://blog.clamav.net/2023/10/clamav-121-113-104-010311-patch.html
> <https://blog.clamav.net/2023/10/clamav-121-113-104-010311-patch.html>
> >
>
> --
> Robert M. Stockmann - RHCE
> Network Engineer - UNIX/Linux Specialist
> crashrecovery.org st...@stokkie.net
>
> ___
>
> Manage your clamav-users mailing list subscription / unsubscribe:
> https://lists.clamav.net/mailman/listinfo/clamav-users
> <https://lists.clamav.net/mailman/listinfo/clamav-users>
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/Cisco-Talos/clamav-documentation
> <https://github.com/Cisco-Talos/clamav-documentation>
>
> https://docs.clamav.net/#mailing-lists-and-chat
> <https://docs.clamav.net/#mailing-lists-and-chat>
>
___

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat

Re: [clamav-users] ClamAV 1.2.1, 1.1.3, 1.0.4, 0.103.11 patch versions published

[Kevin O'Connor via clamav-users]

Hi Micah,

I'm assuming that this is the report of an updated 0.103.11:

$ /usr/sbin/clamd --version

ClamAV 1.0.3/27072/Wed Oct 25 07:45:37 2023

Is that correct?.. it was difficult to tell from the links.

Kevin

On Wed, Oct 25, 2023 at 2:13 PM Micah Snyder (micasnyd) via clamav-users <
clamav-users@lists.clamav.net> wrote:

> Read this online at:
> https://blog.clamav.net/2023/10/clamav-121-113-104-010311-patch.html
> 
>
>
>
> Today, we are publishing the 1.2.1, 1.1.3, 1.0.4, and 0.103.11 security
> patch versions.
> The release files for the patch versions are available for download on the 
> ClamAV
> downloads page
> ,
> on the GitHub Release page
> ,
> and through Docker Hub
> 
> .
>
> Continue reading to learn what changed in each version.
>
> 1.2.1
>
> ClamAV 1.2.1 is a patch release with the following fixes:
>
>-
>
>Eliminate security warning about unused "atty" dependency.
>- GitHub pull request
>   
>   .
>-
>
>Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
>- GitHub pull request
>   
>   .
>-
>
>Build system: Fix link error with Clang/LLVM/LLD version 17. Patch
>courtesy of Yasuhiro Kimura.
>- GitHub pull request
>   
>   .
>-
>
>Fix alert-exceeds-max feature for files > 2GB and < max-filesize.
>- GitHub pull request
>   
>   .
>
> Special thanks to Yasuhiro Kimura for code contributions and bug reports.
> 1.1.3
>
> ClamAV 1.1.3 is a patch release with the following fixes:
>
>-
>
>Eliminate security warning about unused "atty" dependency.
>- GitHub pull request.
>   
>-
>
>Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
>- GitHub pull request
>   
>   .
>-
>
>Windows: libjson-c 0.17 compatibility fix with ssize_t type definition.
>- GitHub pull request
>   
>   .
>-
>
>Build system: Fix link error with Clang/LLVM/LLD version 17. Patch
>courtesy of Yasuhiro Kimura.
>- GitHub pull request
>   
>   .
>-
>
>Fix alert-exceeds-max feature for files > 2GB and < max-filesize.
>- GitHub pull request
>   
>   .
>
> Special thanks to Yasuhiro Kimura for code contributions and bug reports.
> 1.0.4
>
> ClamAV 1.0.4 is a patch release with the following fixes:
>
>-
>
>Eliminate security warning about unused "atty" dependency.
>- GitHub pull request
>   
>   .
>-
>
>Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
>- GitHub pull request
>   
>   .
>-
>
>Windows: libjson-c 0.17 compatibility fix with ssize_t type definition.
>- GitHub pull request
>   
>   .
>-
>
>Freshclam: Removed a verbose warning printed for each Freshclam HTTP
>request.
>- GitHub pull request
>   
>   .
>-
>
>Build system: Fix link error with Clang/LLVM/LLD version 17. Patch
>courtesy of Yasuhiro Kimura.
>- GitHub pull request
>   
>   .
>-
>
>Fix alert-exceeds-max feature for files > 2GB and < max-filesize.
>- GitHub pull request
>   
>   .
>
> Special thanks to Yasuhiro Kimura for code contributions and bug reports.
> 0.103.11
>
> ClamAV 0.103.11 is a patch release with the following fixes:
>
>-
>
>Upgrade the bundled UnRAR library (libclamunrar) to version 6.2.12.
>- GitHub pull request
>   
>   .
>-
>
>Windows: libjson-c 0.17 compatibility fix with ssize_t type definition.
>- GitHub pull request
>   
>   .
>-
>
>Windows: Update build system to use OpenSSL 3 and PThreads-Win32 v3.
>- GitHub pull request
>   
>   .
>
>
> Posted by Micah Snyder
> 
> at 1:36 PM
> 
>
> 

Re: [clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

[Kevin O'Connor via clamav-users]

ytecode.cld​.  We may issue an empty patch
>file (zero-bytes) to tell freshclam​ to download the whole bytecode.cvd​
>instead. We do this if the patch is so big it is better to just download
>the whole file, or if is a bug preventing the patch file from working
>correctly, which there presently is for bytecode signatures (sad!).
>
>This .cdiff​ update mechanism would not be used in your situation
>because ScriptedUpdates is disabled.
>
>2. a new bytecode.cvd​.
>
>This should only be downloaded in two cases: A) If you do not have the
>old bytecode.cvd​ (or cld​) and thus cannot use the patch file to
>update.  And B) If the bytecode.cdiff​ patch file is empty.
>
> The issue you're facing feels to me like an issue with what the private
> mirror is serving. Can you please check if it is serving an empty
> bytecode.cvd​?  It feels like it may be serving both the empty
> bytecode.cvd​ and a bytecode.cld​.
>
> If that's not the case, then we may have a bug in freshclam​ and I would
> love some more information on what freshclam​ is downloading when it runs
> in order to get into this strange state.
>
> Best,
> Micah
>
> Micah Snyder
> ClamAV Development
> Talos
> Cisco Systems, Inc.
>
> --
> *From:* clamav-users  on behalf of
> Kevin O'Connor via clamav-users 
> *Sent:* Monday, February 27, 2023 11:12 AM
> *To:* ClamAV users ML 
> *Cc:* Kevin O'Connor 
> *Subject:* Re: [clamav-users] 0 length bytecode.cvd causing problems with
> clamav daemon
>
> Marc,
>
> I had a similar understanding of that document.  That is; if there is no
> bytecode.cvd pushed by the ClamAV team, it should not exist on my local
> scanners. When I checked the mirror and there was no bytecode.cvd file, yet
> it appeared on my scanner machines with 0 length, I figured that the new
> release had highlighted a misconfiguration in my freshclam.conf that the
> earlier version was more forgiving of.  However I have not found what that
> might be.
>
> Your idea of removing all the files in the /var/lib/clamav directory is
> what I found worked initially, but that seems like a poor workaround as I
> need this running all the time.  I don't know when our clients will drop
> files on us that need a scan.
>
> Thanks for looking at it.
>
> Kevin
>
> On Mon, Feb 27, 2023 at 1:11 PM Marc via clamav-users <
> clamav-users@lists.clamav.net> wrote:
>
> i would suggest, to delete alle libraries in /var/lib/clamav and download
> all complete new.
> CLD Files comes not regularly, normally we have CVD only.
>
> If i understand this well, CLD Files comes only when error occures while
> updating.
> https://blog.clamav.net/2021/03/clamav-cvds-cdiffs-and-magic-behind.html
> <https://blog.clamav.net/2021/03/clamav-cvds-cdiffs-and-magic-behind.html>
>
>
> Von / From: Kevin O'connor <mailto:kocon...@ampion.net>
> An / To: Newcomer01 <mailto:newcome...@posteo.de>
> Gesendet / Sent: Montag, Februar 27, 2023 um 18:38 (at 06:38 PM) +0100
> Betreff / Subject: Re: [clamav-users] 0 length bytecode.cvd causing
> problems with clamav daemon
> > Heh, good question.  Just checked again, and it looks like that was a
> copy-paste error.  There is only one PrivateMirror line.
> > Kevin
> >
> > On Mon, Feb 27, 2023 at 12:02 PM newcomer01 via clamav-users <
> clamav-users@lists.clamav.net> wrote:
> >
> > why you have set two times the "PrivateMirror" with identically IP's?
> > Can't believe that this happens with the automated PostInst 
> >
> >
> > Von / From: Clamav User Mailinglist  clamav-users@lists.clamav.net>
> > An / To: Newcomer01 <mailto:newcome...@posteo.de>
> > CC / CC: Kevin O'connor <mailto:kocon...@ampion.net>
> > Gesendet / Sent: Montag, Februar 27, 2023 um 16:58 (at 04:58 PM) +0100
> > Betreff / Subject: [clamav-users] 0 length bytecode.cvd causing problems
> with clamav daemon
> > > I am having an issue with 0 length bytecode.cvd files on my scanner
> instances.  This seems to have started sometime on 22 Feb, I'm afraid I
> don't have an exact time. The clamav daemon produces logs like the
> following:
> > >
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error:
> cli_cvdverify: Can't read CVD header
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error: Can't
> load /var/lib/clamav/bytecode.cld: Broken or not a CVD file
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error:
> cli_loaddbdir(): error loading database /var/lib/clamav/bytecode.cld
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: Mon Feb 27 14:39:11

Re: [clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

[Kevin O'Connor via clamav-users]

Marc,

I had a similar understanding of that document.  That is; if there is no
bytecode.cvd pushed by the ClamAV team, it should not exist on my local
scanners. When I checked the mirror and there was no bytecode.cvd file, yet
it appeared on my scanner machines with 0 length, I figured that the new
release had highlighted a misconfiguration in my freshclam.conf that the
earlier version was more forgiving of.  However I have not found what that
might be.

Your idea of removing all the files in the /var/lib/clamav directory is
what I found worked initially, but that seems like a poor workaround as I
need this running all the time.  I don't know when our clients will drop
files on us that need a scan.

Thanks for looking at it.

Kevin

On Mon, Feb 27, 2023 at 1:11 PM Marc via clamav-users <
clamav-users@lists.clamav.net> wrote:

> i would suggest, to delete alle libraries in /var/lib/clamav and download
> all complete new.
> CLD Files comes not regularly, normally we have CVD only.
>
> If i understand this well, CLD Files comes only when error occures while
> updating.
> https://blog.clamav.net/2021/03/clamav-cvds-cdiffs-and-magic-behind.html
> 
>
>
> Von / From: Kevin O'connor 
> An / To: Newcomer01 
> Gesendet / Sent: Montag, Februar 27, 2023 um 18:38 (at 06:38 PM) +0100
> Betreff / Subject: Re: [clamav-users] 0 length bytecode.cvd causing
> problems with clamav daemon
> > Heh, good question.  Just checked again, and it looks like that was a
> copy-paste error.  There is only one PrivateMirror line.
> > Kevin
> >
> > On Mon, Feb 27, 2023 at 12:02 PM newcomer01 via clamav-users <
> clamav-users@lists.clamav.net> wrote:
> >
> > why you have set two times the "PrivateMirror" with identically IP's?
> > Can't believe that this happens with the automated PostInst 
> >
> >
> > Von / From: Clamav User Mailinglist  clamav-users@lists.clamav.net>
> > An / To: Newcomer01 
> > CC / CC: Kevin O'connor 
> > Gesendet / Sent: Montag, Februar 27, 2023 um 16:58 (at 04:58 PM) +0100
> > Betreff / Subject: [clamav-users] 0 length bytecode.cvd causing problems
> with clamav daemon
> > > I am having an issue with 0 length bytecode.cvd files on my scanner
> instances.  This seems to have started sometime on 22 Feb, I'm afraid I
> don't have an exact time. The clamav daemon produces logs like the
> following:
> > >
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error:
> cli_cvdverify: Can't read CVD header
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error: Can't
> load /var/lib/clamav/bytecode.cld: Broken or not a CVD file
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error:
> cli_loaddbdir(): error loading database /var/lib/clamav/bytecode.cld
> > > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: Mon Feb 27 14:39:11 2023
> -> !Broken or not a CVD file
> > > Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Main
> process exited, code=exited, status=1/FAILURE
> > > Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Failed
> with result 'exit-code'.
> > > Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service:
> Consumed 8.679s CPU time.
> > >
> > >
> > > I feel like I have narrowed the problem down to a 0 length
> 'bytecode.cvd' file.  Here is a listing of the definitions directory:
> > >
> > > $ ls -l /var/lib/clamav
> > > total 226168
> > > -rw-r--r-- 1 clamav clamav314802 Feb 27 14:06 bytecode.cld
> > > -rw-r--r-- 1 clamav clamav 0 Feb 27 02:00 bytecode.cvd
> > > -rw-r--r-- 1 clamav clamav  60787973 Feb 27 10:01 daily.cld
> > > -rw-r--r-- 1 clamav clamav69 Feb 23 15:33 freshclam.dat
> > > -rw-r--r-- 1 clamav clamav 170479789 Feb 27 02:00 main.cvd
> > >
> > >
> > > My initial fix (before narrowing the problem down to bytecode.cvd) was
> to
> > >
> > > 1. stop freshclam
> > > 2. clean this directory
> > > 3. restart freshclam
> > > 4. give it time to get the definitions (from a private mirror)
> > > 5. start clamav daemon
> > >
> > > This would work for maybe 1/2 day then the empty bytecode.cvd file
> would reappear and the daemon would fail.
> > >
> > > This morning I was able to spend some more time and find that it was
> just the one file that needed to be removed.
> > >
> > > I have a local mirror because there are several instances of this
> scanner in use (at least 2 instances for several environments).  I have
> checked the mirror and it appears to be working fine and keeping the
> definitions up to date inside our environment.  In addition, the scanner
> instances appear to be keeping the local set of definitions up to date with
> the mirror.
> > >
> > > The mirror does not have a bytecode.cvd file on it (here is a listing
> of its definitions directory)
> > >
> > > $ ls -l /var/lib/clamav
> > > total 226172
> > > -rw-r--r-- 1 clamav clamav

Re: [clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

[Kevin O'Connor via clamav-users]

Heh, good question.  Just checked again, and it looks like that was a
copy-paste error.  There is only one PrivateMirror line.
Kevin

On Mon, Feb 27, 2023 at 12:02 PM newcomer01 via clamav-users <
clamav-users@lists.clamav.net> wrote:

> why you have set two times the "PrivateMirror" with identically IP's?
> Can't believe that this happens with the automated PostInst 
>
>
> Von / From: Clamav User Mailinglist 
> An / To: Newcomer01 
> CC / CC: Kevin O'connor 
> Gesendet / Sent: Montag, Februar 27, 2023 um 16:58 (at 04:58 PM) +0100
> Betreff / Subject: [clamav-users] 0 length bytecode.cvd causing problems
> with clamav daemon
> > I am having an issue with 0 length bytecode.cvd files on my scanner
> instances.  This seems to have started sometime on 22 Feb, I'm afraid I
> don't have an exact time.  The clamav daemon produces logs like the
> following:
> >
> > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error:
> cli_cvdverify: Can't read CVD header
> > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error: Can't load
> /var/lib/clamav/bytecode.cld: Broken or not a CVD file
> > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error:
> cli_loaddbdir(): error loading database /var/lib/clamav/bytecode.cld
> > Feb 27 14:39:11 av-scan-wrhn clamd[163614]: Mon Feb 27 14:39:11 2023 ->
> !Broken or not a CVD file
> > Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Main
> process exited, code=exited, status=1/FAILURE
> > Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Failed
> with result 'exit-code'.
> > Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Consumed
> 8.679s CPU time.
> >
> >
> > I feel like I have narrowed the problem down to a 0 length
> 'bytecode.cvd' file.  Here is a listing of the definitions directory:
> >
> > $ ls -l /var/lib/clamav
> > total 226168
> > -rw-r--r-- 1 clamav clamav314802 Feb 27 14:06 bytecode.cld
> > -rw-r--r-- 1 clamav clamav 0 Feb 27 02:00 bytecode.cvd
> > -rw-r--r-- 1 clamav clamav  60787973 Feb 27 10:01 daily.cld
> > -rw-r--r-- 1 clamav clamav69 Feb 23 15:33 freshclam.dat
> > -rw-r--r-- 1 clamav clamav 170479789 Feb 27 02:00 main.cvd
> >
> >
> > My initial fix (before narrowing the problem down to bytecode.cvd) was to
> >
> > 1. stop freshclam
> > 2. clean this directory
> > 3. restart freshclam
> > 4. give it time to get the definitions (from a private mirror)
> > 5. start clamav daemon
> >
> > This would work for maybe 1/2 day then the empty bytecode.cvd file would
> reappear and the daemon would fail.
> >
> > This morning I was able to spend some more time and find that it was
> just the one file that needed to be removed.
> >
> > I have a local mirror because there are several instances of this
> scanner in use (at least 2 instances for several environments).  I have
> checked the mirror and it appears to be working fine and keeping the
> definitions up to date inside our environment.  In addition, the scanner
> instances appear to be keeping the local set of definitions up to date with
> the mirror.
> >
> > The mirror does not have a bytecode.cvd file on it (here is a listing of
> its definitions directory)
> >
> > $ ls -l /var/lib/clamav
> > total 226172
> > -rw-r--r-- 1 clamav clamav314802 Feb 22 22:02 bytecode.cld
> > -rw-r--r-- 1 clamav clamav  60787973 Feb 27 09:06 daily.cld
> > -rw-r--r-- 1 clamav clamav69 Jan 29  2022 freshclam.dat
> > -rw-r--r-- 1 clamav clamav 170479789 Jan 29  2022 main.cvd
> > -rw-r--r-- 1 clamav clamav87 Jan 29  2022 test.html
> >
> >
> > To the best of my knowledge, the software is up to date:
> >
> > $ sudo freshclam -V
> > ClamAV 0.103.8/26825/Mon Feb 27 08:24:38 2023
> >
> >
> > Here is the freshclam.conf used on all the local sanner instances
> >
> > $ cat /etc/clamav/freshclam.conf
> > # Automatically created by the clamav-freshclam postinst
> > # Comments will get lost when you reconfigure the clamav-freshclam
> package
> >
> > DatabaseOwner clamav
> > UpdateLogFile /var/log/clamav/freshclam.log
> > LogVerbose false
> > LogSyslog false
> > LogFacility LOG_LOCAL6
> > LogFileMaxSize 0
> > LogRotate true
> > LogTime true
> > Foreground false
> > Debug false
> > MaxAttempts 5
> > DatabaseDirectory /var/lib/clamav
> > DNSDatabaseInfo current.cvd.clamav.net  
> >
> > ConnectTimeout 30
> > ReceiveTimeout 0
> > TestDatabases yes
> > CompressLocalDatabase no
> > Bytecode true
> > NotifyClamd /etc/clamav/clamd.conf
> > # Check for new database 24 times a day
> > Checks 24
> > PrivateMirror http://10.50.0.2
> 
> > ScriptedUpdates no
> > PrivateMirror http://10.50.0.2
> 
> >
> >
> > The scanner has been working fine for about 12 months, keeping the
> software and the definitions up to date.   The only configuration item that
> seems to relate is "Bytecode 

[clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

[Kevin O'Connor via clamav-users]

I am having an issue with 0 length bytecode.cvd files on my scanner
instances.  This seems to have started sometime on 22 Feb, I'm afraid I
don't have an exact time.  The clamav daemon produces logs like the
following:

Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error: cli_cvdverify:
Can't read CVD header
Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error: Can't load
/var/lib/clamav/bytecode.cld: Broken or not a CVD file
Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error:
cli_loaddbdir(): error loading database /var/lib/clamav/bytecode.cld
Feb 27 14:39:11 av-scan-wrhn clamd[163614]: Mon Feb 27 14:39:11 2023 ->
!Broken or not a CVD file
Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Main
process exited, code=exited, status=1/FAILURE
Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Failed with
result 'exit-code'.
Feb 27 14:39:11 av-scan-wrhn systemd[1]: clamav-daemon.service: Consumed
8.679s CPU time.


I feel like I have narrowed the problem down to a 0 length 'bytecode.cvd'
file.  Here is a listing of the definitions directory:

$ ls -l /var/lib/clamav
total 226168
-rw-r--r-- 1 clamav clamav314802 Feb 27 14:06 bytecode.cld
-rw-r--r-- 1 clamav clamav 0 Feb 27 02:00 bytecode.cvd
-rw-r--r-- 1 clamav clamav  60787973 Feb 27 10:01 daily.cld
-rw-r--r-- 1 clamav clamav69 Feb 23 15:33 freshclam.dat
-rw-r--r-- 1 clamav clamav 170479789 Feb 27 02:00 main.cvd


My initial fix (before narrowing the problem down to bytecode.cvd) was to

   1. stop freshclam
   2. clean this directory
   3. restart freshclam
   4. give it time to get the definitions (from a private mirror)
   5. start clamav daemon

This would work for maybe 1/2 day then the empty bytecode.cvd file would
reappear and the daemon would fail.

This morning I was able to spend some more time and find that it was just
the one file that needed to be removed.

I have a local mirror because there are several instances of this scanner
in use (at least 2 instances for several environments).  I have checked the
mirror and it appears to be working fine and keeping the definitions up to
date inside our environment.  In addition, the scanner instances appear to
be keeping the local set of definitions up to date with the mirror.

The mirror does not have a bytecode.cvd file on it (here is a listing of
its definitions directory)

$ ls -l /var/lib/clamav
total 226172
-rw-r--r-- 1 clamav clamav314802 Feb 22 22:02 bytecode.cld
-rw-r--r-- 1 clamav clamav  60787973 Feb 27 09:06 daily.cld
-rw-r--r-- 1 clamav clamav69 Jan 29  2022 freshclam.dat
-rw-r--r-- 1 clamav clamav 170479789 Jan 29  2022 main.cvd
-rw-r--r-- 1 clamav clamav87 Jan 29  2022 test.html


To the best of my knowledge, the software is up to date:

$ sudo freshclam -V
ClamAV 0.103.8/26825/Mon Feb 27 08:24:38 2023


Here is the freshclam.conf used on all the local sanner instances

$ cat /etc/clamav/freshclam.conf
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package

DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
LogRotate true
LogTime true
Foreground false
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 30
ReceiveTimeout 0
TestDatabases yes
CompressLocalDatabase no
Bytecode true
NotifyClamd /etc/clamav/clamd.conf
# Check for new database 24 times a day
Checks 24
PrivateMirror http://10.50.0.2
ScriptedUpdates no
PrivateMirror http://10.50.0.2


The scanner has been working fine for about 12 months, keeping the software
and the definitions up to date.   The only configuration item that seems to
relate is "Bytecode true", but the description seems to discuss just the
downloading of the file, not whether it is created on the local instance.

Does anyone have any pointers?

Thanks
Kevin
-- 

*Kevin O'Connor*
Principal DevOps Engineer
M: 617-834-1291

[image: email-footer-logos.jpg (1000×120)]

STATEMENT OF CONFIDENTIALITY: The information contained in this message and
any attachments are intended solely for the addressee(s) and may contain
confidential or privileged information. If you are not the intended
recipient, or responsible for delivering the e-mail to the intended
recipient, you have received this message in error. Any use, dissemination,
forwarding, printing, or copying is strictly prohibited. Please notify
Ampion immediately at secur...@ampion.net and destroy all copies of this
message and any attachments.
___

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat