<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On 11 Jul 2019, at 10.13, Alessio Cecchi via dovecot <<a href="mailto:dovecot@dovecot.org" class="">dovecot@dovecot.org</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-15" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Hi,</p><p class="">I'm running some Dovecot servers configured with LVS + Director +
Backend + NFS and version 2.2.36.3 (a7d78f5a2).<br class="">
</p><p class="">In the last days I see an increased number of these error:</p><p class="">Error:
o_stream_send_istream(/nfs/mail/<a href="http://company.com/info/Maildir/.Sent/tmp/1562771349.M255624P9151.pop01" class="">company.com/info/Maildir/.Sent/tmp/1562771349.M255624P9151.pop01</a>)
failed: Broken pipe</p><p class="">always with action "Disconnected in APPEND", when users try to
upload a message in Sent or Drafts.</p></div></div></blockquote><div><br class=""></div><div>I think it simply means that Dovecot sees that the client disconnected while it was APPENDing the mail. Although I don't know why they would suddenly start now. And I especially don't understand why the error is "Broken pipe". Dovecot uses it internally when it closes input streams, so it's possibly that, but why would isn't that happening elsewhere then.. Did you upgrade your kernel recently? I guess it's also possible that there is some bug in Dovecot, but I don't remember any changes related to this for a long time.</div><div><br class=""></div><div>I guess it could actually be writing as well, because "Broken pipe" is set also for closed output streams, so maybe some failed NFS write could cause it (although it really should have logged a different error in that case, so if that was the reason this is a bug).</div><div><br class=""></div><div>Dovecot v2.3.x would log a different error depending on if the problem was reading or writing, which would make this clearer.</div><div><br class=""></div></div></body></html>