<div>                I meant upstream is doing the right thing when fail2ban-client flushlogs exits with an error code when fail2ban is NOT running. The word NOT was omitted in my previous message.<br><br><br>            </div>            <div class="yahoo_quoted" style="margin:10px 0px 0px 0.8ex;border-left:1px solid #ccc;padding-left:1ex;">                        <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">                                <div>                    On Wednesday, April 15, 2020, 09:35:21 AM GMT+1, Ron Varburg <ronvarburg@yahoo.com> wrote:                </div>                <div><br></div>                <div><br></div>                <div><div id="yiv3449203201"><div><div>                Hello,<br clear="none">I won't follow your suggestion to report it upstream. I think he does the right thing<br clear="none">when fail2ban-client flushlogs exits with an error code when fail2ban is running.<br clear="none">That said, I think logrotate shouldn't fail either in these circumstances. It could be<br clear="none">that the administrator stopped fail2ban for his own reasons, or that he just installed<br clear="none">the package and still hasn't ran it at all. It could also be there is a problem and<br clear="none">fail2ban stopped running without any one aware of that. And there could be other<br clear="none">circumstances why fail2ban is not running. Still, I think the right action, if at all, to<br clear="none">make someone aware of it is not by creating logrotate failures.<br clear="none">            </div>            <div class="yiv3449203201yqt2479877534" id="yiv3449203201yqt64794"><div class="yiv3449203201yahoo_quoted" style="margin:10px 0px 0px 0.8ex;border-left:1px solid #ccc;padding-left:1ex;">                                                <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">                                <div>                    On Tuesday, April 14, 2020, 10:45:15 AM GMT+1, Sylvestre Ledru <sylvestre@debian.org> wrote:                </div>                <div><br clear="none"></div>                <div><br clear="none"></div>                <div><div dir="ltr">Hello<br clear="none"><br clear="none">Thanks for your patch!<br clear="none"><br clear="none">Le 14/04/2020 à 11:30, Ron Varburg a écrit :<br clear="none">> Package: fail2ban<br clear="none">> Version: 0.10.2-2.1<br clear="none">> Severity: normal<br clear="none">> Tags: patch<br clear="none">> <br clear="none">> The following patch:<br clear="none">> 1. Prevents logrotate failures when fail2ban doesn't run for any reason.<br clear="none">>      When fail2ban  isn't running, fail2ban-client flushlogs exits with an error<br clear="none">>      code. I think announcing fail2ban isn't running should not be made by<br clear="none">>      making logrotate to fail.<br clear="none">This should be fixed upstream in "fail2ban-client flushlogs" I think.<br clear="none">Could you please report an issue there?<div class="yiv3449203201yqt0275911752" id="yiv3449203201yqtfd22365"><br clear="none"><br clear="none">> 2. Doesn't rotate empty log files.</div><br clear="none">agreed & pushed. thanks<br clear="none"><br clear="none">Cheers,<br clear="none">Sylvestre<div class="yiv3449203201yqt0275911752" id="yiv3449203201yqtfd16105"><br clear="none"></div></div></div>            </div>                                </div></div></div></div></div>            </div>                </div>