[Dovecot] doveadm director move behaviour
Hi,
I have a director farm running in front of dovecot pop/imap servers. For a reason, one of my backend servers have been down, so poolmon disables it in director servers and users corresponding to it has been sent to other servers. Until this, no problem.
Now my failed backend server is up again, and I want to redirect all of its users to it, without waiting for it director sessions to end.
So I have used doveadm director move <user> <backend ip> to move them to its "hashed" server. Although a doveadm director status <user> now shows me that this user is directed to the new server, doveadm who in the temporal server shows me that the user is actually connected to it, although messages are delivered to it through is correct server. So I have had to manually kick that users in the temporal servers.
Is this the expected behaviour of the move command for director?
Is there any way to also force the kick of the imap/pop user's connection in the temporal server?
-- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337
On 12.7.2012, at 14.14, Angel L. Mateo wrote:
So I have used doveadm director move <user> <backend ip> to move them to its "hashed" server. Although a doveadm director status <user> now shows me that this user is directed to the new server, doveadm who in the temporal server shows me that the user is actually connected to it, although messages are delivered to it through is correct server. So I have had to manually kick that users in the temporal servers.
Is this the expected behaviour of the move command for director?
Is there any way to also force the kick of the imap/pop user's connection in the temporal server?
Do you see any errors in logs? Especially:
director: Error: connect(ipc) failed: Permission denied
Timo Sirainen <tss@iki.fi> schrieb:
On 12.7.2012, at 14.14, Angel L. Mateo wrote:
So I have used doveadm director move <user> <backend ip> to move them to its "hashed" server. Although a doveadm director status <user> now shows me that this user is directed to the new server, doveadm who in the temporal server shows me that the user is actually connected to it, although messages are delivered to it through is correct server. So I have had to manually kick that users in the temporal servers.
Is this the expected behaviour of the move command for director?
Is there any way to also force the kick of the imap/pop user's connection in the temporal server?
Do you see any errors in logs? Especially:
director: Error: connect(ipc) failed: Permission denied
Looks very familiar to me.
I'm having the same problem as Angel with director move that I have to kick the user logged into the proxy. Plus I'm also getting the ipc permission denied errors you mentioned.
Regards Daniel
On 1.8.2012, at 7.32, Daniel Parthey wrote:
Do you see any errors in logs? Especially:
director: Error: connect(ipc) failed: Permission denied
Looks very familiar to me.
I'm having the same problem as Angel with director move that I have to kick the user logged into the proxy. Plus I'm also getting the ipc permission denied errors you mentioned.
I added a note about it to http://wiki2.dovecot.org/Director#Other_settings
Timo Sirainen wrote:
On 1.8.2012, at 7.32, Daniel Parthey wrote:
Do you see any errors in logs? Especially:
director: Error: connect(ipc) failed: Permission denied
Looks very familiar to me.
I'm having the same problem as Angel with director move that I have to kick the user logged into the proxy. Plus I'm also getting the ipc permission denied errors you mentioned.
I added a note about it to http://wiki2.dovecot.org/Director#Other_settings
doveadm director move needs to be able to connect to the ipc socket. Make sure the director process can do it.
service ipc { unix_listener ipc { user = dovecot } }
Thanks, Timo.
Does this apply to the mailbox config or the director config? Which instance needs to access the ipc socket of which instance?
Regards Daniel
On 1.8.2012, at 21.09, Daniel Parthey wrote:
I added a note about it to http://wiki2.dovecot.org/Director#Other_settings
doveadm director move needs to be able to connect to the ipc socket. Make sure the director process can do it.
service ipc { unix_listener ipc { user = dovecot } }
Thanks, Timo.
Does this apply to the mailbox config or the director config? Which instance needs to access the ipc socket of which instance?
director instance needs access to director instance.
El 01/08/12 20:10, Timo Sirainen escribió:
On 1.8.2012, at 21.09, Daniel Parthey wrote:
I added a note about it to http://wiki2.dovecot.org/Director#Other_settings
doveadm director move needs to be able to connect to the ipc socket. Make sure the director process can do it.
service ipc { unix_listener ipc { user = dovecot } }
Thanks, Timo.
Does this apply to the mailbox config or the director config? Which instance needs to access the ipc socket of which instance?
director instance needs access to director instance.
Hello,
Sorry for the delay, I've been on vacation these days. I'm going to try it.-- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337
Timo Sirainen wrote:
On 1.8.2012, at 21.09, Daniel Parthey wrote:
http://wiki2.dovecot.org/Director#Other_settings
doveadm director move needs to be able to connect to the ipc socket. Make sure the director process can do it.
service ipc { unix_listener ipc { user = dovecot } }
director instance needs access to director instance.
With the above configuration, ipc works correctly between our directors and kicks the moved users which had been connected via proxy.
Thanks a lot!
Regards Daniel
El 01/08/12 20:10, Timo Sirainen escribió:
On 1.8.2012, at 21.09, Daniel Parthey wrote:
I added a note about it to http://wiki2.dovecot.org/Director#Other_settings
doveadm director move needs to be able to connect to the ipc socket. Make sure the director process can do it.
service ipc { unix_listener ipc { user = dovecot } }
Thanks, Timo.
Does this apply to the mailbox config or the director config? Which instance needs to access the ipc socket of which instance?
director instance needs access to director instance.
With this configuration, doveadm director move now works correctly, kicking user's connection in the old backend server.
-- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337
participants (3)
-
Angel L. Mateo
-
Daniel Parthey
-
Timo Sirainen