Backend attempting to proxy to itself?

Andrew Morgan morgan at orst.edu
Mon Apr 26 12:40:51 EDT 2010


On Mon, 26 Apr 2010, Simon Beale wrote:

> Thank you!
>
> Yes, doing the following steps:
> - ctl_mboxlist -d > file.txt
> - stopping the backend cyrus
> - removing mailboxes.db,
> - starting cyrus
> - ctl_mboxlist -u < file.editted.txt
> does mean I can run "imtest -a cyrus-frontend -u simon store-101" (i.e.
> against the backend) successfully and SELECT the INBOX.
>
> However, if I restart the backend at this point, I get the old entries
> back again in addition to the fixed entries.
>
> Given this cluster isn't yet in production, I've just stopped the entire
> cluster, deleted mailboxes.db from everything and "rm -rf
> ${partition-default}/*" in case there was something bad lurking around
> from previous experiments. But it's still the case that if I "cm
> user.simon" on the frontend with cyradm, the mailboxes.db on the backend
> appears as "... 1 store-101...!default..."
>
> So for some reason I'm not getting correct mailbox location information
> created on the backends.

Maybe this has changed recently, but I always thought you had to issue "cm 
user.foo" on the backend server you wanted to locate the mailbox on.  How 
does the frontend server know which backend server to select, in a 
generalized case?

 	Andy


More information about the Info-cyrus mailing list