When I run my dbmail-util -ay weekly, I get a result laced with warnings about the DB taking too long as seen below. Is there a way to disable this, or increase the amount of seconds at which the warning is triggered? DBMail is 2.10
Thanks ====================== Repairing DBMAIL messageblocks integrity... Ok. Found [0] unconnected messageblks. Repairing DBMAIL physmessage integrity... Ok. Found [0] unconnected physmessages. Repairing DBMAIL message integrity... Ok. Found [0] unconnected messages. Repairing DBMAIL mailbox integrity... Ok. Found [0] unconnected mailboxes. Repairing DBMAIL for NULL messages... Ok. Found [0] NULL messages. Checking DBMAIL for NULL physmessages... Sep 24 04:03:53 Arzamas dbmail-util[7779]: Message:[db] dbmodule.c,db_query(+149): slow query [SELECT pm.id FROM dbmail_physmessage pm LEFT JOIN dbmail_messageblks mbk ON pm.id = mbk.physmessage_id WHERE mbk.physmessage_id is NULL] took [22] seconds Ok. Found [0] physmessages without messageblocks. Deleting messages with DELETE status... Ok. [3591] messages deleted. Repairing DBMAIL for rfcsize field... Ok. Found [0] missing rfcsize values. Repairing DBMAIL for incorrect is_header flags... Sep 24 04:16:29 Arzamas dbmail-util[7779]: Message:[db] dbmodule.c,db_query(+149): slow query [SELECT MIN(messageblk_idnr),MAX(is_header) FROM dbmail_messageblks GROUP BY physmessage_id HAVING MAX(is_header)=0] took [654] seconds Sep 24 04:16:29 Arzamas dbmail-util[7779]: Warning:[db] dbmodule.c,db_query(+151): slow query [SELECT MIN(messageblk_idnr),MAX(is_header) FROM dbmail_messageblks GROUP BY physmessage_id HAVING MAX(is_header)=0] took [654] seconds Ok. Found [0] incorrect is_header flags. Repairing DBMAIL for cached envelopes... Ok. Found [0] missing envelope values. Repairing DBMAIL for cached header values... Sep 24 04:16:58 Arzamas dbmail-util[7779]: Message:[db] dbmodule.c,db_query(+149): slow query [SELECT p.id FROM dbmail_physmessage p LEFT JOIN dbmail_headervalue h ON p.id = h.physmessage_id WHERE h.physmessage_id IS NULL] took [21] seconds Ok. Found [0] un-cached physmessages. Setting DELETE status for deleted messages... Ok. [6908] messages set for deletion. Re-calculating used quota for all users... Ok. Used quota updated for all users. Removing aliases with nonexistent delivery userid's... Ok. Found [0] dangling aliases. Vacuuming and optimizing database... Ok. Database cleaned up. Maintenance done. No errors found. _______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
