From: Alan Hicks <ahi...@p-o.co.uk>
Subject: Re: [Dbmail] Migration of Data from 2.2.17 to 3.0.2
(dbmail-util coredumping)
Resending as it does not appear to have arrived!
On 24/05/2012 10:32, Alan Hicks wrote:
> On 24/05/2012 08:52, Paul J Stevens wrote:
>> On 05/22/2012 01:17 PM, Daniel Sch?tze wrote:
>>> Can anyone suggest to me what might be going wrong, or if there is
>>> anything useful I can examine? So far this has happened 7 times up
>>> to physmessage_id 612844 (out of the 900k or so) so it is infrequent
>>> but being a coredump it does mean it halts the migration which is
>>> inconvenient. I am running MySQL 5.1.55, on freebsd 8.2 for general
>>> information.
> Apologies I only just picked up on fbsd. I'm preparing an upgrade to
> gmime and will hopefully have this later today, the port is
> unmaintained so unless anyone else is interested I'll look after it.
Submitted as http://www.freebsd.org/cgi/query-pr.cgi?pr=168308
Thank you, I updated the ports and built gmime 2.4.32 and tried again with
the dbmail-util -yM. It ran the first batch fine (no error on exit) and
then I started dbmail-util off again and immediately received a foreign key
error for a message (exactly as before). I do not know if it was literally
the first message that was attempted to be processed but the error was
essentially instant. I then deleted the entries for that physmessage_id
from the dbmail_partlists table and reran dbmail-util which then proceeded.
Looking at dbmail_partlists it appears that the message was migrated again,
this time without throwing an error. Currently I'm leaving the migration
going with 100000 messages with the aim of hopefully getting through all of
them. Unfortunately this test box gets through them very slowly.
Daniel Schütze
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
