See:
http://stuff.mit.edu/afs/sipb/project/linerva/project/packages/cyrus/cyrus21-imapd-2.1.18/debian/README.Debian.debug
On 05/07/11 13:38 -0400, Robert Spellman wrote:
>Occasionally, I see something mentioned about tracing a particular
>cyrus process to determine what's going on (or wrong, as
Occasionally, I see something mentioned about tracing a particular cyrus
process to determine what's going on (or wrong, as the case may be).
How is this done? I'm not getting very far at resolving my particular
problem, so I'd like to know what the proxyd process thinks it's doing
each time
It appears that the front end does know that it has the mailbox:
[cyrus@postoffice09 ~]$ cyr_dbtool `pwd`/mailboxes.db skiplist show
user.frodo
user.frodo1 postoffice09.bates.edu!default frodolrswipkxtecda
The backend knows nothing about the user frodo:
[cyrus@mailstore07 ~]$ cyr_db
On 01/07/11 09:10 -0400, Robert Spellman wrote:
>We have recently upgraded to cyrus 2.4.6. Our environment includes a
>server running as a murder server, four back end mailstores, and two
>front end servers. If we mistakenly create a user mailbox on one of
>the front end servers using cyradm,
We have recently upgraded to cyrus 2.4.6. Our environment includes a
server running as a murder server, four back end mailstores, and two
front end servers. If we mistakenly create a user mailbox on one of the
front end servers using cyradm, and then try to manage it (dm, sam,
info, lm), cpu
