Re: [clamav-users] clamav-daemon do not start after upgrade

Hello guys, Thanks for the reply The problem is solved. the file /etc/group was on a 640 mode and the clamd process could not open it. After changing the mode to 644, the process has started. Regards - On 25 Mar, 2022, at 18:06, clamav-users wrote: > Hi there, > On Fri, 25 Mar 2022

Re: [clamav-users] clamav-daemon do not start after upgrade

Hi there, On Fri, 25 Mar 2022, Jean-Claude VERGEROLLE wrote: After an apt upgrade, clamav-daemon do not start System : debian buster 4.19.232-1 clamav version : 0.103.5+dfsg-0+deb10u1 amd64 I got this in the log /var/log/clamav/clamav.log ... ... Fri Mar 25 13:00:11 2022 -> ERROR: Unknown gro

[clamav-users] clamav-daemon do not start after upgrade

Hello guys, After an apt upgrade, clamav-daemon do not start System : debian buster 4.19.232-1 clamav version : 0.103.5+dfsg-0+deb10u1 amd64 I got this in the log /var/log/clamav/clamav.log Fri Mar 25 12:59:43 2022 -> +++ Started at Fri Mar 25 12:59:43 2022 Fri Mar 25 12:59:43 2022 -> Rec

Re: [clamav-users] clamav-daemon crashing periodically

Hi, Thanks for your kind message. Indeed it looks as an issue related to RAM. Reading Freshclam logs all issues came exactly at that moment when a new DB started to be processed. Very well explained. *** I sent this message days ago, but I used the wrong account and it was returned recently

Re: [clamav-users] clamav-daemon crashing periodically

Hi, Thanks for your kind message. Indeed it looks as an issue related to RAM. Reading Freshclam logs all issues came exactly at that moment when a new DB started to be processed. Very well explained. *** I sent this message days ago, but I used the wrong account and it was returned recently

Re: [clamav-users] clamav-daemon crashing periodically

Hi there, On Wed, 3 Jun 2020, Stefan Bauer via clamav-users wrote: Am Mi., 3. Juni 2020 schrieb Jesus Arnaiz via clamav-users > It normally works fine, but, apparently it is crashing everyday more > than once, meaning a manual restart is needed once or twice per day. > > I don't see anything re

Re: [clamav-users] clamav-daemon crashing periodically

Check 'dmesg' and look for OOM-killer. Clamav needs a descend amount of RAM - especially when using 3rd-party signatures. As there are random updates over the day, the reloads could lead to your noticed behavior. Am Mi., 3. Juni 2020 um 10:00 Uhr schrieb Jesús Arnáiz via clamav-users < clamav-user

[clamav-users] clamav-daemon crashing periodically

Hi! I have an Ubuntu server as email server. I use there, MailInABox: https://mailinabox.email/ I installed on my own (since it is not part of MailInABox) clamav and I configured it to be used with clamsmtp on postfix, so email is scanned for virus. It normally works fine, but, apparently it

Re: [clamav-users] ClamAV Daemon Log - Filepath of the infected file

