Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DBMail: users

why...?

 

 

DBMail users RSS feed   Index | Next | Previous | View Threaded


andrea at brancatelli

Mar 28, 2009, 6:22 PM

Post #1 of 7 (839 views)
Permalink
why...?

Why?

Repairing DBMAIL for cached header values...
Ok. Found [4] un-cached physmessages.
Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '467171-1970-01-01
00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id,
datefield) VALUES (467171,'1970-01-01 00:00:00')]
Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(467171,'1970-01-01 00:00:00')]
..Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '467170-1970-01-01
00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id,
datefield) VALUES (467170,'1970-01-01 00:00:00')]
Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(467170,'1970-01-01 00:00:00')]
..Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '270306-1970-01-01
00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id,
datefield) VALUES (270306,'1970-01-01 00:00:00')]
Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(270306,'1970-01-01 00:00:00')]
..Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '270298-1970-01-01
00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id,
datefield) VALUES (270298,'1970-01-01 00:00:00')]
Mar 29 03:20:52 mela.raged.it dbmail-util[56101]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(270298,'1970-01-01 00:00:00')]


How do I fix this? dbmail-util doesn't fix it in any way.

Why it happened?
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


paul at nfg

Mar 29, 2009, 5:53 AM

Post #2 of 7 (799 views)
Permalink
Re: why...? [In reply to]

andrea[at]brancatelli.it wrote:
> 00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id,
> datefield) VALUES (467171,'1970-01-01 00:00:00')]

> How do I fix this? dbmail-util doesn't fix it in any way.

Remove the entries that are in the way. In the example above:
delete from dbmail_datefield where physmessage_id=467171;

> Why it happened?

The -b check of dbmail-util will lookup all physmessages that don't have
an entry in dbmail_headervalue. If for some reason that happens to be
the case, while the other cache tables still contain entries for that
message, subsequent dbmail-util -by runs will fail.



> _______________________________________________
> DBmail mailing list
> DBmail[at]dbmail.org
> http://mailman.fastxs.nl/cgi-bin/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
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


aleksander at krediidiinfo

Mar 29, 2009, 6:09 AM

Post #3 of 7 (803 views)
Permalink
Re: why...? [In reply to]

Paul J Stevens wrote:
> The -b check of dbmail-util will lookup all physmessages that don't have
> an entry in dbmail_headervalue. If for some reason that happens to be
> the case, while the other cache tables still contain entries for that
> message, subsequent dbmail-util -by runs will fail.

Should a bug report be filed on this so dbmail-util would be enhanced to
handle the scenario?


--

Aleksander Kamenik
System Administrator
Krediidiinfo AS
an Experian Company
Phone: +372 665 9649
Email: aleksander[at]krediidiinfo.ee

http://www.krediidiinfo.ee/
http://www.experiangroup.com/
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


paul at nfg

Mar 29, 2009, 9:01 AM

Post #4 of 7 (797 views)
Permalink
Re: why...? [In reply to]

Aleksander Kamenik wrote:
> Paul J Stevens wrote:
>> The -b check of dbmail-util will lookup all physmessages that don't have
>> an entry in dbmail_headervalue. If for some reason that happens to be
>> the case, while the other cache tables still contain entries for that
>> message, subsequent dbmail-util -by runs will fail.
>
> Should a bug report be filed on this so dbmail-util would be enhanced to
> handle the scenario?

What scenario? There is already a bugreport for duplicate key errors on
insertion. dbmail-util -b is/was meant as a migration tool, not as a
fix-all-my-caching-errors tool.

--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


andrea at brancatelli

Apr 6, 2009, 2:00 AM

Post #5 of 7 (738 views)
Permalink
Re: why...? [In reply to]

Il giorno dom, 29/03/2009 alle 14.53 +0200, Paul J Stevens ha scritto:

> > 00:00:00' for key 2] [INSERT INTO dbmail_datefield (physmessage_id,
> > datefield) VALUES (467171,'1970-01-01 00:00:00')]
> > How do I fix this? dbmail-util doesn't fix it in any way.
> Remove the entries that are in the way. In the example above:
> delete from dbmail_datefield where physmessage_id=467171;
>


No Paul, sorry, that didn't work:

mysql> delete from dbmail_datefield where physmessage_id=467171;
Query OK, 1 row affected (0.00 sec)

mysql> delete from dbmail_datefield where physmessage_id=270298;
Query OK, 1 row affected (0.00 sec)

mysql> delete from dbmail_datefield where physmessage_id=467170;
Query OK, 1 row affected (0.00 sec)

