similar to: Poolmon: Problem with index-locking

On 10 Jan 2017, at 20.38, Tom Sommer <mail at tomsommer.dk> wrote: > > I have Poolmon (https://github.com/brandond/poolmon) set up. When it does all the checks concurrently, obviously there are locking issues on each mailserver it tests: > > "Warning: Locking transaction log file xxxx/indexes/dovecot.list.index.log took 60 seconds (syncing)" > > It's just

In data venerd? 7 settembre 2018 11:20:49 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.25, Simone Lazzaris <simone.lazzaris at qcom.it> wrote: > > Actually, I have a poolmon script running that should drop vhost count for > > unresponsive backends; the strage thing is, the backends are NOT > > unresponsive, they are working as ususal. > If it's this

In data venerd? 7 settembre 2018 10:06:00 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at interactive.eu> > > wrote: > > > > > > The only suspect thing is this: > > > > Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host > > 192.168.1.142 > > vhost count changed from 100 to 0 >

Hi My servers are Ubuntu 14.04 and I'm needing to make a Upstart script for Poolmon. Does someone already made this and could to share with us ? Thanks! -- Thiago henrique

Hello, I have recently setup mailserver solution using 2-node master-master setup (mainly based on MySQL M-M replication and GlusterFS with 2 replica volume) on Ubuntu 14.04 (Dovecot 2.2.9). Unfortunately even with shared-storage-aware setting: mail_nfs_index = yes mail_nfs_storage = yes mail_fsync = always mmap_disable = yes ..I have hit strange issues pretty soon especially when user was

> On 7 Sep 2018, at 11.25, Simone Lazzaris <simone.lazzaris at qcom.it> wrote: > Actually, I have a poolmon script running that should drop vhost count for unresponsive backends; the strage thing is, the backends are NOT unresponsive, they are working as ususal. > If it's this one https://github.com/brandond/poolmon/blob/master/poolmon

On 2018-10-05 11:35, Timo Sirainen wrote: > On 4 Oct 2018, at 17.13, Tom Sommer <mail at tomsommer.dk> wrote: >> >> >> On 2018-10-04 15:55, Timo Sirainen wrote: >>> On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote: >> >>>> Is this correct, and if so are there any plans to move dotlocks etc. >>>> to this

On 07 Apr 2016, at 14:49, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2016-04-06 21:09, Tom Sommer wrote: >> On 2016-04-06 20:38, Timo Sirainen wrote: >>> On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote: >>>> I'm switching quota backend to redis (from maildir++), so all my current usages are reset. >>>> I get that

Hi I have two server directors in ring and 5 dovecot servers (2.2.36) IP for IMAP and POP3 is a VIP (keepalived) What is the best solutions to get realy HA for 5 dovecot servers ? Maby corosync+pacemeker ? But this solution is too problematic and hardcore Why I need HA ? Doveadmin is too lazy and doveadm director does not know that one machine broke down and still sends traffic

On 2018-10-04 15:55, Timo Sirainen wrote: > On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote: >> Is this correct, and if so are there any plans to move dotlocks etc. >> to this directory? > > > What dotlocks? I guess mbox and Maildir have some locks that could be > moved there, but a better performance optimization for those > installations

On 2016-04-05 08:44, aki.tuomi at dovecot.fi wrote: >> On April 5, 2016 at 9:27 AM Tom Sommer <mail at tomsommer.dk> wrote: >> >> >> On 2016-04-04 20:22, aki.tuomi at dovecot.fi wrote: >> >> > Since the API is still a little beta, it will not return anything in >> > case >> > doveadm does not like the arguments (that is, calls

On 2016-04-06 20:38, Timo Sirainen wrote: > On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote: >> >> I'm switching quota backend to redis (from maildir++), so all my >> current usages are reset. >> >> I get that I can do "doveadm quota recalc -A", but it takes forever >> (and auth processes time out/crash). >>

On Mon, 22 Oct 2018 19:48:17 +0200 Tom Sommer <mail at tomsommer.dk> wrote: > On 2018-10-22 12:56, Mar?a Arrea wrote: > > > We use sabredav for caldav+cardav and roundcube+agendav for nice > > web ui :) > > > Is Sabre still maintained? http://sabre.io/ says 2018 is most recent version -- In modern fantasy (literary or governmental), killing people is the

> On May 2, 2016 at 9:56 AM Tom Sommer <mail at tomsommer.dk> wrote: > > > > On 2016-04-29 16:25, Matteo Gaito Test Account wrote: > > > i've search a lot in order to find a way to delete account by dovecot > > but i > > found only this way > > > > http://dovecot.org/list/dovecot/2011-November/079273.html > > > > It's

On 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2018-06-29 14:51, Timo Sirainen wrote: > >> v2.3.2 is mainly a bugfix release. It contains all the changes in >> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only >> bugs). Binary packages are already in https://repo.dovecot.org/ > > A simple "yum update"

We ran a load test using glusterfs and were able to deliver mail (I can't remember specifically how much per second, maybe 100 messages per second?) without any issues. We did use the glusterfs fuse client and not nfs, and used regular maildir. We developed a mail bot cluster that would deliver mail, and simultaneously receive and delete it with pop and IMAP and we ran into zero issues. We

I upgraded to beta7 from alpha4, and got this error during the auth process: dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=0.0.0.0 rip=0.0.0.0 resp=<hidden> dovecot: auth-worker(default): sql(webmaster at example.com,0.0.0.0): query: SELECT username as user, NULL as password FROM users WHERE username = 'webmaster at example.com' AND

> On May 1, 2017 at 8:26 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: > > > > > > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg > > and /var/log/messages are getting flooded by these errors: > > > > lmtp[45758]: segfault at

Hello Tom On 02.05.2017 11:19, Timo Sirainen wrote: > On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote: >> >> (gdb) bt full >> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298 >> _stream = <value optimized out> >> #1 0x00007fe98391ff32 in i_stream_concat_read_next (stream=0x1efe6c0) at istream-concat.c:77 >>

On 2017-05-02 09:35, Aki Tuomi wrote: > On 2017-05-02 10:20, Tom Sommer wrote: >> On 2017-05-01 19:26, Aki Tuomi wrote: >>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> >>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my >>>> dmesg >>>> and /var/log/messages