similar to: Multiple Instances with Director

Displaying 20 results from an estimated 7000 matches similar to: "Multiple Instances with Director"

2012 Nov 20
1
v2.1.10: Director director_servers order issue
Hi, I'm setting up an IMAP/POP cluster using dovecot director for some NFS reasons and I'm getting some troubles with director_servers directive. Configuration is shared on both nodes : director_servers = 10.0.50.50 10.0.50.51 director_mail_servers = 192.168.0.150 192.168.0.151 director_user_expire = 15 min service director { unix_listener login/director { mode = 0666 }
2014 Feb 12
1
Getting Director Proxy Working
Hi All, I can't get directory proxying of pop3 and imap working.? The director stuff appears to be OK - see below.?? The ldap authentication is working on the backend mail server.? I just get connection refused when I telnet to the proxy on the pop3 and imap ports.? Nothing appears to be running on the pop3 and imap ports despite the lines in the config below.? I am not sure what to do from
2014 Jun 03
2
director with multiple instances
I'm experiencing some problems similar to those described in http://dovecot.org/list/dovecot/2012-July/137250.html except with 2.0.9. Adding http://dovecot.org/list/dovecot/2012-July/084906.html to the main config didn't seem to help, nor did setting the list of director and backend servers to just the system itself. I get a banner connecting to port 143: [root at retr01 log]# telnet
2019 Mar 19
1
4sec latency when using director
Hi, I've been running dovecot for many years, but now i've hit a strange problem. when retrieving imap there is sometimes in 1 of 4 imap requests a 4sec latency. * notes: - connected directly to the backends this latency disappears - removing a director from the loadbalancer(lvs) so i'm the only connected to the director this latency disappears too I would appreciate some feedback
2012 Nov 21
1
Dovecot director doveadm with switch "-A" error
Hi, we have a problem with our director proxy configuration. When we run on proxy server the doveadm command with -A switch, fails with the error: # doveadm -D quota get -A doveadm(user1): Debug: auth input: user=user1 proxy starttls=any-cert doveadm(user1): Error: Proxy is missing destination host doveadm: Error: Failed to iterate through some users If we execute the command with a single
2015 Jul 20
0
Problems with IMAP/POP and dovecot director on backend (director_proxy_maybe)
Hello dovecot community, first of all: dovecot ist great! ;) ...nevertheless I?ve got some problems to get my director scenario running as needed/expected :( My scenario: I?d like to configure two dovecot backends, without the need for multiple dovecot instances. Both backend servers are active/active and act on top of a glusterfs storage, which implies the need for dovecot director. As
2011 Oct 04
1
trouble setting up director, "invalid argument" for connect() call
Hi Timo & everyone, I'm trying out a 2-node director setup, but I keep getting the following error: Oct 3 16:11:29 imapdir1 dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) Oct 3 16:11:34 imapdir1 dovecot: director: Error: connect(132.198.100.150:9090) failed: Invalid argument Oct 3 16:11:41 imapdir1 last message repeated 3 times Both nodes report this error. The
2019 Nov 19
1
Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established)
I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed:
2018 Sep 18
0
Auth process sometimes stop responding after upgrade
> Hi all, again; > > I've enabled the core dumps and let it go for some day waiting for the issue > to reoccur. > > Meantime I've also upgraded the poolmon script, as Sami suggested. > > It seems that the upgrade has scared the issue away, because it no longer > occurred. > > Maybe the problem is related to the way the old poolmon talked to the >
2018 Sep 07
1
Auth process sometimes stop responding after upgrade
Hi all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting):
2012 Oct 21
2
No failover from director to backend?
Hi everyone, short version: Is there no built in failover mechanism for the director service to handle a backend failure? Long version: I have a frontend server running the director service and two backends. Due to maintenance I had to shut down one of the backends which caused connection errors for the users being directed to this backend. I was very surprised as I expected the director to
2012 Oct 15
1
Plugin hooks in login process
Hi all; I've setup dovecot (2.1.10) in a cluster configuration. We have two servers acting as frontend which authenticates users and proxy them to other two servers which handles the "real" work. Users credentials are on a mysql cluster; we have one master, in which read/write queries are processed, and many replicated slave, which process read-only queries. The frontend
2018 Sep 06
0
Auth process sometimes stop responding after upgrade
Hi all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting):
2014 May 13
0
Error on doveadm director map
Hi All, I am running Dovecot 1:2.2.9-1~bpo70+1 on Debian Wheezy. I have just started getting the error below when I do a do a list of proxied users. The list of users appears OK afterwards. # doveadm director map doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed user mail server ip expire time . . . My director config is below. Thanks
2014 Jun 16
0
connection to director (lmtp) time out
Hi all, I'm running two directors with lmtp proxy as relay transport for my mail exchangers. relay_transport = lmtp:inet:dovecot-directors.example.net dovecot-directors.example.net resolves to 172.17.1.3 and 172.17.1.4 Now, .3 is down and Postfix tries to deliver it to .4 but this connection gets a timeout: (delivery temporarily suspended: connect to 172.17.1.4[172.17.1.4]:24: Connection
2011 Sep 12
3
director ignoring director_mail_servers for lmtp connections
Hello, Following Jan-Frode's advise I am trying this configuration: {postfix} ---lmtp---> {director} ---lmtp---> {dovecot} so I have two dovecot instances for director/proxy and lmtp delivery on ports 1024 and 24 respectively. whilst for imap connections I can specify a pool of imap backend servers via 'director_mail_servers' it seems is not possible with lmtp. Sep 12
2015 May 06
0
dovecot-proxy with managesieve, director and backend dovecot imap
hi all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the
2013 Nov 06
0
2.2.6 auth process crash using LMTP and LDAP on director.
I'm upgrading my configuration to use director and lmtp for delivery. (doveconf -n at end of the mail). I use the same config for auth on mail backends and see no errors. My setup seem to work nicely but i have some auth process crashing when using lmtp protocol. Everything is working a sexpected then i've got 5-6 errors like this in logs and a crach of the auth process: dovecot:
2014 Feb 06
0
Trying to get Dovecot Director Proxying working
Hi All, Firstly, thanks for all the really helpful responses to my previous questions "Architecture for large Dovecot cluster" and "Sizing MTA servers". I am now trying to get a Dovecot director proxy working with a single backend mail server. When I try to connect to the dovecot proxy on the pop3 and imap ports I get connection refused. I want the authentication to
2011 Sep 28
0
2.0.14 IPC client_limit reached error
Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot: