Clamav stopped working, to old database... freshclam missing ?

Johannes Johannes at kehrer.by
Thu Apr 21 18:50:45 CEST 2016 

Hello Thanks,
I tried to follow your instructions, however I didn' succeed.

Here is what I did/found:

Am 2016-04-21 15:43, schrieb Winfried Ritsch:
> Hello,
> 
> Did you see clamd at amavisd.service running ?
> 
>  # systemctl status -l clamd at amavisd.service

[root at mail ~]# systemctl status -l clamd at amavisd.service
● clamd at amavisd.service - clamd scanner (amavisd) daemon
    Loaded: loaded (/usr/lib/systemd/system/clamd at .service; static; 
vendor preset: disabled)
    Active: failed (Result: start-limit) since Mi 2016-04-20 21:37:06 
CEST; 20h ago
   Process: 2544 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf 
--nofork=yes (code=exited, status=1/FAILURE)
  Main PID: 2544 (code=exited, status=1/FAILURE)

Apr 20 21:37:05 mail.kehrer.cc systemd[1]: clamd at amavisd.service: main 
process exited, code=exited, status=1/FAILURE
Apr 20 21:37:05 mail.kehrer.cc systemd[1]: Unit clamd at amavisd.service 
entered failed state.
Apr 20 21:37:05 mail.kehrer.cc systemd[1]: clamd at amavisd.service failed.
Apr 20 21:37:06 mail.kehrer.cc systemd[1]: clamd at amavisd.service holdoff 
time over, scheduling restart.
Apr 20 21:37:06 mail.kehrer.cc systemd[1]: start request repeated too 
quickly for clamd at amavisd.service
Apr 20 21:37:06 mail.kehrer.cc systemd[1]: Failed to start clamd scanner 
(amavisd) daemon.
Apr 20 21:37:06 mail.kehrer.cc systemd[1]: Unit clamd at amavisd.service 
entered failed state.
Apr 20 21:37:06 mail.kehrer.cc systemd[1]: clamd at amavisd.service failed.



> 
> When yes  there should be the
> /var/run/clamd.amavisd/clamd.sock

Directory /var/run/clamd.amavisd/ is empty.

> 
> if not it is not st
>  # systemctl start clamd at amavisd.service

Performed, but no further output.

> yu
> should give you the error to old database.

No error shown. Empty commandline

> 
> After installing  clamav-update also enable freshclam  in 
> /etc/freshclam.conf:
>  # Comment or remove the line below.
>  #Example
> 

Done. Beginning of file is:
## Example config file for freshclam
## Please read the freshclam.conf(5) manual before editing this file.
##


# Comment or remove the line below.
# Example

# Path to the database directory.
# WARNING: It must match clamd.conf's directive!
# Default: hardcoded (depends on installation options)
#DatabaseDirectory /var/lib/clamav


> and restart. afterwards restart clamd at amavisd.service, if not done by
> supervisor.

I restarted the server. However, the output of " # systemctl status -l 
clamd at amavisd.service" is:
[root at mail ~]#  systemctl status -l clamd at amavisd.service
● clamd at amavisd.service - clamd scanner (amavisd) daemon
    Loaded: loaded (/usr/lib/systemd/system/clamd at .service; static; 
vendor preset: disabled)
    Active: failed (Result: start-limit) since Do 2016-04-21 18:36:01 
CEST; 1min 21s ago
   Process: 2596 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf 
--nofork=yes (code=exited, status=1/FAILURE)
  Main PID: 2596 (code=exited, status=1/FAILURE)

Apr 21 18:36:01 mail.kehrer.cc systemd[1]: clamd at amavisd.service: main 
process exited, code=exited, status=1/FAILURE
Apr 21 18:36:01 mail.kehrer.cc systemd[1]: Unit clamd at amavisd.service 
entered failed state.
Apr 21 18:36:01 mail.kehrer.cc systemd[1]: clamd at amavisd.service failed.
Apr 21 18:36:01 mail.kehrer.cc systemd[1]: clamd at amavisd.service holdoff 
time over, scheduling restart.
Apr 21 18:36:01 mail.kehrer.cc systemd[1]: start request repeated too 
quickly for clamd at amavisd.service
Apr 21 18:36:01 mail.kehrer.cc systemd[1]: Failed to start clamd scanner 
(amavisd) daemon.
Apr 21 18:36:01 mail.kehrer.cc systemd[1]: Unit clamd at amavisd.service 
entered failed state.
Apr 21 18:36:01 mail.kehrer.cc systemd[1]: clamd at amavisd.service failed.

