Also, just wanted to include the problems I’m getting with running dbmail-util 
–by

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

Repairing DBMAIL for cached envelopes...
Ok. Found [1] missing envelope values.
Jan 16 12:11:48 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Info:[message] 
_retrieve(+1006): [5592286] Deprecation warning. Please migrate the old 
messageblks using dbmail-util -M
Jan 16 12:11:48 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Error:[db] 
db_query(+360): SQLException:
Jan 16 12:11:48 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Error:[db] 
db_query(+361): failed query [SELECT b.messageblk, b.is_header, 
DATE_FORMAT(p.internal_date, GET_FORMAT(DATETIME,'ISO')) FROM 
dbmail_messageblks b JOIN dbmail_physmessage p ON b.physmessage_id=p.id WHERE 
b.physmessage_id = 5592286 ORDER BY b.messageblk_idnr]
Jan 16 12:11:48 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Error:[message] 
dbmail_message_retrieve(+1076): retrieval failed for physid [5592286]
Jan 16 12:11:48 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Warning:[db] 
db_set_envelope(+1671): error retrieving physmessage: [5592286]
E
Repairing DBMAIL for cached header values...
Ok. Found [1] un-cached physmessages.
Jan 16 12:11:50 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Info:[message] 
_retrieve(+1006): [5592286] Deprecation warning. Please migrate the old 
messageblks using dbmail-util -M
Jan 16 12:11:50 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Error:[db] 
db_query(+360): SQLException:
Jan 16 12:11:50 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Error:[db] 
db_query(+361): failed query [SELECT b.messageblk, b.is_header, 
DATE_FORMAT(p.internal_date, GET_FORMAT(DATETIME,'ISO')) FROM 
dbmail_messageblks b JOIN dbmail_physmessage p ON b.physmessage_id=p.id WHERE 
b.physmessage_id = 5592286 ORDER BY b.messageblk_idnr]
Jan 16 12:11:50 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Error:[message] 
dbmail_message_retrieve(+1076): retrieval failed for physid [5592286]
Jan 16 12:11:50 LAMZ1LAPS001N1 dbmail-util[14083]: [0x82be008] Warning:[db] 
db_set_headercache(+1602): error retrieving physmessage: [5592286]
E
Maintenance done. Errors were found and fixed.
We suggest running dbmail-util again to confirm that all errors were repaired.



When I run it again I just get the same message, but I kind of expect that 
because of the error messages from dbmail-util.

Any more insight into this?

I was thinking that if I could write a query to delete that single message that 
seems to be giving it a problem but I wasn’t sure if that would create other 
problems.

Thanks again for any help.

From: dbmail-boun...@dbmail.org [mailto:dbmail-boun...@dbmail.org] On Behalf Of 
Gray, Patrick
Sent: Thursday, January 16, 2014 10:45 AM
To: DBMail mailinglist
Subject: Re: [Dbmail] Dbmail-util functionality problems

Below is the result of explain (select hv.id from dbmail_headervalue hv left 
join dbmail_header h on hv.id = h.headervalue_id where h.headervalue_id is 
NULL);


id,           select_type,       table,    type,     possible_keys,             
    key,                                       key_len,              ref,       
                  rows,                     Extra
'1',          'SIMPLE',              'hv',        'index',                 
NULL,                    'datefield',                          '9',             
             NULL,                    '25544862',          'Using index'
'1',          'SIMPLE',              'h',          'ref',       
'headervalue_id',             'headervalue_id',             '8',                
          'dbmail.hv.id',    '1',                                 'Using where; 
Using index; Not exists'

I guess the NULLs look a bit suspicious.

Not really sure where to go from here.

Thanks for your help.

From: dbmail-boun...@dbmail.org<mailto:dbmail-boun...@dbmail.org> 
[mailto:dbmail-boun...@dbmail.org] On Behalf Of Gennadiy Poryev
Sent: Thursday, January 16, 2014 9:40 AM
To: DBMail mailinglist
Subject: Re: [Dbmail] Dbmail-util functionality problems

Hi Patrick,

I would run EXPLAIN of that SELECT query to see if some indexes got corrupted 
or not used in the DB. This is more likely to slow query down rather than 
dbmail.

Checking DBMAIL headervalues integrity...
DATE SERVERNAME dbmail-util[12351]: [0x93dc008] Warning:[db] 
log_query_time(+299): slow query [SELECT hv.id FROM dbmail_headervalue hv LEFT 
JOIN dbmail_header h ON hv.id = h.headervalue_id WHERE h.headervalue_id IS 
NULL] took [79.420] seconds

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

Reply via email to