lots of un-cached physmessages since 2.2.5

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')]
Aug 22 02:08:33 <server>
 dbmail-util[57474]: Error:[message]
dbmail-message.c,insert_field_cache(+1133): insert datefield
failed [INSERT INTO dbmail_datefield (physmessage_id,
datefield) VALUES (10077789,'1970-01-01 00:00:00')]
Aug 22 02:08:33 <server>
 dbmail-util[57474]: Error:[sql] dbmysql.c,db_query(+293):
[Duplicate entry '10077789-Sieve script run error' for key
2] [INSERT INTO dbmail_subjectfield (physmessage_id,
subjectfield) VALUES (10077789,'Sieve script run error')]
Aug 22 02:08:33 <server>
 dbmail-util[57474]: Error:[message]
dbmail-message.c,insert_field_cache(+1133): insert
subjectfield failed [INSERT INTO dbmail_subjectfield
(physmessage_id, subjectfield) VALUES (10077789,'Sieve
script run error')]
.
Maintenance done. Errors were found and fixed.
We suggest running dbmail-util again to confirm that all
errors were repaired.

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

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
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Aaron Stone wrote:
> Paul, take a look at pipe.c, send_alert. It directly
inserts a message
> created with dbmail_message_construct. Is there an
additional internal API
> call that needs to be made to cache the message
headers?

dbmail_message_cache_headers



-- 
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

On Thu, Aug 23, 2007, Paul J Stevens <paulnfg.nl> said:

> Aaron Stone wrote:
>> Paul, take a look at pipe.c, send_alert. It
directly inserts a message
>> created with dbmail_message_construct. Is there an
additional internal API
>> call that needs to be made to cache the message
headers?
> 
> dbmail_message_cache_headers

Ah, thank you. I'll add this call later today.

Aaron
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

I have the same problem after running 2.2.5 for a month or
so. Each time 
the dbmail-util -ay runs I get

Repairing DBMAIL for cached header values...
Ok. Found [169] un-cached physmessages.

And they don't go away in subsequent runs of dbmail-util.

The number of mails that got in the system during that time
is of course 
far greater.

I now went back to gmime 2.1.19 and dbmail 2.2.1 due the
/tmp space 
problem. Hopefully it'll help. I'll know around Monday
morning.

-- 
br,
Tommi
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail