remy at linuxnet
Mar 17, 2011, 12:58 PM
Post #1 of 3
(395 views)
Permalink
|
Hello guys! This is my first time in the mailing list. My name is Remy
and I'm brazilian.
First of all, I think it's important to give you some more information
about my environment, which follows:
Linux powermail 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 i686
athlon i386 GNU/Linux
openSUSE 11.3 (i586)
VERSION = 11.3
This is DBMail version 2.2.17
mysql-community-server-5.1.46-2.18.i586
So, I'm running dbmail with mysql as you can see. I never had issued the
command to verify the integrity of the database, recently first time I
did, I got:
(dbmail-util -avy)
*/Opening connection to database...
Opening connection to authentication...
Ok. Connected.
Repairing DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.
--- Repairing block integrity took 1 seconds
Repairing DBMAIL physmessage integrity...
Ok. Found [0] unconnected physmessages.
--- Repairing unconnected physmessages took 0 seconds
Repairing DBMAIL message integrity...
Ok. Found [0] unconnected messages.
--- Repairing message integrity took 0 seconds
Repairing DBMAIL mailbox integrity...
Ok. Found [0] unconnected mailboxes.
--- Repairing mailbox integrity took 0 seconds
Repairing DBMAIL for NULL messages...
Ok. Found [0] NULL messages.
--- checking NULL messages took 0 seconds
Checking DBMAIL for NULL physmessages...
Ok. Found [0] physmessages without messageblocks.
--- checking NULL physmessages took 0 seconds
Deleting messages with DELETE status...
Ok. [0] messages deleted.
Repairing DBMAIL for rfcsize field...
Ok. Found [0] missing rfcsize values.
--- checking rfcsize field took 0 seconds
Repairing DBMAIL for incorrect is_header flags...
Ok. Found [0] incorrect is_header flags.
--- checking is_header flags took 2 seconds
Repairing DBMAIL for cached envelopes...
Ok. Found [0] missing envelope values.
--- checking envelope cache took 1 seconds
Repairing DBMAIL for cached header values...
Ok. Found [2] un-cached physmessages.
Mar 17 16:47:13 powermail dbmail-util[6809]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '164194-1970-01-01 00:00:00'
for key 'physmessage_id'] [INSERT INTO dbmail_datefield (physmessage_id,
datefield) VALUES (164194,'1970-01-01 00:00:00')]
Mar 17 16:47:13 powermail dbmail-util[6809]: Error:[message]
dbmail-message.c,insert_field_cache(+1116): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(164194,'1970-01-01 00:00:00')]
Mar 17 16:47:13 powermail dbmail-util[6809]: Message:[message]
dbmail-message.c,dbmail_message_cache_subjectfield(+1218): no subject
field value [164194]
..Mar 17 16:47:13 powermail dbmail-util[6809]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '134-1970-01-01 00:00:00' for
key 'physmessage_id'] [INSERT INTO dbmail_datefield (physmessage_id,
datefield) VALUES (134,'1970-01-01 00:00:00')]
Mar 17 16:47:13 powermail dbmail-util[6809]: Error:[message]
dbmail-message.c,insert_field_cache(+1116): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(134,'1970-01-01 00:00:00')]
Mar 17 16:47:13 powermail dbmail-util[6809]: Message:[message]
dbmail-message.c,dbmail_message_cache_subjectfield(+1218): no subject
field value [134]
..--- checking cached headervalues took 0 seconds
Setting DELETE status for deleted messages...
Ok. [0] 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. Errors were found and fixed.
We suggest running dbmail-util again to confirm that all errors were
repaired/*.
And then, when I run it again as suggested, I got exactly the same thing
over and over again... In other words it cannot fix the error, even
though tells it can. Outside that, It's working perfectly...
I can't just forget this because I'm intending to deploy dbmail in my
new customers, for that, I'd to be sure that my deployment is ok.
Thanks in advance.
Remy.
|
