From owner-freebsd-stable@freebsd.org Sun Jun 17 14:27:39 2018 Return-Path: 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 C7B461020ABA for ; Sun, 17 Jun 2018 14:27:39 +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 583C77010B for ; Sun, 17 Jun 2018 14:27:39 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae] (p200300E97F3E03016061D32E91BFAAAE.dip0.t-ipconnect.de [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae]) (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 417xQH1z1nz9mJ for ; Sun, 17 Jun 2018 16:27:35 +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: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Message-Id: Date: Sun, 17 Jun 2018 16:27:33 +0200 To: freebsd-stable@FreeBSD.org X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,RDNS_NONE,TW_VU 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-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 14:27:39 -0000 Hi, I am running service jails (VNET/bridge/epair) and a host at = 11.2-PRERELEASE r335282, upgraded from r334874 today. All syslog messages at each jail become forwarded to syslogd running at = the host. This setup worked for years. Today not a single syslog message = becomes forwarded to the host's syslogd. Host's syslogd can be reached from inside every jail, e.g.: jtest> nc -4vuw 1 10.x.y.z 514=20 Connection to 10.x.y.z 514 port [udp/syslog] succeeded! logger doesn't throw any error. No message will be forwarded to the = host's syslogd either: jtest> logger -4 10.x.y.z HELLO jtest> I cannot find any hint in src/UPDATING.=20 What did I miss? Anyone else with a silenced syslogd? Anyone running my setup with a noisy syslogd? Thank you in advance and regards, Michael