[clamav-users] clamav

2019-11-13 Thread ALMOKBEL, RAWAN
Good Day! I have a question regarding clamav scan, Does clamav scan embedded virus and malicious inside files ? Kind regards, This Email and any files transmitted may contain confidential and/or privileged information and is intended solely for the addressee(s)

Re: [clamav-users] [ext] SelfCheck: Database modification detected. Forcing reload.

2019-11-13 Thread Ralf Hildebrandt via clamav-users
* Cliff Hayes via clamav-users : > I have a daily cron job that runs around 3am that: > - shuts down clamd > - runs freshclam > - starts clamd Why? freshclam usually runs all the time, updating and signalling clamd on demand. But you do have a point... Ralf Hildebrandt Charité -

Re: [clamav-users] SelfCheck: Database modification detected. Forcing reload.

2019-11-13 Thread Orion Poplawski
freshclam-sleep is Fedora's method of automatically updating the signatures. If you want to update it your way, feel free to disable it. BTW - you don't need to shutdown clamd to update the signatures. On 11/13/19 7:17 PM, Cliff Hayes via clamav-users wrote: I have more information. Turns

Re: [clamav-users] Use of clamav-daemon.socket? (0.102.0)

2019-11-13 Thread Orion Poplawski
On 11/9/19 2:46 AM, Frans de Boer wrote: LS, I use several machines and found that most of the time the use of the 'clamav-daemon.socket' file only leads to a startup failure of clamd. Why is this file file in the first place? I ask this because clamd is already creating the socket - that

Re: [clamav-users] SelfCheck: Database modification detected. Forcing reload.

2019-11-13 Thread Cliff Hayes via clamav-users
I have more information. Turns out there is a cron job I was unaware of. freshclam-sleep is running every 3 hours. Apparently, freshclam-sleep does something that freshclam doesn't and causes a database update. Do I need to run freshclam and freshclam-sleep? Can I turn off the freshclam-sleep

[clamav-users] SelfCheck: Database modification detected. Forcing reload.

2019-11-13 Thread Cliff Hayes via clamav-users
Hello clamd mailing list, I recently installed clamav version 0.101.4-1.fc30 on Fedora 30. A new situation I have never seen has started. Every day around 5am clamd causes a problem. I traced it to this in logs: SelfCheck: Database modification detected. Forcing reload. I have a daily cron job

Re: [clamav-users] clamav-milter and ClamdSocket tcp with multi-host A record

2019-11-13 Thread Matus UHLAR - fantomas
On 13.11.19 11:21, Chris Conn wrote: I am trying to use the ClamdSocket tcp: and am successfully connecting to port 3310 of a clamd daemon on remote hosts to scan using clamav-milter. The hostname I configured points to a pool ClamdSocket tcp:mypool.mydomain.com this resolves to 4 IP

Re: [clamav-users] Html.Malware.Agent-7380889-0 false positive on Apache files?

2019-11-13 Thread Christina Qian
Hi Al, Thank you very much for your reply. I just realized that I was on the wrong thread though. I meant to ask the reason for the alarms below, or at least to confirm it's a false alarm, so I can just exclude the files. Do you or anybody on the list has information on this? Thanks. Christina

[clamav-users] clamav-milter and ClamdSocket tcp with multi-host A record

2019-11-13 Thread Chris Conn
Hello, I am trying to use the ClamdSocket tcp: and am successfully connecting to port 3310 of a clamd daemon on remote hosts to scan using clamav-milter. The hostname I configured points to a pool ClamdSocket tcp:mypool.mydomain.com this resolves to 4 IP addresses I am surprised to see

Re: [clamav-users] Problem running virus scanner: code=999, category=cannot-execute, action=tempfail

2019-11-13 Thread G.W. Haywood via clamav-users
Hi there, On Wed, 13 Nov 2019, Andrew Watkins via clamav-users wrote: On 11/13/19 10:33 AM, G.W. Haywood via clamav-users wrote: Perhaps clamd is reloading its databases when you see this. Depending on configuration and the host performance it can take anywhere between a few tens of seconds

Re: [clamav-users] Problem running virus scanner: code=999, category=cannot-execute, action=tempfail

2019-11-13 Thread Andrew Watkins via clamav-users
On 11/13/19 10:33 AM, G.W. Haywood via clamav-users wrote: Perhaps clamd is reloading its databases when you see this. Depending on configuration and the host performance it can take anywhere between a few tens of seconds and several minutes to reload all the databases, and during that time

Re: [clamav-users] Problem running virus scanner: code=999, category=cannot-execute, action=tempfail

2019-11-13 Thread Andrew Watkins via clamav-users
On 11/13/19 10:26 AM, Reio Remma via clamav-users wrote: On 13/11/2019 12:19, Andrew Watkins via clamav-users wrote: Check if it's coinciding with clamd reloading its databases. Clamd currently doesn't scan when reloading databases. Look for: Nov 13 11:37:04 clamd clamd[15795]: SelfCheck:

Re: [clamav-users] Problem running virus scanner: code=999, category=cannot-execute, action=tempfail

2019-11-13 Thread G.W. Haywood via clamav-users
Hi there, On Wed, 13 Nov 2019, Andrew Watkins via clamav-users wrote: I get the following error a few times a day for a while, so I thought I would look into it. I am using mimedefang to send mail to clamd and it works fine, but at random point of the day I get the error:

Re: [clamav-users] Problem running virus scanner: code=999, category=cannot-execute, action=tempfail

2019-11-13 Thread Reio Remma via clamav-users
On 13/11/2019 12:19, Andrew Watkins via clamav-users wrote: Hello, I get the following error a few times a day for a while, so I thought I would look into it. I am using mimedefang to send mail to clamd and it works fine, but at random point of the day I get the error:

[clamav-users] Problem running virus scanner: code=999, category=cannot-execute, action=tempfail

2019-11-13 Thread Andrew Watkins via clamav-users
Hello, I get the following error a few times a day for a while, so I thought I would look into it. I am using mimedefang to send mail to clamd and it works fine, but at random point of the day I get the error: mimedefang.pl[26234]:  xAD8PbeZ009878: Timeout reading from clamd daemon at