[Dovecot] Replication on v2.2.6 - I'm stuck (again)
Hi,
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): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set)
Here is my config:
# 2.2.6: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.2 cobalt auth_mechanisms = plain login doveadm_password = mylittlesecret doveadm_port = 12345 dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u listen = 192.168.1.1 login_greeting = Go on then, let's have it... mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " notify replication" passdb { driver = passwd } plugin { mail_replica = remote:vmail@server2.mydomain.com replication_full_sync_interval = 1 hours } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0600 user = vmail } unix_listener replication-notify { mode = 0600 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service doveadm { inet_listener { port = 12345 } } service imap-login { inet_listener imap { port = 0 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_cert = </etc/openssl/certs/mail.mydomain.com.crt ssl_key = </etc/openssl/private/mail.mydomain.com.key userdb { driver = passwd } protocol lda { postmaster_address = postmaster@mydomain.com
Can anyone give me some guidance on where I've gone wrong with my config?
Any help would be appreciated,
-Mark
On 30.10.2013, at 13.01, IT geek 31 <itgeek31@googlemail.com> 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): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set)
I don’t think you need to have doveadm_port set, since you’re not replicating over TCP. Remove it and it should just work? Anyway, it still shouldn’t have failed, this fixes it:
http://hg.dovecot.org/dovecot-2.2/rev/47848e9fc622
also this gives a bit better error message for the PASS lookup failure:
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 <tss@iki.fi> wrote:
On 30.10.2013, at 13.01, IT geek 31 <itgeek31@googlemail.com> 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): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set)
I don’t think you need to have doveadm_port set, since you’re not replicating over TCP. Remove it and it should just work? Anyway, it still shouldn’t have failed, this fixes it:
http://hg.dovecot.org/dovecot-2.2/rev/47848e9fc622
also this gives a bit better error message for the PASS lookup failure:
Upgrade to v2.2.7
Use:
mail_replica = tcp:server2.mydomain.com
On 3.11.2013, at 21.53, IT geek 31 <itgeek31@googlemail.com> 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.dovecot.org/Replication, but I've obviously taking a wrong turn...
-Mark
On 2 November 2013 11:46, Timo Sirainen <tss@iki.fi> wrote: On 30.10.2013, at 13.01, IT geek 31 <itgeek31@googlemail.com> 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): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set)
I don’t think you need to have doveadm_port set, since you’re not replicating over TCP. Remove it and it should just work? Anyway, it still shouldn’t have failed, this fixes it:
http://hg.dovecot.org/dovecot-2.2/rev/47848e9fc622
also this gives a bit better error message for the PASS lookup failure:
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 /home/mark/.dovecot-sync.lock: Timed out after 30 seconds
Also, I get a lot of errors about Dovecot trying to replicate mailboxes for (system) users that don't have them. Is there any way to exclude users from replication?
-Mark
On 3 November 2013 21:23, Timo Sirainen <tss@iki.fi> wrote:
Upgrade to v2.2.7
Use:
mail_replica = tcp:server2.mydomain.com
On 3.11.2013, at 21.53, IT geek 31 <itgeek31@googlemail.com> 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.dovecot.org/Replication, but I've obviously taking a wrong turn...
-Mark
On 2 November 2013 11:46, Timo Sirainen <tss@iki.fi> wrote: On 30.10.2013, at 13.01, IT geek 31 <itgeek31@googlemail.com> 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): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set)
I don’t think you need to have doveadm_port set, since you’re not replicating over TCP. Remove it and it should just work? Anyway, it still shouldn’t have failed, this fixes it:
http://hg.dovecot.org/dovecot-2.2/rev/47848e9fc622
also this gives a bit better error message for the PASS lookup failure:
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 <itgeek31@googlemail.com> 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 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 /home/mark/.dovecot-sync.lock: Timed out after 30 seconds
Also, I get a lot of errors about Dovecot trying to replicate mailboxes for (system) users that don't have them. Is there any way to exclude users from replication?
-Mark
On 3 November 2013 21:23, Timo Sirainen <tss@iki.fi> wrote:
Upgrade to v2.2.7
Use:
mail_replica = tcp:server2.mydomain.com
On 3.11.2013, at 21.53, IT geek 31 <itgeek31@googlemail.com> 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.dovecot.org/Replication, but I've obviously taking a wrong turn...
-Mark
On 2 November 2013 11:46, Timo Sirainen <tss@iki.fi> wrote: On 30.10.2013, at 13.01, IT geek 31 <itgeek31@googlemail.com> 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): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set)
I don’t think you need to have doveadm_port set, since you’re not replicating over TCP. Remove it and it should just work? Anyway, it still shouldn’t have failed, this fixes it:
http://hg.dovecot.org/dovecot-2.2/rev/47848e9fc622
also this gives a bit better error message for the PASS lookup failure:
On 5.11.2013, at 11.01, IT geek 31 <itgeek31@googlemail.com> 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: dsync-local(mark): Error: Couldn't lock /home/mark/.dovecot-sync.lock: Timed out after 30 seconds
Every time? I can see how it could happen for the initial dsync that takes a long time, but afterwards the syncs should be pretty fast.
Also, I get a lot of errors about Dovecot trying to replicate mailboxes for (system) users that don't have them. Is there any way to exclude users from replication?
Dovecot replicates those users that are returned by: doveadm user ‘*’
How that list is generated depends on the userdbs you have. With passwd it’s filtered only by first_valid_uid and last_valid_uid settings. Perhaps you can set those to the range of users you actually want replicated.
On 10 November 2013 19:34, Timo Sirainen <tss@iki.fi> wrote:
On 5.11.2013, at 11.01, IT geek 31 <itgeek31@googlemail.com> 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: dsync-local(mark): Error: Couldn't lock /home/mark/.dovecot-sync.lock: Timed out after 30 seconds
Every time? I can see how it could happen for the initial dsync that takes a long time, but afterwards the syncs should be pretty fast.
Yes. I started the daemon four hours ago and I'm still seeing that error. Oddly, I'm seeing it even though the data hasn't changed - I'm using test data on a non-production system. So nothing should be replicating.
Also, I get a lot of errors about Dovecot trying to replicate mailboxes for (system) users that don't have them. Is there any way to exclude users from replication?
Dovecot replicates those users that are returned by: doveadm user ‘*’
How that list is generated depends on the userdbs you have. With passwd it’s filtered only by first_valid_uid and last_valid_uid settings. Perhaps you can set those to the range of users you actually want replicated.
Where is this filter set?
participants (2)
-
IT geek 31
-
Timo Sirainen