Date: Tue, 11 Oct 2022 20:38:15 +0200 From: Michael Grimm <trashcan@ellael.org> To: freeBSD ports <freebsd-ports@FreeBSD.org> Cc: "cy@freebsd.org" <cy@FreeBSD.org>, Cy Schubert <Cy.Schubert@cschubert.com> Subject: Re: security/py-fail2ban quits working after some hours Message-ID: <281556A3-5C87-412B-8867-32EADA1264DB@ellael.org> In-Reply-To: <BE17DDA9-FBA4-4EA5-B685-6D5E9DEB39D1@ellael.org> References: <6EF1B25D-3121-4FA1-BF47-DCE1FFD64A5E@ellael.org> <20221010204219.4A3ED19F@slippy.cwsent.com> <pqrnp6nq-7p8o-19o4-pq24-26p19qr733sn@mx.roble.com> <20221011042427.78E0BD1@slippy.cwsent.com> <BE17DDA9-FBA4-4EA5-B685-6D5E9DEB39D1@ellael.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Grimm <trashcan@ellael.org> wrote: > Cy Schubert <Cy.Schubert@cschubert.com> wrote >> I've been able to reproduce the problem here. Please try the attached = patch=20 >> obtained from our upstream. It fixes a dovecot regression that crept = into=20 >> the latest release. >=20 > Yes, I am running dovecot jails at both servers. >=20 > Like Roger, truss reports "ERR#60 'Operation timed out'", only. >=20 > I did apply your patch, and both instances are up running. I will = report back. But that will take some hours to observe. Ok, after that many hours both fail2ban-servers are up running without = an issues. Thanks and regards, Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?281556A3-5C87-412B-8867-32EADA1264DB>