search for: doveadm_connection

...l to me)? The usage is explained at the beginning > of the script. At least in theory we could then debug with the core file, > although I've had some trouble even then. > > But just in case the core doesn't work, could you also do: > > bt full > fr 8 > p *((struct doveadm_connection *)io->context) > p *((struct doveadm_connection *)io->context)->input I'm sending you the tarball created with core-tar; and just in case: root at imap-front4:/usr/local/src/dovecot-2.2.36# gdb ./src/director/.libs/director /var/tmp/ core.10733 GNU gdb (GDB) 7.4.1-debian Copyrigh...

...cript. At least in theory we could then debug with the core file, >> > although I've had some trouble even then. >> > >> > But just in case the core doesn't work, could you also do: >> > >> > bt full >> > fr 8 >> > p *((struct doveadm_connection *)io->context) >> > p *((struct doveadm_connection *)io->context)->input >> >> I'm sending you the tarball created with core-tar; and just in case: > > Thanks, the core worked fine. Does the attached patch (on top of the previous one) help? > > <...

...0, format=0x805c274 "file %s: line %d (%s): assertion failed: (%s)", args=0xbf839ce4 "4\370\005\bI\004") at failures.c:670 #5 0xb75ce35e in i_panic (format=format at entry=0x805c274 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 #6 0x080574f7 in doveadm_connection_deinit (_conn=_conn at entry=0xbf839d60) at doveadm-connection.c:1097 #7 0x08057f03 in doveadm_connection_input (conn=0x0) at doveadm-connection.c:1051 #8 0xb76613db in io_loop_call_io (io=0x82fb780) at ioloop.c:600 #9 0xb7662e1e in io_loop_handler_run_internal (ioloop=ioloop at entry=0x82bd648...

...and the related binaries (e.g. just email to me)? The usage is explained at the beginning of the script. At least in theory we could then debug with the core file, although I've had some trouble even then. But just in case the core doesn't work, could you also do: bt full fr 8 p *((struct doveadm_connection *)io->context) p *((struct doveadm_connection *)io->context)->input -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180919/c452a2e6/attachment.html>

...beginning > > of the script. At least in theory we could then debug with the core file, > > although I've had some trouble even then. > > > > But just in case the core doesn't work, could you also do: > > > > bt full > > fr 8 > > p *((struct doveadm_connection *)io->context) > > p *((struct doveadm_connection *)io->context)->input > > I'm sending you the tarball created with core-tar; and just in case: Thanks, the core worked fine. Does the attached patch (on top of the previous one) help? -------------- next part ---------...

...could then debug with the core file, >>> > although I've had some trouble even then. >>> > >>> > But just in case the core doesn't work, could you also do: >>> > >>> > bt full >>> > fr 8 >>> > p *((struct doveadm_connection *)io->context) >>> > p *((struct doveadm_connection *)io->context)->input >>> >>> I'm sending you the tarball created with core-tar; and just in case: >> >> Thanks, the core worked fine. Does the attached patch (on top of the previous one) h...

Hi would it be possible to consider a new parameter for replication: doveadm_local_ip which allows the source ip address to be set when connection to a remote dovecot for replication? It could be useful when the network interface has multiple ips and a specific one is used for mail services. See attached proposal. I tested against 2.2.36 only. It applies correctly against 2.3.4 with a warning,.

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