search for: directores

I've had 2x director ring up and running with production load on 2.1.8 with around 10,000 active connections for two weeks and everything has been working great - until this morning. There isn't anything obvious in the logs beyond the fact that the director connections started bouncing. It was not resolved by reloads or restarts or an upgrade to 2.1.9 (only the directors.) I've

We just had a bunch of backend boxes go down due to a DDoS in our director cluster. When the DDoS died down, our director ring was a mess. Each box had thousands (and hundreds per second, which is a bit much) of log lines like the following: Apr 03 19:59:29 director: Warning: director(10.1.20.10:9090/left): Host 10.1.17.15 is being updated before previous update had finished (up -> down) -

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address

Hello, I'm build system with two director/proxy and dual stack network (or IPv6-only local services) http://wiki2.dovecot.org/Director say "This also means that a single director ring must use either IPv4 or IPv6 addresses, but not both at the same time." OK All servers have 2 interface (public and local network), and all dual stack IPv4/IPv6, imap/pop (mail) and lmtp (mx) proxy run

On 18 Sep 2018, at 13.29, Simone Lazzaris <s.lazzaris at interactive.eu> wrote: > > > 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

Timo/Aki/Docecot guys, any hints here? Is this a bug? Design issue? On Fri, Apr 7, 2017 at 10:10 AM Mark Moseley <moseleymark at gmail.com> wrote: > On Mon, Apr 3, 2017 at 6:04 PM, Mark Moseley <moseleymark at gmail.com> > wrote: > >> We just had a bunch of backend boxes go down due to a DDoS in our >> director cluster. When the DDoS died down, our director ring

I've got a couple more issues with the doveadm director interface: 1) If I use "doveadm director remove" to disable a host with active users, the director seems to lose track of users mapped to that host. I guess I would expect it to tear down any active sessions by killing the login proxies, like I'd done 'doveadm direct add HOSTNAME 0 && doveadm director flush

In data luned? 10 settembre 2018 09:58:50 CEST, Timo Sirainen ha scritto: > On 8 Sep 2018, at 15.18, Simone Lazzaris <simone.lazzaris at qcom.it> wrote: > > Timo, unfortunately the patch doesn't compile; I've moved the declaration > > of "conn" one line up to make it work. > > Oops, I guess I was too much in a hurry to even compile it. Here's a

I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I

Hi all, I configured samba version 2.2.1a-4 on linux RedHat and many share folders for department. this is the configure d---rwx--- 13 account account .. .. Accounting d---rwx--- 4 admin admin .. .. Administration d---rwx--- 5 director director .. .. Directors d---rwx--- 9 hrd hrd .. .. Hrd [accounting]

On 7 Sep 2018, at 19.43, Timo Sirainen <tss at iki.fi> wrote: > > On 7 Sep 2018, at 16.50, Simone Lazzaris <s.lazzaris at interactive.eu <mailto:s.lazzaris at interactive.eu>> wrote: >> >> Some more information: the issue has just occurred, again on an instance without the "service_count = 0" configuration directive on pop3-login. >> >>

But if in the configuration of the director is stated login/director. Than I assume this socket should be in the login dir not? You have also the director activate with executable = imap-login director? -----Original Message----- Subject: Re: Login/director not created On my install the login/ dir is: drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/ srw-rw-rw- 1 root

On Thu, Feb 23, 2017 at 3:15 PM, Timo Sirainen <tss at iki.fi> wrote: > On 24 Feb 2017, at 0.08, Mark Moseley <moseleymark at gmail.com> wrote: > > > > As someone who is about to begin the process of moving from maildir to > > mdbox on NFS (and therefore just about to start the 'director-ization' of > > everything) for ~6.5m mailboxes, I'm

On 2017-05-31 15:24, Timo Sirainen wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig > > Due to some release process changes I didn't notice that one important > bugfix wasn't included in the v2.2.30 release branch before I made the > release. So fixing it here with v2.2.30.1. Also included

Hi, I've just setup a testing enviroment for director, and it's not working as expected. I have just 1 director (called director) and 2 dovecot servers (dovecot1 and dovecot2); these are exact copies. First problem: when both dovecot servers are up, every imap connection is redirected to the same server as you can see here: $ sudo doveadm director map user

Alas, I've set fs.suid_dumpable to 2 but the core is not dumped. So far I've checked: - ulimit -c unlimited, done - /proc/sys/kernel/core_pattern is set to /var/tmp/core.%p - /var/tmp is chmod 1777 - daemon is not chrooted - sysctl -w fs.suid_dumpable=2 - dir /var/tmp is empty and filesystem has 2GB free This is the logfile: Sep 18 13:54:22 imap-front4 dovecot: director: doveadm: Host

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically

Hi Guys, I am trying to use 2 instances of Dovecot on the same server so I can have a Director managing my connections, everything appears to be working, but I can not use doveadm to control my 2nd instance, but doveconf seems to work fine. [user at server logs]$ doveconf -i Director | grep logs debug_log_path = /home/user/apps/logs/director/director_debug.log info_log_path =

On Mon, Apr 3, 2017 at 6:04 PM, Mark Moseley <moseleymark at gmail.com> wrote: > We just had a bunch of backend boxes go down due to a DDoS in our director > cluster. When the DDoS died down, our director ring was a mess. > > Each box had thousands (and hundreds per second, which is a bit much) of > log lines like the following: > > Apr 03 19:59:29 director: Warning:

As someone who is about to begin the process of moving from maildir to mdbox on NFS (and therefore just about to start the 'director-ization' of everything) for ~6.5m mailboxes, I'm curious if anyone can share any experiences with it. The list is surprisingly quiet about this subject, and articles on google are mainly just about setting director up. I've yet to stumble across an