From owner-freebsd-stable@freebsd.org  Fri Jun 22 18:13:59 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 181851023409
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 22 Jun 2018 18:13:59 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9BF597A96A;
 Fri, 22 Jun 2018 18:13:58 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1fWQZM-000GX3-0i; Fri, 22 Jun 2018 20:14:00 +0200
Date: Fri, 22 Jun 2018 20:13:59 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>
Cc: freebsd-stable@freebsd.org, ed@freebsd.org
Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059,
 stable/11)
Message-ID: <20180622181359.GQ4028@home.opsec.eu>
References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org>
 <20180622155922.GA61217@plan-b.pwste.edu.pl>
 <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org>
 <b4074f85-bf12-b13b-a92f-69e4c3e84435@plan-b.pwste.edu.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b4074f85-bf12-b13b-a92f-69e4c3e84435@plan-b.pwste.edu.pl>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2018 18:13:59 -0000

Hi!

> >> Could you please give any advice or workaround for this issue?
> > I switched to a workaround for the time being which you might use as well in a similar way:
> >
> > #) configure fail2ban to use /var/log/faillog
> > #) run something like that in the background:
> >
> > 	nohup tail -q -F /var/log/fail2ban.log | logger -t fail2ban.filter -p daemon.notice &
> >
> > #) to let this workaround survive a reboot you need to use a script fired up from /etc/rc.d
> >
> >
> 
> I have rolled back to r334835. The issue has gone. Should a PR be
> created about this regression ?

Yes, please.

> BTW a few decent syslog daemons are available in /usr/ports/sysutils.

-- 
pi@opsec.eu            +49 171 3101372                    2 years to go !