similar to: shutdown_clients ignored on Director upgrade/restart

On 8.7.2019 14.54, Tom Sommer via dovecot wrote: > > On 2019-07-08 13:36, Tom Sommer via dovecot wrote: >> I rotate logs every night on my Director, running "doveadm log reopen" > > It happens on "/etc/init.d/dovecot restart", not "doveadm log reopen" > - sorry > > So it happens when you run killproc on dovecot > > --- > Tom Do

I try to restart dovecot 2.2.24 (for changing limits) without killing all IMAP and POP3 sessions. dovecot(1) tells me: When shutdown_clients is set to no, existing sessions will continue to use the old settings, after a dovecot reload. Also all sessions will keep alive after a dovecot stop. By default all active sessions will be shut down. According to my

I rotate logs every night on my Director, running "doveadm log reopen" I've noticed a problem with processes not closing correctly, they can be open for days and cause corrupt index files because they are connected to different backends (so it writes to the wrong server when the process disconnects) 23518 ? S 140:53 dovecot/anvil [4 connections] 23519 ? S

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 18.05.2017 10:55, Tom Sommer wrote: > On 2017-05-18 09:36, Teemu Huovila wrote: >> 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 >>>>

My director has started segfaulting since upgradeing to 2.3.2: # gdb /usr/libexec/dovecot/imap-login ./core.9757 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the

--- Tom On 2017-05-18 10:05, Teemu Huovila wrote: > On 18.05.2017 10:55, Tom Sommer wrote: >> On 2017-05-18 09:36, Teemu Huovila wrote: >>> 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

Hello, I have two mail servers and am also experiencing sporadic replication errors over tcps, similar to Reuben. Each server is running Dovecot 2.3.11.3 (502c39af9) on Debian 10.6. *Log entries from MX1* Nov 18 00:39:26 mx1 dovecot: dsync-local(user at example.com)<Ow3zAjWxtF+TDgAAPHKnuQ>: Error: dsync(mx2.example.com): I/O has stalled, no activity for 600 seconds (last sent=mailbox,

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

Hi Timo & Dovecot users, We have a 2-node director setup which front-ends for 4 nodes which share a clustered filesystem (GFS). All nodes run Dovecot 2.0.18. Approximately 40k users, but typically only a few thousand active at any time. The director nodes run sendmail, which deliver mail "locally" using LMTP to the director, which then feeds to SMTP on the real servers (also

On 5 Jul 2018, at 15.12, Tom Sommer <mail at tomsommer.dk> wrote: > > My director has started segfaulting since upgradeing to 2.3.2: > > #0 0x00007fa19b3ec6ed in i_stream_get_root_io () from /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #1 0x00007fa19b3ec9b5 in i_stream_set_input_pending () from /usr/lib64/dovecot/libdovecot.so.0 > No symbol

Hi I am seeing a lot of clients time out on my Director. I'm wondering if this is "normal" or there is some opportunity to tweak something? Log line: imap-login: Info: proxy(user at example.com): disconnecting 1.2.3.4 (Disconnected by client: read(size=433) failed: Connection timed out(37s idle, in=939, out=3083)): user=<user at example.com>, method=CRAM-MD5, rip=1.2.3.4,

> 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

On 2017-05-18 09:36, Teemu Huovila wrote: > 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

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

Thanks. We'll take a look at this. ---Aki TuomiDovecot oy -------- Original message --------From: Tom Sommer <mail at tomsommer.dk> Date: 05/07/2018 16:01 (GMT+01:00) To: Aki Tuomi <aki.tuomi at dovecot.fi> Cc: Dovecot <dovecot at dovecot.org> Subject: Re: 2.3.2 director imap-login segfaults # gdb /usr/libexec/dovecot/imap-login ./core.34022 GNU gdb (GDB) Red Hat

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:09.openssh Security Advisory The FreeBSD Project Topic: Remote denial of service in OpenSSH Category: contrib Module: OpenSSH Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:09.openssh Security Advisory The FreeBSD Project Topic: Remote denial of service in OpenSSH Category: contrib Module: OpenSSH Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:09.openssh Security Advisory The FreeBSD Project Topic: Remote denial of service in OpenSSH Category: contrib Module: OpenSSH Announced: