The following issue has been RESOLVED. ====================================================================== http://dbmail.org/mantis/view.php?id=486 ====================================================================== Reported By: zak Assigned To: aaron ====================================================================== Project: DBMail Issue ID: 486 Category: Database layer Reproducibility: always Severity: minor Priority: normal Status: resolved target: Resolution: fixed Fixed in Version: 2.2.4 ====================================================================== Date Submitted: 07-Jan-07 21:07 CET Last Modified: 02-May-07 00:59 CEST ====================================================================== Summary: Many duplicate key errors from MySQL running "dbmail-util -by" Description: I have just attempted an upgrade from dbmail 2.0.11 to 2.2.1 on a fairly low-volume system, and (after running the migrate_from_2.0_to_2.2.mysql.gz script) I now get the lots of the following errors every time I run "dbmail-util -by":
... Error insert datefield failed [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (1976,'1970-01-01 00:00:00')] .Error [Duplicate entry '1975-1970-01-01 00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (1975,'1970-01-01 00:00:00')] Error insert datefield failed [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (1975,'1970-01-01 00:00:00')] .Error [Duplicate entry '1974-1970-01-01 00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (1974,'1970-01-01 00:00:00')] Error insert datefield failed [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (1974,'1970-01-01 00:00:00')] .Error [Duplicate entry '1973-1970-01-01 00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (1973,'1970-01-01 00:00:00')] ... All the dates are '1970-01-01 00:00:00'. However, the IMAP daemon has started and appears to be functioning fine. I'm using MySQL 4.1.21. I'm not sure what additional information might be useful in tracking this down, but I'm happy to provide any that is likely to help. ====================================================================== ---------------------------------------------------------------------- aaron - 19-Jan-07 02:50 ---------------------------------------------------------------------- Dump out a couple of messages and their respective messageblks and attach them to the bug. The first easiest thing will be to re-insert your messageblks into another database and see if they still act up. Also, what version of GMime are you using? ---------------------------------------------------------------------- Anne - 19-Jan-07 16:49 ---------------------------------------------------------------------- I have the same problem. My errors also include the dbmail_subjectfield table. I get these errors sometimes when doing a daily dbmail-util -ay Ok. Found [2] un-cached physmessages. Error [Duplicate entry '8127044-2007-01-16 09:13:32' for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (8127044,'2007-01-16 09:13:32')] Error insert datefield failed [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (8127044,'2007-01-16 09:13:32')] Error [Duplicate entry '8127044-Lang zullen ze lezen!' for key 2] [INSERT INTO dbmail_subjectfield (physmessage_id, subjectfield) VALUES (8127044,'Lang zullen ze lezen!')] Error insert subjectfield failed [INSERT INTO dbmail_subjectfield (physmessage_id, subjectfield) VALUES (8127044,'Lang zullen ze lezen!')] .Error [Duplicate entry '8127043-2007-01-16 09:13:32' for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (8127043,'2007-01-16 09:13:32')] Error insert datefield failed [INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES (8127043,'2007-01-16 09:13:32')] Error [Duplicate entry '8127043-Lang zullen ze lezen!' for key 2] [INSERT INTO dbmail_subjectfield (physmessage_id, subjectfield) VALUES (8127043,'Lang zullen ze lezen!')] Error insert subjectfield failed [INSERT INTO dbmail_subjectfield (physmessage_id, subjectfield) VALUES (8127043,'Lang zullen ze lezen!')] . ---------------------------------------------------------------------- aaron - 06-Feb-07 01:08 ---------------------------------------------------------------------- Has this been resolved by Paul's recent patch? ---------------------------------------------------------------------- pgilmore-ellis - 06-Feb-07 12:45 ---------------------------------------------------------------------- Sorry filed a dupe bug for this with id 503. Nube! We're using MySQL 5.0.18 and GMime 2.2.3 and dbmail-2.2.2. Tried to patch with PostgreSQL patch but to no awail. The error log is attached to bug id 503. ---------------------------------------------------------------------- aaron - 01-Mar-07 07:20 ---------------------------------------------------------------------- Please see if DBMail 2.2.3 is still affected. ---------------------------------------------------------------------- aaron - 02-May-07 00:59 ---------------------------------------------------------------------- I'm assuming this was indeed fixed in the last version. Issue History Date Modified Username Field Change ====================================================================== 07-Jan-07 21:07 zak New Issue 19-Jan-07 02:50 aaron Note Added: 0001735 19-Jan-07 16:44 Anne Note Added: 0001736 19-Jan-07 16:49 Anne Note Edited: 0001736 06-Feb-07 01:08 aaron Note Added: 0001815 06-Feb-07 12:45 pgilmore-ellis Note Added: 0001817 01-Mar-07 07:20 aaron Note Added: 0001850 02-May-07 00:59 aaron Status new => resolved 02-May-07 00:59 aaron Fixed in Version => 2.2.4 02-May-07 00:59 aaron Resolution open => fixed 02-May-07 00:59 aaron Assigned To => aaron 02-May-07 00:59 aaron Note Added: 0002125 ====================================================================== _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