On 19.09.19 18:57, Jorge Martins wrote: I Was running like this: clamdscan /home/ --infected --multiscan --fdpass After some testing I noticed that if I remove the --fdpass the filepath is correctly logged Thu Sep 19 18:27:22 2019 -> /home/test/eicar.txt: Eicar-Test-Signature(69630e4574ec679823

Re: [clamav-users] ClamAV Daemon Log - Filepath of the infected file

I Was running like this: clamdscan /home/ --infected --multiscan --fdpass After some testing I noticed that if I remove the --fdpass the filepath is correctly logged Thu Sep 19 18:27:22 2019 -> /home/test/eicar.txt: Eicar-Test-Signature(69630e4574ec6798239b091cda43dca0:69) FOUND I really don't u

Re: [clamav-users] ClamAV Daemon Log - Filepath of the infected file

Hi there, On Thu, 19 Sep 2019, Jorge Martins wrote: I have ClamAV Daemon installed, and if clamdscan detects something I get an entry log on the /var/log/clamav/clamav.log file, but that entry does not identify the infected file, it only shows something like this: Thu Sep 19 16:42:24 2019 -> f

[clamav-users] ClamAV Daemon Log - Filepath of the infected file

Hi, I have ClamAV Daemon installed, and if clamdscan detects something I get an entry log on the /var/log/clamav/clamav.log file, but that entry does not identify the infected file, it only shows something like this: Thu Sep 19 16:42:24 2019 -> fd[12]: Eicar-Test-Signature(44d88612fea8a8f36de82e1

Re: [clamav-users] Clamav daemon not found

Hi all, Thank you for your feedback. It seems that the issue is resolved now, here is what I did. I created the config file manually /etc/clamd.conf and started clamd from " /usr/sbin/clamd" (or reboot). Best regards On Mon, Jul 23, 2018 at 9:57 AM, tschmidt wrote: > Your issues appear to b

Re: [clamav-users] Clamav daemon not found

Your issues appear to be specific to the packages you're using. What exactly did you install? Which packages from which repo? Did you follow the instructions coming with those packages? Did you encounter any problems or peculiarities while doing so? Am 23.07.2018 um 10:04 schrieb Aziz: > Hi users,

Re: [clamav-users] Clamav daemon not found

Hi Mark, No, it seems different to me, I'm attaching the default clamsmtpd.conf . Here is a sample of the clamd.conf file Thanks On Mon, Jul 23, 2018 at 9:38 AM, wrote: > Hi Aziz, >

Re: [clamav-users] Clamav daemon not found

Hi Aziz, It looks like your clamd.conf might be called /etc/clamsmtpd.conf so crating a symbolic link to it would resolve the issue. Have a look at /etc/clamsmtpd.conf to confirm it looks like a clamd configuration file first. If it looks correct then the next thing to try would be: ln -s

Re: [clamav-users] Clamav daemon not found

Thanks Mark for your feedback. It seems that the file doesn't exist at all, here is the output : *[root@mail /]# find /etc -name "*clam*.conf" -print/etc/clamd.d/clamsmtp.conf/etc/freshclam.conf/etc/tnc/clamavimc.conf/etc/mail/clamav-milter.conf/etc/clamsmtpd.conf* BR On Mon, Jul 23, 201

Re: [clamav-users] Clamav daemon not found

One option to try, as root, run the command: find /etc -name "*clam*.conf" -print Most likely the file is in /etc/clamav Regards Mark. On 23/07/18 09:04, Aziz wrote: Hi users, I'm trying to install Clamav in my Centos 7 to use it with Postfix, however I can't get Clamav deamon cl

[clamav-users] Clamav daemon not found

Hi users, I'm trying to install Clamav in my Centos 7 to use it with Postfix, however I can't get Clamav deamon clamd to run, which is causing the following error : */var/run/clamd.amavisd/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamd.amavisd/clamd.sock: Connection

[clamav-users] clamav-daemon start stuck in a loop

This is clamav 0.99.4+addedllvm-0ubuntu0.16.04.1 amd64 on Ubuntu 16.04.4 LTS.  This morning I updated via system updates to the above version. After the update I stopped the clamav-daemon and restarted via  sudo /etc/init.d/clamav-daemon start [ ok ] Starting clamav-daemon (via systemctl): clamav

Re: [clamav-users] Clamav daemon quitting unexpectedly

Hi Added the debug option I have noticed that when the daemon stops these lines appear in the syslog: Jun 15 10:51:39 merzariotz clamd[17048]: LibClamAV debug: [Bytecode JIT]: emitted function bc54f0 of 448 bytes at 0x7f5279bff170 Jun 15 10:51:39 merzariotz clamd[17048]: LibClamAV debug: [Byteco

Re: [clamav-users] Clamav daemon quitting unexpectedly

Thanks. I'll give it a go. I have added swap space today and this seems to have sorted the issue. Could this be the cause? Fabrizio Mazzoni. IT/Database/Programmer Consultant. +255 755 46 88 26 www.fsm.co.tz > On 14 Jun 2017, at 18:36, Steven Morgan wrote: > > Hi, > > Try adding "D

Re: [clamav-users] Clamav daemon quitting unexpectedly

Hi, Try adding "Debug true" to clamd.conf. It may provide some insight into what is going on. Steve On Wed, Jun 14, 2017 at 2:08 AM, Fabrizio Mazzoni wrote: > Good Morning too all! > > I’m having an issue whereas clamp is quitting unexpectedly and I have no > clue what is causing this. There

[clamav-users] Clamav daemon quitting unexpectedly

Good Morning too all! I’m having an issue whereas clamp is quitting unexpectedly and I have no clue what is causing this. There is not trace in the logs. I had thought it was due to space issues in /tmp as my tmp is only 500MB and it was full of clam files. I changed the clams.conf to read:

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Noel Jones-2 wrote: > > On 4/22/2010 10:51 AM, Thomas Herzog wrote: >> >> >> >> Török Edwin wrote: >>> >>> On 04/22/2010 10:24 AM, Török Edwin wrote: > lxhv1m02:~# grep ctl /etc/amavis/conf.d/15-av_scanners > \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"], >>> >>> You

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Noel Jones wrote: Clam must scan the whole email message because (as you know) some signatures only trigger on files that look like a mail message. To have both attachment blocking and full email scanning, the mail ends up being scanned twice. Maybe I'll put in a request for a "don't scan

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On 4/22/2010 12:30 PM, aCaB wrote: Paul Whelan wrote: I think your amavis tried to decode the message, and pass only parts of it to ClamAV. In general then, clamav may only recognise some malware when it is still attached to a mail message and not after it has been separately stored. Is that

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Paul Whelan wrote: >> I think your amavis tried to decode the message, and pass only parts of >> it to ClamAV. > > In general then, clamav may only recognise some malware when it is > still attached to a mail message and not after it has been > separately stored. Is that correct? It may or ma

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On 22 Apr 2010 at 12:06, Török Edwin wrote: > You need to tell amavis to pass the entire message to ClamAV, try: > $bypass_decode_parts = 1; > > I think your amavis tried to decode the message, and pass only parts of > it to ClamAV. In general then, clamav may only recognise some malware when

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On 4/22/2010 10:51 AM, Thomas Herzog wrote: Török Edwin wrote: On 04/22/2010 10:24 AM, Török Edwin wrote: lxhv1m02:~# grep ctl /etc/amavis/conf.d/15-av_scanners \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"], You need to tell amavis to pass the entire message to ClamAV,

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On 04/22/2010 06:51 PM, Thomas Herzog wrote: > > > > Török Edwin wrote: >> >> On 04/22/2010 10:24 AM, Török Edwin wrote: lxhv1m02:~# grep ctl /etc/amavis/conf.d/15-av_scanners \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"], >> >> You need to tell amavis to pass the ent

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Török Edwin wrote: > > On 04/22/2010 10:24 AM, Török Edwin wrote: >>> lxhv1m02:~# grep ctl /etc/amavis/conf.d/15-av_scanners >>>\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"], > > You need to tell amavis to pass the entire message to ClamAV, try: > $bypass_decode_parts = 1; >

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Török Edwin wrote: > > On 04/22/2010 10:24 AM, Török Edwin wrote: >>> lxhv1m02:~# grep ctl /etc/amavis/conf.d/15-av_scanners >>>\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"], > > You need to tell amavis to pass the entire message to ClamAV, try: > $bypass_decode_parts = 1; >

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Török Edwin wrote: > > On 04/22/2010 10:01 AM, Thomas Herzog wrote: >> >> Amavis seems to be calling the clam deamon, it finds also some other >> exploits, viruses... >> /var/log/clamav/clamav.log: >> Thu Apr 22 08:15:07 2010 -> /tmp/UPS_invoice_4557.zip: >> Suspect.Bredozip-zippwd-5 FOUND >

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On 04/22/2010 10:24 AM, Török Edwin wrote: >> lxhv1m02:~# grep ctl /etc/amavis/conf.d/15-av_scanners >>\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"], You need to tell amavis to pass the entire message to ClamAV, try: $bypass_decode_parts = 1; I think your amavis tried to decode

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On 04/22/2010 10:01 AM, Thomas Herzog wrote: > > Amavis seems to be calling the clam deamon, it finds also some other > exploits, viruses... > /var/log/clamav/clamav.log: > Thu Apr 22 08:15:07 2010 -> /tmp/UPS_invoice_4557.zip: > Suspect.Bredozip-zippwd-5 FOUND BTW attachments are automatically r

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Rob MacGregor wrote: > > On Thu, Apr 22, 2010 at 07:16, Thomas Herzog > wrote: >> >> Thanks for your reply, just to get this right. >> The virus is detected by the binaries clamdscan or clamscan, but not by >> the >> deamon called through amavis -> see the attachment of my first post. > > The

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On Thu, Apr 22, 2010 at 07:16, Thomas Herzog wrote: > > Thanks for your reply, just to get this right. > The virus is detected by the binaries clamdscan or clamscan, but not by the > deamon called through amavis -> see the attachment of my first post. Then you have a problem with the way Amavis i

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Thomas Herzog wrote: > > > Rob MacGregor wrote: >> >> On Wed, Apr 21, 2010 at 16:02, Thomas Herzog >> wrote: >>> >>> Hello, >>> We're running clamav 0.95.3 with amavisd-new-2.6.1and postfix 2.5.5. >>> >>> Sending a message with a virus attached clamav-daemon didn't find it. -> >> >> http://w

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

Rob MacGregor wrote: > > On Wed, Apr 21, 2010 at 16:02, Thomas Herzog > wrote: >> >> Hello, >> We're running clamav 0.95.3 with amavisd-new-2.6.1and postfix 2.5.5. >> >> Sending a message with a virus attached clamav-daemon didn't find it. -> > > http://www.clamav.net/lang/en/sendvirus/ > > -

Re: [Clamav-users] clamav-daemon didn't recognise attached virus

On Wed, Apr 21, 2010 at 16:02, Thomas Herzog wrote: > > Hello, > We're running clamav 0.95.3 with amavisd-new-2.6.1and postfix 2.5.5. > > Sending a message with a virus attached clamav-daemon didn't find it. -> http://www.clamav.net/lang/en/sendvirus/ -- Please keep list traffi

[Clamav-users] clamav-daemon didn't recognise attached virus

Hello, We're running clamav 0.95.3 with amavisd-new-2.6.1and postfix 2.5.5. Sending a message with a virus attached clamav-daemon didn't find it. -> Please take a look at the attachment. When copying this msg onto the servre and scanning it manually withclamdscan or clamscan the Virus is found

Re: [Clamav-users] Clamav-users] Clamav daemon crashes after upgrading debian "Parse error at line 46:Unknown option PhishingScanURLs."

Thanks, I commented out the "Phishing" lines and it runs again. -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Tomasz Kojm Verzonden: dinsdag 12 februari 2008 12:34 Aan: clamav-users@lists.clamav.net Onderwerp: Re: [Clamav-users] Clamav-use

Re: [Clamav-users] Clamav-users] Clamav daemon crashes after upgrading debian "Parse error at line 46:Unknown option PhishingScanURLs."

On Tue, 12 Feb 2008 12:29:09 +0100 "Heskes, E.H. (Erik)" <[EMAIL PROTECTED]> wrote: > It's version 0.90.2-01 This version doesn't support PhishingScanURLs -- oo. Tomasz Kojm <[EMAIL PROTECTED]> (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._

Re: [Clamav-users] Clamav-users] Clamav daemon crashes after upgrading debian "Parse error at line 46:Unknown option PhishingScanURLs."

It's version 0.90.2-01 -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Tomasz Kojm Verzonden: dinsdag 12 februari 2008 11:07 Aan: clamav-users@lists.clamav.net Onderwerp: Re: [Clamav-users] Clamav-users] Clamav daemon crashes after upgrading debian &

Re: [Clamav-users] Clamav-users] Clamav daemon crashes after upgrading debian "Parse error at line 46:Unknown option PhishingScanURLs."

