Anne wrote: > Hi, > > Since 2.2.5 (so also with 2.2.6rc1), I see these warnings 3 or 4 times a > week. dbmail-util is run daily. > > Ok. Found [1] un-cached physmessages. > Aug 22 02:08:33 <server> dbmail-util[57474]: Error:[sql] > dbmysql.c,db_query(+293): [Duplicate entry '10077789-1970-01-01 > 00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id, > datefield) VALUES (10077789,'1970-01-01 00:00:00')]
[snip] > Maintenance done. Errors were found and fixed. > We suggest running dbmail-util again to confirm that all errors were > repaired. I assume the dbmail-util run doesn't fix anything, and this error keeps popping up every time you run dbmail-util, right? The code that checks for uncached messages does not check for *every* caching table to contain all required rows. Messages are considered uncached if the headervalue table doesn't contain any reference to the physmessage in question. In this case it sounds like you have a partially cached message. This should normally never happen: the whole caching operation is wrapped in a single transaction. Is it always the datecache that is causing this? Is there anything in the cache tables regarding physmessage 10077789? -- ________________________________________________________________ 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
