Re: upgrade failure

Curtis,

It is quite safe to delete and re-create all the cache
tables as created
by the 2.0_2.2 upgrade script, and re-run dbmail-util -by
after that. No
messages will be lost.

the whole list of caching tables:


| dbmail_ccfield            |
| dbmail_datefield          |
| dbmail_envelope           |
| dbmail_fromfield          |
| dbmail_headername         |
| dbmail_headervalue        |
| dbmail_referencesfield    |
| dbmail_replycache         |
| dbmail_replytofield       |
| dbmail_subjectfield       |
| dbmail_tofield            |


Curtis Maurand wrote:
> -ay covers ctubpds (note that "b" is in
there, but I think the order of
> things clobbers the headers. At any rate, it looks like
I lost any
> headers that might have been in there when the
operation was performed,
> not that anyone besides me was using imap anyway. 
After the upgrade
> amavis tried furiously to deliver to the old server (I
neglected to
> change that config) so anything from 2 am on, is OK. 
Otherwise the
> messages are there, they just look funny.  I'll live
with it.  To try to
> fix it now mean a loss of several hours of data.  My
customers wouldn't
> stand for that.
> 
> Curtis
> 
> Jesse Norell wrote:
>> On Thu, 2008-05-22 at 09:36 -0400, Curtis Maurand
wrote:
>>   
>>> OK, I did something wrong.
>>>
>>> from the server where the upgrade was to go.
>>> I did:
>>> mysqladmin -p<password> create dbmail
>>> mysqldump -p<password> -h old.server.com
--database dbmail >dbmail.dump
>>> mysql -p<password> dbmail
<dbmail.dump
>>> mysql -p<password> dbmail
<migrate_from_2.0_to_2.2.sql
>>> dbmail-util -ay (I think this might have been
the screw up)
>>>
>>> Now all headers when connecting with any imap
client are blank (no from, 
>>> no subject).
>>>
>>> Do I need to do the import over again?
>>>     
>>
>>   From memory, I think you need to run dbmail-util
-by after an upgrade,
>> to populate header cache tables and the like.  You
use -ay for
>> daily/periodic maintenance.
>>
>>
>>   
> 
> 
>
------------------------------------------------------------
------------
> 
> _______________________________________________
> DBmail mailing list
> DBmaildbmail.org
> htt
ps://mailman.fastxs.nl/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
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Paul J Stevens wrote:
> Curtis,
> 
> It is quite safe to delete and re-create all the cache
tables as created
> by the 2.0_2.2 upgrade script, and re-run dbmail-util
-by after that. No
> messages will be lost.
> 
> the whole list of caching tables:
> 
> 
> | dbmail_ccfield            |
> | dbmail_datefield          |
> | dbmail_envelope           |
> | dbmail_fromfield          |
> | dbmail_headername         |
> | dbmail_headervalue        |
> | dbmail_referencesfield    |
> | dbmail_replycache         |
> | dbmail_replytofield       |
> | dbmail_subjectfield       |
> | dbmail_tofield            |
> 
> 

I can confirm this works: 
http://www.mail-ar
chive.com/dbmaildbmail.org/msg14505.html
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail