From owner-freebsd-ports@freebsd.org Fri Jun 22 13:12:21 2018 Return-Path: Delivered-To: freebsd-ports@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 8E567101B27C; Fri, 22 Jun 2018 13:12:21 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:401:2100::5:8a0e]) (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 2B2FD8FC19; Fri, 22 Jun 2018 13:12:17 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f1b:7801:4570:b981:3c60:950f] (p200300E97F1B78014570B9813C60950F.dip0.t-ipconnect.de [IPv6:2003:e9:7f1b:7801:4570:b981:3c60:950f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 41BzVw2YDJzkH; Fri, 22 Jun 2018 15:12:08 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net From: Michael Grimm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-Id: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> Date: Fri, 22 Jun 2018 15:12:05 +0200 To: Mailing List FreeBSD Ports , FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2018 13:12:21 -0000 Hi, this is 11.2-STABLE (r335532), and I am referring to the recent MFC of = syslogd modifications [1].=20 Because I cannot judge whether fail2ban lacks support for the renewed = syslogd or syslogd has an issue in receiving fail2ban messages I do = crosspost this mail to ports and stable. I do have fail2ban configured to report to SYSLOG: logtarget =3D SYSLOG syslogsocket =3D auto But now, after upgrading to the new syslogd fail2ban refuses to report = to syslogd; no single message gets recorded [2]. I did try to modify the syslogsocket setting to /var/run/log without = success. Pointing logtarget to a regular files tells me that fail2ban is = running as expected, it only lacks reporting to SYSLOG. #) Does anyone else has running py-fail2ban at >=3D r335059 and can = confirm my observations?=20 #) Any ideas how to debug this issue? Thank you in advance and regards, Michael [1] = https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revisi= on=3D335059&view=3Dmarkup&sortby=3Dfile [2] both syslogd and fail2ban are running at the host, thus another = issue with syslogd fixed in=20 = https://svnweb.freebsd.org/base?view=3Drevision&sortby=3Dfile&revision=3D3= 35314 does not apply