Peter Rabbitson wrote:
Hello all,
This is not strictly a DBMail question, but it is close. Lately I
noticed that any time the SQL server needs to be restarted for some
reason, DBMail starts having problems with inserting messages. Since the
error message was changed to 450 from 503, this is not a big issue, as
mail is not lost. Nevertheless I want to know if someone else had such
problems and what steps if any were taken to solve them.
The situation is as follows. Under Debian the mysql init script runs the
following upon the start of the daemon:
/usr/bin/mysqlcheck --defaults-file=/etc/mysql/debian.cnf
--all-databases --fast --silent
This process is pretty resource intensive and causes the following to
happen in DBMail from time to time:
Jul 20 09:29:23 Arzamas dbmail-lmtpd[2954]: Error:[sql]
dbmysql.c,db_query(+293): [Lock wait timeout exceeded; try restarting
transaction] [INSERT INTO dbmail_messageblks (is_header,
messageblk,blocksize, physmessage_id) VALUES (_omitted_)]
I got this every time I restarted the mysql server on a dbmail host.
You can tune the timeout involved
/etc/mysql/my.cnf: innodb_lock_wait_timeout
But my choice would be to disable the check run.
My question is - should I try to fix this at all? Is the mysqlcheck
process useful at all or should I disable it on startup? Or can I tune
some timeouts within dbmail?
Any input would be appreciated.
Thanks
Peter
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
