Re: Replication problem do_folders(): failed to rename

Am Montag, den 14.12.2015, 07:31 -0400 schrieb Patrick Boutilier via Info-cyrus: > On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: > > Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via > > Info-cyrus: > >> Hi, > >> > >> I have a problem with a single mailbox. The user'

Re: Replication problem do_folders(): failed to rename

Hi, Am Montag, den 14.12.2015, 12:53 +0100 schrieb Michael Menge via Info-cyrus: > Hi, > > > Quoting Patrick Boutilier via Info-cyrus : > > > On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: > >> Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via > >> Info-cyrus: > >

Re: Replication problem do_folders(): failed to rename

Hi, Quoting Patrick Boutilier via Info-cyrus : On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: Hi, I have a problem with a single mailbox. The user's Outlook crashed and since then the sync_client is

Re: Replication problem do_folders(): failed to rename

On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: Hi, I have a problem with a single mailbox. The user's Outlook crashed and since then the sync_client is running wild on this user account and produces hig

Re: Replication problem do_folders(): failed to rename

Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: > Hi, > > I have a problem with a single mailbox. The user's Outlook crashed and > since then the sync_client is running wild on this user account and > produces high load on the master. I stopped sync_client on master

Re: Replication problem do_folders(): failed to rename

Hi, forgot the cyrus version: 2.4.12 on Ubuntu 12.04 LTS Ciao! Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: Replication problem

I swear I'm going to tattoo "RTFM" to my forehead. :-) Putting sync_client into the START section fixed the problem. Replication works flawlessly now. Thank you very much for your help! David Patrick Radtke wrote: Don't put syncclient in the SERVICE section, it should go in the START s

Re: Replication problem

Don't put syncclient in the SERVICE section, it should go in the START section. Your syncserver line looks correct. How many users are on your primary? Possibly you see thrashing on the replica if its doing the initial copy of everyone's files. The initial sync can be time consuming dep

Re: Replication problem

Hi Patrick, I do apologize, that message was hurried so I could get it out and you are right, I did not correctly label things. Your suggestion fixed my main problem, however, a new problem appeared. It started to work when I set the replica to use "sasl_mech_list: PLAIN". I had accident

Re: Replication problem

PLAIN for sasl_pwcheck_method isn't a valid option. Keep it as saslauthd (and then make sure the testsaslauthd program works with your sync username and password). I think you showed me your primary imapd.conf and not the replica's. What does imtest show you when you log into the replica (capa

Re: Replication problem

Hello Patrick! I set the sasl_pwcheck_method to be PLAIN from what it used to be (saslauthd) on the replica server. Still doesn't work though, it gives me this error: badlogin: lmc1.cs.umass.edu [128.119.243.236] DIGEST-MD5 [SASL(-13): user not found: no secret in database] HISTORY: our ser

Re: Replication problem

did you try setting sasl_pwcheck_method on the replica? 'unix' isn't a SASL mechanism. you may want to try PLAIN (what do you use currently on the primary server)? on the replica use this line sasl_mech_list: PLAIN to make it only advertise PLAIN authentication, and then the primary mach