On 10 November 2013 19:34, Timo Sirainen wrote:
> On 5.11.2013, at 11.01, IT geek 31 wrote:
>
> > Thanks for the info. I've upgraded to v2.2.7 and made the change. Now I
> > get:
> >
> > Nov 5 11:00:00 server1 dovecot: dsync-server(mark): Error: Couldn't lock
> > /home/mark/.dovecot-sync.lock
On 5.11.2013, at 11.01, IT geek 31 wrote:
> Thanks for the info. I've upgraded to v2.2.7 and made the change. Now I
> get:
>
> Nov 5 11:00:00 server1 dovecot: dsync-server(mark): Error: Couldn't lock
> /home/mark/.dovecot-sync.lock: Timed out after 30 seconds
> Nov 5 11:00:02 server1 dovecot
Hi,
Does anyone have any ideas? I need to iron out these few remaining issues
before I deploy this into production...
-Mark
> On 5 Nov 2013, at 10:01 am, IT geek 31 wrote:
>
> Hi Timo,
>
> Thanks for the info. I've upgraded to v2.2.7 and made the change. Now I get:
>
> Nov 5 11:00:00
Hi Timo,
Thanks for the info. I've upgraded to v2.2.7 and made the change. Now I
get:
Nov 5 11:00:00 server1 dovecot: dsync-server(mark): Error: Couldn't lock
/home/mark/.dovecot-sync.lock: Timed out after 30 seconds
Nov 5 11:00:02 server1 dovecot: dsync-local(mark): Error: Couldn't lock
/hom
1) Upgrade to v2.2.7
2) Use:
mail_replica = tcp:server2.mydomain.com
On 3.11.2013, at 21.53, IT geek 31 wrote:
> Hi Timo,
>
> Thanks for your response.
>
> Getting it to replicate over TCP is what I'm after. How do I tweak my config
> to get it to do that?
>
> I followed http://wiki2.dove
Hi Timo,
Thanks for your response.
Getting it to replicate over TCP is what I'm after. How do I tweak my
config to get it to do that?
I followed http://wiki2.dovecot.org/Replication, but I've obviously taking
a wrong turn...
-Mark
On 2 November 2013 11:46, Timo Sirainen wrote:
> On 30.10.
On 30.10.2013, at 13.01, IT geek 31 wrote:
> I'm trying to get Dovecot replication working between two servers. I
> didn't have much luck on v2.1.3, so after receiving advice from the list I
> have upgraded to v2.2.6.
>
> I now get the error:
>
> Oct 30 11:50:16 server1 dovecot: doveadm(mark):
