Another question is about the director failover. In http://blog.dovecot.org/2010/05/new-director-service-in-v20-for-nfs.html you said: "The main complexity here comes from how to handle proxy server failures in different situations. Those are less interesting to describe and I haven't yet implemented all of it, so let's just assume that in future it all works perfectly." So currently there is no good way to handle the director failover, or any 3rd party solution like poolmon by Brad Davidson for health monitoring of backend servers?
Thanks.
Timo Sirainen
<t...@iki.fi>
Sent by: To
dovecot-bounces@d Dovecot Mailing List
ovecot.org <dovecot@dovecot.org>
cc
02/12/2012 12:06 Subject
PM Re: [Dovecot] Synchronization error
in NFS
Please respond to
Dovecot Mailing
List
<dovecot@dovecot.
org>
On 10.2.2012, at 10.08, Andy YB Hu wrote:
> Searched the archive, and got the doveadm -a director-admin for local
> doveadm access, and -a host: port for remote doveadm access.
You can give -c parameter also to doveadm (and all other Dovecot programs
as well).
> And you said: http://dovecot.org/list/dovecot/2010-July/050731.html
> Now in my director, I have configed the userdb passwd, but the same error
> occur:
> doveadm(root): Error: User listing returned failure
> doveadm(root): Error: user listing failed
>
> And in the log: Feb 10 07:45:25 auth: Error: Trying to iterate users, but
> userdbs don't support it
I'm guessing that it's connecting to wrong Dovecot's auth process. Use
doveadm -c instead of -a.
<<inline: graycol.gif>>
<<inline: pic09320.gif>>
<<inline: ecblank.gif>>
