1

Topic: Safe to remove @storage_sql_dsn from amavisd.conf?

==== Required information ====
- iRedMail version: Version 0.8.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx):apache
- Linux/BSD distribution name and version: centos 6.6
- Related log if you're reporting an issue:
====

http://www.iredmail.org/forum/topic7326 … mavis.html

Is it save to remove this directive, the cleanup process via:
/var/www/iredadmin/tools/cleanup_amavisd_db.py...

is causing lock wait timeouts in mysql and periodically causes it to crash. Instead of increasing the lockwait timout in mysql, i'd rather just stop logging these messages, however, if it affects scanning, I obviously can't do that.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Safe to remove @storage_sql_dsn from amavisd.conf?

BTW running /var/www/iredadmin/tools/cleanup_amavisd_db.py

Results in a table lock of around 11 minutes during the removal process.

3

Re: Safe to remove @storage_sql_dsn from amavisd.conf?

Dear amora,

I'm sorry about this trouble.

*) It's ok to disable '@storage_sql_dsn' and '@lookup_sql_dsn'.

*) The ideal solution is upgrading to the latest iRedAdmin-Pro, because script 'tools/cleanup_amavisd_db.py' is improved and it won't cause sql table lock at all. If you don't want to upgrade iRedAdmin-Pro, you can simply copy all files under 'tools/' directory in the latest iRedAdmin-Pro to the one you're currently running.

4

Re: Safe to remove @storage_sql_dsn from amavisd.conf?

Thanks! I might as well upgrade, I'm getting behind on updates anyway.