On Tue, 12 Feb 2008 10:33:35 +0100 "Heskes, E.H. (Erik)" <[EMAIL PROTECTED]> wrote: > After updating and upgrading debian packages and then restarting the > Clamav Daemon I get: > > /etc/init.d/clamav-daemon restart > Starting ClamAV daemon clamd ERROR: Parse error at line 46: Unknown > option P

Re: [Clamav-users] Clamav-users] Clamav daemon crashes after upgrading debian "Parse error at line 46:Unknown option PhishingScanURLs."

On Tue, 12 Feb 2008 10:33:35 +0100 "Heskes, E.H. (Erik)" <[EMAIL PROTECTED]> wrote: > After updating and upgrading debian packages and then restarting the > Clamav Daemon I get: > > /etc/init.d/clamav-daemon restart > Starting ClamAV daemon clamd ERROR: Parse error at line 46: Unknown > option P

[Clamav-users] Clamav-users] Clamav daemon crashes after upgrading debian "Parse error at line 46:Unknown option PhishingScanURLs."

After updating and upgrading debian packages and then restarting the Clamav Daemon I get: /etc/init.d/clamav-daemon restart Starting ClamAV daemon clamd ERROR: Parse error at line 46: Unknown option PhishingScanURLs. ERROR: Can't open/parse the config file /etc/clamav/clamd.conf I tried differen

Re: [Clamav-users] clamav daemon

Gareth wrote: now, but want to try using the daemon instead. I've looked at Page 7 in the ClamAV PDF, and found I need to edit /etc/clamav.conf, but this file doesn't even exist in my /.etc directory, nor anywhere on my system. Perhaps the documentation is outdated ... What ClamAV version are

[Clamav-users] clamav daemon

Hi Guys I've been using the ClamAV commandline scanner with AMaVIs for some time now, but want to try using the daemon instead. I've looked at Page 7 in the ClamAV PDF, and found I need to edit /etc/clamav.conf, but this file doesn't even exist in my /.etc directory, nor anywhere on my system.