Koozali.org: home of the SME Server

Error starting clamd

Bradster

Error starting clamd
« on: August 12, 2004, 07:51:19 PM »
Hello everybody,

This problem has pleagued me for over a month and me and my limited SME skills would apprecieate anybody's suggestion before I perform a re-install.

Here is the error:
Starting clamd: ERROR: Can't open/parse the config file /etc/clamav.conf

The clamav.conf file is empty

Thanks in advance.

Bradster[/i]

mbachmann

Error starting clamd
« Reply #1 on: August 16, 2004, 01:03:08 PM »
Look into directory, search clamav.conf, view contents with editor. Mine is about 7 KB. If it is not there, uninstall, reinstall. You can use scripts from

http://www.pagefault.org/ or http://sme.swerts-knudsen.dk/.

Bradster

Error starting clamd
« Reply #2 on: August 17, 2004, 05:48:15 AM »
I think we're almost there...

I deleted the clamd.conf and re-installed.  I no longer have errors loading the clamd service, additionally; I don't have any errors running any test on the ClamAv for dummies article:
http://sme.swerts-knudsen.dk/index.html

Now my SMTP server hangs and when I tail the amavis-ng.log file; this is what I see.

Aug 16 18:39:43 mail amavis[3460]: Starting AMaViS 0.1.6.4
Aug 16 18:39:43 mail amavis[3463]: Starting AMaViS 0.1.6.4
Aug 16 18:39:44 mail amavis[3464]: Starting AMaViS 0.1.6.4
Aug 16 18:39:46 mail amavis[3465]: Starting AMaViS 0.1.6.4
Aug 16 18:40:00 mail amavis[3481]: Starting AMaViS 0.1.6.4
Aug 16 18:40:01 mail amavis[3484]: Starting AMaViS 0.1.6.4
Aug 16 18:40:22 mail amavis[3492]: Starting AMaViS 0.1.6.4
Aug 16 18:40:39 mail amavis[3499]: Starting AMaViS 0.1.6.4
Aug 16 18:40:44 mail amavis[3504]: Starting AMaViS 0.1.6.4
Aug 16 18:40:45 mail amavis[3508]: Starting AMaViS 0.1.6.4


Anybody else have this problem???

mbachmann

Error starting clamd
« Reply #3 on: August 17, 2004, 05:13:15 PM »
Reboot the machine?
Disable amavis, look if SMTP is working and vice versa?
I have not seen this before. amavis-ng.log reads like this

Aug 17 16:35:04 nautilus1 amavis[18031]: Starting AMaViS 0.1.6.4
Aug 17 16:35:05 nautilus1 amavis[18031]: Unpacking message in /var/spool/amavis-ng/amavis-unpack-41221799-466f
Aug 17 16:35:05 nautilus1 amavis[18031]: AMAVIS: Determined 00000000 to be type message/rfc822
Aug 17 16:35:05 nautilus1 amavis[18031]: AMAVIS: Determined 00000001 to be type text/plain
Aug 17 16:35:05 nautilus1 amavis[18031]: Not attempting to unpack 00000001
Aug 17 16:35:05 nautilus1 amavis[18031]: AMAVIS::MTA::Qmail: Accepting message
Aug 17 16:35:24 nautilus1 amavis[18031]: AMAVIS::MTA::Qmail: /var/qmail/bin/qmail-spamc exited: 0
Aug 17 16:35:24 nautilus1 amavis[18031]: AMAVIS: Cleaning up.
Aug 17 16:35:24 nautilus1 amavis[18031]: AMAVIS: Done.

Bradster

Error starting clamd
« Reply #4 on: August 18, 2004, 05:33:32 PM »
My smtp server died but came back online after manually disabling the antivirus.

I ran the Manuall Installation test and here are the results:
[root@mail root]# ps -efa | grep clamd
qmailq    2799     1  0 09:34 ?        00:00:00 clamd


[root@mail root]# ls -ld /var/lib/clamav
drwx------    2 qmailq   qmail        4096 Aug 18 09:34 /var/lib/clamav

[root@mail root]# tail /var/log/amavis-ng/amavis-ng.log
Aug 18 09:39:56 mail amavis[3070]: Starting AMaViS 0.1.6.4
Aug 18 09:39:57 mail amavis[3073]: Starting AMaViS 0.1.6.4
Aug 18 09:40:07 mail amavis[3075]: Starting AMaViS 0.1.6.4
Aug 18 09:40:17 mail amavis[3083]: Starting AMaViS 0.1.6.4
Aug 18 09:40:19 mail amavis[3084]: Starting AMaViS 0.1.6.4
Aug 18 09:40:26 mail amavis[3086]: Starting AMaViS 0.1.6.4
Aug 18 09:40:55 mail amavis[3093]: Starting AMaViS 0.1.6.4
Aug 18 09:41:33 mail amavis[3104]: Starting AMaViS 0.1.6.4
Aug 18 09:41:34 mail amavis[3106]: Starting AMaViS 0.1.6.4
Aug 18 09:41:59 mail amavis[3126]: Starting AMaViS 0.1.6.4


All of the Perl test worked ok.

Does this help?

Thanks,
Bradster

mbachmann

Error starting clamd
« Reply #5 on: August 18, 2004, 06:04:55 PM »
I'm stuck on this. Try

service clamd stop
cd /var/lib/clamav/
rm clamd.sock (or mv clamd.sock clamd.sock.old)
service clamd start

look at the permissions of clamd.sock before and after clamd stop/start.

Last resort: /sbin/e-smith/signal-event post-upgrade
reboot