Something's not right on my new server.

Forum for getting help with Project Gamera, Spamassassin, Clamav, qmail-scanner and other anti-spam tools.
carliebentley
Forum User
Forum User
Posts: 46
Joined: Mon Oct 09, 2006 5:32 pm

Something's not right on my new server.

Unread post by carliebentley »

This is a CentOS 5 server running Plesk 8.3, with the atomic qmailscanner, et al.

Here's what my log is firing out:
Tue, 18 Mar 2008 16:35:14 CDT:3727: ------ Process 3727 finished. Total of 0.016835 secs
Tue, 18 Mar 2008 16:35:17 CDT:3780: +++ starting debugging for process 3780 (ppid=3772) by uid=2020
Tue, 18 Mar 2008 16:35:17 CDT:3780: w_c: Total time between DATA command and "." was 0.000175 secs
Tue, 18 Mar 2008 16:35:17 CDT:3780: w_c: elapsed time from start 0.000113 secs
Tue, 18 Mar 2008 16:35:17 CDT:3780: g_e_h: return-path='GMC@email.gmc.bfi0.com', recips='aaron@theinstallgroup.com'
Tue, 18 Mar 2008 16:35:17 CDT:3780: from='The Professionals at GMC <GMC@email.gmc.bfi0.com>', subj='Your GMC: Monthly Update', via SMTP from 216.33.63.75
Tue, 18 Mar 2008 16:35:17 CDT:3780: s_p_d: /var/spool/qscan/settings_per_domain.db doesn't exist falling to installed scanners
Tue, 18 Mar 2008 16:35:17 CDT:3780: error_condition: X-Qmail-Scanner-2.01st: clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem - exit status 512/2

There's obviously something wrong.

Any suggestions?
scott
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin
Posts: 8355
Joined: Wed Dec 31, 1969 8:00 pm
Location: earth
Contact:

Unread post by scott »

check to make sure clamd is running
carliebentley
Forum User
Forum User
Posts: 46
Joined: Mon Oct 09, 2006 5:32 pm

Part of the problem identified.

Unread post by carliebentley »

Okay, I found part of the problem was that the clamd.log wasn't created and didn't have the proper permissions set.

That got the clamd running without error.
carliebentley
Forum User
Forum User
Posts: 46
Joined: Mon Oct 09, 2006 5:32 pm

Unread post by carliebentley »

Apparently the server was holding all of the mail until it could scan it with clamd. It caused a pretty significant delay in processing the mail.

Now that clamd is running properly it seems to be filtering through now.
Thanks Scott, for your (as usual) prompt replies.
Post Reply