On 04 Jun 2010, at 04:14, Gavin Gray wrote:
It's not a unified murder, we have a number of frontends and a
dedicated mupdate master. As for kick_mupdate we see lots of those
errors say over the course of the night when the xfers are taking
place ,but perhaps only one instance of a xfer
Yes, all that you're saying makes sense in terms of what we're experiencing,
Quoting Wesley Craig w...@umich.edu:
On 03 Jun 2010, at 09:24, Gavin Gray wrote:
imap[29289]: [ID 886451 local6.error] Could not trigger remote push to
mupdate serverduring move of user...
During the xfer, the
Hi there,
We are busy migrating lots of users to new backends in our cyrus
murder using xfer.
The existing backends (and the rest of the murder) are cyrus 2.2 where
as the new backend machines are cyrus 2.3.15.
Mostly everything works just fine. However every now and them our new
backends
Forgot to mention the more specific errors we have seen on the
backends we're moving users from:
imap[29289]: [ID 886451 local6.error] Could not trigger remote push to
mupdate serverduring move of user...
and
imap[22505]: [ID 772019 local6.error] Could not set remote acl on user
On 03 Jun 2010, at 09:24, Gavin Gray wrote:
imap[29289]: [ID 886451 local6.error] Could not trigger remote push to
mupdate serverduring move of user...
During the xfer, the local backend sets some information in the
mupdate master WRT the new mailbox location. However, this
information may
