I think I may have a better idea what is going on.
After leaving the migration going (using the latest gmime) the dbmail-util
core dumped again.
I ran dbmail-util with full logging and I could see what situation was
bringing up the foreign key error.
Essentially dbmail-util -My gets a list of me
How did you do the migration of the database?
On 29/05/12 19:10, Daniel Schütze wrote:
I think I may have a better idea what is going on.
After leaving the migration going (using the latest gmime) the dbmail-util
core dumped again.
I ran dbmail-util with full logging and I could see what situa
On 05/29/2012 11:10 AM, Daniel Schütze wrote:
> Now I thought that dbmail-util -ay checked for unconnected messages and
> removed them which is clearly not happening on my test box; but at this
> stage I am also rather perplexed as to how these entries are in the database
> at all given they are n
>How did you do the migration of the database?
I took a mysql dump from the replication slave, copied it over to the test
box and imported it into a completely empty mysql installation with mysql <
dumpfile.sql
Daniel Schütze
CWA International
Balmoral House
9
I wonder if that's where the issue came into it.
take a look at individual records, if they are in the first db, and not
in it after a restore that's where I'd be looking, are you getting any
warnings on the load?.
I also wonder if it might be something like max packet size conflicts
between
>I wonder if that's where the issue came into it.
>take a look at individual records, if they are in the first db, and not in
it after a restore >that's where I'd be looking, are you getting any
warnings on the load?.
>I also wonder if it might be something like max packet size conflicts
between t