mysql> delete from dbmail_datefield where physmessage_id=270306;
Query OK, 1 row affected (0.00 sec)

mysql> quit
Bye

[/root[at]mela] #dbmail-util -ay

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...
Ok. Found [0] physmessages without messageblocks.

Deleting messages with DELETE status...
Ok. [0] messages deleted.

Repairing DBMAIL for rfcsize field...
Ok. Found [0] missing rfcsize values.

Repairing DBMAIL for incorrect is_header flags...
Ok. Found [0] incorrect is_header flags.

Repairing DBMAIL for cached envelopes...
Ok. Found [0] missing envelope values.

Repairing DBMAIL for cached header values...
Ok. Found [4] un-cached physmessages.
.....
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.

[/root[at]mela] #dbmail-util -ay

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...
Ok. Found [0] physmessages without messageblocks.

Deleting messages with DELETE status...
Ok. [0] messages deleted.

Repairing DBMAIL for rfcsize field...
Ok. Found [0] missing rfcsize values.

Repairing DBMAIL for incorrect is_header flags...
Ok. Found [0] incorrect is_header flags.

Repairing DBMAIL for cached envelopes...
Ok. Found [0] missing envelope values.

Repairing DBMAIL for cached header values...
Ok. Found [4] un-cached physmessages.
Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '467171-1970-01-01 00:00:00'
for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield)
VALUES (467171,'1970-01-01 00:00:00')]
Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(467171,'1970-01-01 00:00:00')]
..Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '467170-1970-01-01 00:00:00'
for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield)
VALUES (467170,'1970-01-01 00:00:00')]
Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(467170,'1970-01-01 00:00:00')]
..Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '270306-1970-01-01 00:00:00'
for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield)
VALUES (270306,'1970-01-01 00:00:00')]
Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(270306,'1970-01-01 00:00:00')]
..Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[sql]
dbmysql.c,db_query(+290): [Duplicate entry '270298-1970-01-01 00:00:00'
for key 2] [INSERT INTO dbmail_datefield (physmessage_id, datefield)
VALUES (270298,'1970-01-01 00:00:00')]
Apr 06 10:58:14 mela.raged.it dbmail-util[69655]: Error:[message]
dbmail-message.c,insert_field_cache(+1105): insert datefield failed
[INSERT INTO dbmail_datefield (physmessage_id, datefield) VALUES
(270298,'1970-01-01 00:00:00')]
..
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.



Any other hint? :)
Attachments: stock_smiley-1.png (0.85 KB)


josh at worldhosting

Apr 9, 2009, 2:02 PM

Post #6 of 7 (708 views)
Permalink
Re: why...? [In reply to]

> >> The -b check of dbmail-util will lookup all physmessages that don't have
> >> an entry in dbmail_headervalue. If for some reason that happens to be
> >> the case, while the other cache tables still contain entries for that
> >> message, subsequent dbmail-util -by runs will fail.
> >
> > Should a bug report be filed on this so dbmail-util would be enhanced to
> > handle the scenario?
>
> What scenario? There is already a bugreport for duplicate key errors on
> insertion. dbmail-util -b is/was meant as a migration tool, not as a
> fix-all-my-caching-errors tool.

Hi,

I have the same problem here, reported as a reply to Michael Monnerie's
posts "Bug in dbmail-util - not cleaning un-cached physmessages, and
making other mess"

It seems that if a headervalue is not set, e.g. Subject field is blank,
that these errors appear. dbmail-util is not checking for existing
headers when recreating dummy ones, and so is failing to fix the missing
headervalue.

Removing the date field does not fix the problem, because it's another
field that is missing. Since dbmail-util tries to recreate date field
before the other, missing, field, and fails because the unique restraint
stops it, it stops trying to recreate the other header fields. So it
never gets to fix the real problem.

Regards,
Josh.

_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


michael.monnerie at is

Apr 10, 2009, 12:40 AM

Post #7 of 7 (703 views)
Permalink
Re: why...? [In reply to]

On Donnerstag 09 April 2009 Josh Marshall wrote:
> Since dbmail-util tries to recreate date field
> before the other, missing, field, and fails because the unique
> restraint stops it, it stops trying to recreate the other header
> fields. So it never gets to fix the real problem.

I'll have a look into a cleanup of the indices, and Paul will fix the
rest. I'm just on holidays this week, so it needs to wait a bit.

mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4

_______________________________________________
DBmail mailing list
DBmail[at]dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

DBMail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.