Re: doveadm sync - I/O has stalled

2023-01-01 Thread Timo Sirainen
On 2. Jan 2023, at 3.26, Timo Sirainen wrote: > > On 2. Jan 2023, at 3.21, Timo Sirainen wrote: >> >> >>> It may happen, but it is hard to reproduce. >> >> Are you able to try if this patch happens to fix it? : > > Actually, looking at it slightly more, there may be another bug in it, >

Re: doveadm proxy list has strange entries

2023-01-01 Thread Tobias Florek
Thank you for the answer. So I'll just have to filter it for now.

Re: doveadm proxy list has strange entries

2023-01-01 Thread Timo Sirainen
On 30. Dec 2022, at 23.40, Tobias Florek wrote: > > When getting the proxy list I get the following entries. > > # doveadm -f flow proxy list > username=u...@example.com proto=imap src ip=10.254.0.13 dest ip=172.23.6.194 > port=143 > username=username proto=service src ip=src-ip dest

Re: doveadm sync - I/O has stalled

2023-01-01 Thread Timo Sirainen
On 2. Jan 2023, at 3.21, Timo Sirainen wrote: > > >> It may happen, but it is hard to reproduce. > > Are you able to try if this patch happens to fix it? : Actually, looking at it slightly more, there may be another bug in it, although I'm not sure how it affects the behavior. So try this

Re: doveadm sync - I/O has stalled

2023-01-01 Thread Timo Sirainen
Hi, > But when dsync connects over tcps, > it uses function implementations in lib-ssl-iostream to send and receive data. > And this simplified call stack would result in some data are read when > calling o_stream_uncork > > o_stream_uncork => o_stream_flush => o_stream_ssl_flush_buffer => >