Thank you!
Do you have an entry for mupdate in your /etc/services file ?
No, but I specify the port in both /etc/cyrus.conf and /etc/imapd.conf . When I can next afford some downtime I'll try adding that, though, and see if it makes any difference. (Not 100% sure, but what I'm gathering from the stack trace is that ctl_mboxlist is connecting through a socket, getting a banner message from mupdate, trying to look up the peer IP address from the socket which doesn't work because it's a local socket and not a network connection, and not even trying to authenticate.)
Separate your frontend, backend and mupdate server, on differents servers or, if you really can't, with different conf and db files and differents ports or ip.
I can't safely separate them until the migration happens, but using different conf files and ports should work!
What do you mean by different DB files? If mupdate is running on the same host as a frontend (which has to be the current server because I've seen that you shouldn't proxy from a newer version to an older version because it will try to proxy unsupported IMAP commands) and a backend (which has to be the current server because that's where the mailboxes are; the point of all this is to be able to move them elsewhere), what databases have to have separate copies/versions for the various daemons?
Before going tu murder, have a look to replication.
Thank you! That looks like it might be exactly what I want! (The end goal is to have a murder cluster, but replication looks like it's a better match for my immediate needs.)
Jay