The emails I receive are still marked "UNCHECKED".


MfG
    Johannes

> 
> mfg
>  winfried
> 
> 
> Am Mittwoch, 20. April 2016, 12:08:16 schrieb Stephen Switzer:
>> I too am having this issue after updating last night. I'm tempted to
>> backup my mail and rollback the VM.
>> 
>> After update, EVERY email is coming in with "***UNCHECKED***". I 
>> looked
>> at the logs and found many entries like this:
>> 
>> Apr 20 11:31:16 kolab16 amavis[9442]: (09442-17) (!)ClamAV-clamd: All
>> attempts (1) failed connecting to /var/run/clamd.amavisd/clamd.sock,
>> retrying (2)
>> Apr 20 11:31:22 kolab16 amavis[9442]: (09442-17) ClamAV-clamd:
>> Connecting to socket  /var/run/clamd.amavisd/clamd.sock, retry #2
>> Apr 20 11:31:22 kolab16 amavis[9442]: (09442-17) new socket by
>> IO::Socket::UNIX to /var/run/clamd.amavisd/clamd.sock, timeout set to 
>> 10
>> 
>> 
>> Directory listing shows it doesn't exist:
>> 
>> [root at kolab16 etc]# ls -l /var/run/clamd.amavisd/clamd.sock
>> ls: cannot access /var/run/clamd.amavisd/clamd.sock: No such file or
>> directory
>> [root at kolab16 etc]# ls -l /var/run/clamd.amavisd/
>> total 0
>> [root at kolab16 etc]#
>> 
>> 
>> These files seem to match:
>> 
>> [root at kolab16 etc]# grep -i clamd.sock /etc/amavisd/amavisd.conf
>>    \&ask_daemon, ["CONTSCAN {}\n", 
>> "/var/run/clamd.amavisd/clamd.sock"],
>> [root at kolab16 etc]# grep -i clamd.sock /etc/clamd.d/amavisd.conf
>> LocalSocket /var/run/clamd.amavisd/clamd.sock
>> [root at kolab16 etc]#
>> 
>> 
>> Nothing is running under clam:
>> 
>> [root at kolab16 etc]# ps -el | grep clam
>> [root at kolab16 etc]# ps -el | grep clam\|amavis
>> [root at kolab16 etc]#
>> 
>> 
>> clamav-update wasn't installed either. I tried to install it, and it 
>> was
>> no help.
>> 
>> Any help would be appreciated. If I can't figure it out by tonight, 
>> I'll
>> have to backup "/var/spool/imap/domain/" and rollback the VM and 
>> restore
>> - that additional subject is annoying! LOL
>> 
>> Thank you!
>> 
>> 
>> ---
>> Best regards,
>> 
>> STEPHEN H. SWITZER
>> 
>> On 2016-04-12 12:13 PM, Winfried Ritsch wrote:
>> > Hello,
>> >
>> > On an Kolab 16 and Centos 7, Installation on 2016-4-09 I did a yum
>> > update and
>> > afterwards all emails are reported as  "***UNCHECKED***" in subject.
>> >
>> > It showed clamd at amavisd does not start and reports "database more than
>> > 7 days
>> > old"
>> >
>> > Looking at issues I found:
>> > https://issues.kolab.org/show_bug.cgi?id=3996
>> >
>> >   "Running Kolab 16 and freshclam is still not provided"
>> >
>> > I installed freshclam and it worked again but on install told me:
>> >  [...]
>> >  ERROR: Corrupted database file /var/lib/clamav/main.cvd: Can't verify
>> >
>> > database integrity
>> >
>> >  Corrupted database file renamed to /var/lib/clamav/main.cvd.broken
>> >  [...]
>> >
>> > So my question is, since it worked  for a month:
>> >
>> > How has clam database been updated in Kolab 16 without freshclam before
>> > ?
>> >
>> > Did I something wrong installing freshclam by hand ?
>> >
>> > I just wanted to get sure it works before I post here and found some on
>> > german
>> > kolab list with same problem, but we didn't find any hints, anyway I am
>> >
>> >  not a
>> >
>> > kolab specialist.
>> >
>> >
>> > mfg
>> >
>> >  winfried
>> 
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users

More information about the users mailing list