similar to: Host ... is being updated before previous update had finished

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

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:

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

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

Hello, ------------- -------- --- -------- |Sip Softphone|-------|Internet|--------|F.W|-----|Asterisk| ------------- -------- --- -------- IP addresses: a.b.c.d q.w.e.r The SIP softphone(x-lite) is configured to register with the asterisk server through port 9090 (Domain q.w.e.r:9090).Firewall(F.W) is setup as the

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 }

Folks I'd love to use Cockpit, but I cannot open port 9090 for the access in all cases. I'd like to access it via my usual http port (such as 80) where I'm limited to a single HTTP port. I understand the security implications, and can deal with them later. My attempt was to allow the following URL to access the cockpit functionality: http://xxx.example.com/cockpit (not the

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

Hi Timo Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 01:10:20 CEST): ? > Ah, the information comes from the other director running. The other one > is using an unpatched version of dovecot. Your patch for backend-certificate verification works. Thank you for the good and fast work. Is there any chance that this will make it into Dovecot's next release? BTW: The

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

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

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

Hi, I'm using cockpit in standard port 9090 in a Centos 7 system. Due to a suggestion from management, they want TLS 1.1 disabled system-wide in all Linux boxes and TLS 1.2 enabled. I have not found proper documentation on how to disable it for cockpit (version 195.1 ships with Centos 7) So far I have tried (https://cockpit-project.org/guide/149/https.html):

Sure did! I am even playing with different options (including NONE) and it seems to ignore the contents of ssl.conf I have tried Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA: Environment=G_TLS_GNUTLS_PRIORITY=NORMAL:+TLS1.2:!TLS1.1:!TLS1.0:!ECDHE-RSA-AES256-SHA Environment=G_TLS_GNUTLS_PRIORITY=PFS

Hi, I have a setup with several dovecot-servers (2.2.35) and I use dovecot proxy. I upgraded one server to 2.3.1 and got the configs fixed so far that it started again. But when I tried to add it into the proxying again with "doveadm director add" I see the following in the logfiles: May 6 07:19:30 host dovecot: director: Warning: Director xxx.xxx.xxx.176:9090/out disconnected us with

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated

Thanks, Randal for the response. But it did not work. Here the results: #yum info cockpit Name : cockpit Arch : x86_64 Version : 195.1 Release : 1.el7.centos.0.1 Size : 51 k Repo : installed >From repo : extras Summary : Web Console for Linux servers URL : https://cockpit-project.org/ License : LGPLv2+ [root at cockpit ~]# cat

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

Hi all! I've setup an icecast2 relay server, which connect to an icecast1 server mountpoint. the stats.log of icecast1 lists an/my icecast2 relay connect - so far so fine :) BUT: if i try to listen to the relayed stream, my winamp couldn'd connect: 404 file not found :(( the access.log lines are like: 213.23.134.235 - - [13/Apr/2004:08:05:29 +0200] "GET /rc2 HTTP/1.0" 404

> > 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 >> >