[Maia-users] more errors in upgrade to 1.0.1

[Robert LeBlanc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Manuel Cabrera Caballero wrote:

> Nov 29 20:22:53 correopan amavis[18924]: (18924-08) WARN: all primary
> virus scanners failed, considering backups
> Nov 29 20:22:54 correopan amavis[18924]: (18924-08) ClamAV-clamscan
> av-scanner FAILED: run_command (open pipe): Can't fork at
> /usr/lib/perl5/5.8.5/i386-linux-thread-multi/IO/File.pm line 176. at
> /usr/local/sbin/amavisd line 1656.

> In my amavisd.conf
> 
> @av_scanners_backup = (
> 
>   ### http://www.clamav.net/   - backs up clamd or Mail::ClamAV
>   ['ClamAV-clamscan', 'clamscan',
>     "--stdout --disable-summary -r --tempdir=$TEMPBASE {}", [0], [1],
>     qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ],
> );

You probably want to use clamd as a primary scanner, and leave clamscan
as your backup scanner.  Add this to your amavisd.conf file:

  @av_scanners = (

  ### http://www.clamav.net/
  ['ClamAV-clamd',
     \&ask_daemon, ["CONTSCAN {}\n", "/var/amavisd/clamd.sock"],
     qr/\bOK$/, qr/\bFOUND$/,
     qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ],
  );

Note that the "/var/amavisd/clamd.sock" needs to be changed to point to
whatever value you set "LocalSocket" to in your clamd.conf and
clamav.conf files.

You must also remember that clamd and clamscan must be owned by your
amavis/maia user, and must run as that user so that the files they
create can be accessed properly by amavisd-maia.


> Another problem is that process-quarant raises the load of the server
> until the processes die.

You may need to fine-tune your database to improve its performance.
It's normal for the process-quarantine script to put a strain on your
database, but you can minimize that strain somewhat by ensuring that
your database has lots of RAM, processing power, and multiple disks to
stripe its data across, and that it has been tuned with your hardware
and this application in mind.

As I mentioned in another thread recently, if you're using MySQL you may
want to experiment with the innodb_buffer_pool_size setting.  On a
dedicated database server host you might set this as high as 80% of your
system RAM.  On systems where the database must share RAM with other
processes you might still be able to use 30% or 40% of the RAM without
harming other applications.  Clearly a dedicated database server host is
preferred, particularly if you have a high mail volume to process;
trying to host everything on one machine is only a solution for
relatively low mail volume.

- --
Robert LeBlanc <rjl at renaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamailguard.com/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFcCRfGmqOER2NHewRArnKAKCj2Du7ZPoabloTIYmGCWEC/eedHwCfbo9P
4gdlYhMpjmOCL2+5kvAANVc=
=BcBV
-----END PGP SIGNATURE-----