Page 1 of 1

Problems with imapsync

Posted: Tue Apr 10, 2007 2:27 am
by afassl
Hi,

had the last two days "fun" with the side effects of imapsync.
First conclusion: Don't use it on large mailboxes or try to test the migration on a test system.
I'm migrating my users from my good and stable Netscape Messaging Server (out of anything: Support OS, Support System - even the company doesn't exist) to the brilliant scalix server. OM (now scalix) is really a high end messaging solution. I'm using it in the community edition, but I'm recommending it to customers having need for a commercial license. We'll see.

After starting imapsync to copy a 2 GB mailbox (my own, I can't delete old mails :-) and it is up since 1999) I've got many errors and I stopped the import. Thereafter I've got lots of errors like IMAP-access died, LDAP died, web access stopped with "unknown errors".
What a nightmare.

With google I found all the needed information to recover from this desaster.
Thanks to this forum. This is really a masterpiece of commercial customer support mixed with community experience.


Fast cure:
# omoff -d0 omscan
# omscan -Z
# omon omscan
Now check with
# omscan -t
until the message shows "Current Server cycle not started".

a
# omcheck -s -d >fix_perms.sh
# chmod +x fix_perms.sh
# ./fix_perms.sh
and a
# omscan -A -a

was needed as well.

Thereafter a
# omtidyallu -M

restart the processes, up and ready again.

Maybe this helps another desperate soul.

Regards

Andreas