imapsync stops - please help!

[wfweaver]

Working through a migration from cyrus to Zimbra and migrating the email with imapsync. Used the imapsync script. Followed all settings and recommendations found in forums and wikis. However when I do the sync, it only goes so far and then stops! When I turn on debug (or debugimap), I see that the Zimbra side suddenly logs out before the Cyrus side has stopped sending messages over. I've tried many different settings and I have no idea how to fix this but I've got to get it fixed as soon as possible. Please help!

[phoenix]

Some idea of the error messages produced might help, check the zimbra log files and post the errors here: Log Files - Zimbra :: Wiki

[wfweaver]

That's just it though, I can find no errors in the logs! When I turn debugimap on for imapsync, what I see is that Zimbra simply says "BYE" and disconnects and then all subsequent sends from the source server have errors as a result. I don't find ANY errors in the logs, it's as if Zimbra times out the connection and closes it even though it is active. Note that when I do a --dry run, it will go end to end and say that it would have sent 1800 messages, but when I take --dry off, it disconnects before sending those messages. I REALLY need to get this solved today! Thanks!

[phoenix]

If you're hitting bug 27113 then the answer would be to upgrade to the current Zimbra release. Can you do that before the trying the migration with imapsync?

[wfweaver]

That certainly sounds like the bug I'm hitting, though it is more than 1 minute before it happens. Unfortunately I cannot upgrade this weekend, perhaps next, but I have to finish the transition this weekend. The following statement from the bugzilla bug "stick it into timeout and proxy_timeout as
necessary, and you're done" makes it sounds like there is some mechanism for setting it manually? If so, can you please provide me instructions on how to do that?

[p24t]

What version are you on? Your profile reads 4.5.9, but I've seen your post that you might be on 5.0.2? This bug seems specific to 5.0.5 - I'm on 5.0.2 and didn't have much issue with imapsync.

[wfweaver]

Sorry, haven't updated my profile. I'm on 5.0.5.

[mfvm]

This seems to be a problem with nginx, not with th imap component. I had the same issue today, using port 7993 and so ignoring nginx worked fine