From owner-freebsd-stable@freebsd.org Sun Jun 17 16:07:07 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 B9ED01000279 for ; Sun, 17 Jun 2018 16:07:07 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 45A5F73A04 for ; Sun, 17 Jun 2018 16:07:06 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 8DD5B62A5; Mon, 18 Jun 2018 01:07:04 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 1BA05716F; Mon, 18 Jun 2018 01:07:04 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id D18E7716E; Mon, 18 Jun 2018 01:07:03 +0900 (JST) Date: Mon, 18 Jun 2018 01:06:20 +0900 (JST) Message-Id: <20180618.010620.1946151016518038027.yasu@utahime.org> To: freebsd-stable@FreeBSD.org Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 From: Yasuhiro KIMURA In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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 16:07:07 -0000 From: Michael Grimm Subject: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Date: Sun, 17 Jun 2018 16:27:33 +0200 > I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE r335282, upgraded from r334874 today. There was a large MFC about syslogd at r335059: https://svnweb.freebsd.org/base?view=revision&revision=335059 ---------------------------------------------------------------------- MFC r309925, r309931, r309933, r310035, r310278, r310310, r310311, r310323, r310349, r310350, r310351, r310352, r310383, r310384, r310385, r310386, r310393, r310453, r310456, r310494, r310504, r310528, r310890, r310893, r310974, r311918, r312921, r313357, r314563, r314585, r314642, r315322, r315618, r315620, r315622, r315643, r316951, r316973, r326338, r326339, r326573, r331270, r332099, r332110, r332111, r332118, r332165, r332510 and r332511. This commit brings syslogd(8) in sync with the copy in HEAD. The key improvement of this change is that it adds support for RFC 5424 log ingestion and exposition (enabled by passing in -O rfc5424). This allows for saner logging in environments with multiple time zones. The list of changes to merge back were obtained by running: svn mergeinfo --show-revs eligible \ ^/head/usr.sbin/syslogd ^/stable/11/usr.sbin/syslogd Of the commits listed, r314436, r325188 and r326025 were excluded, as they affect a significant number of unrelated files (SPDX and 4-clause license renumbering). Due to the large number of directly committed changes on this branch, I had no choice but to perform the merge as follows: svn merge --accept=theirs-full -c ^/head . This would, however, cause some unrelated changes, such as undoing the r333356 (MFC of r332877) and still adding the SPDX tag to syslogd.c. These have been reverted manually. Requested by: Dave Cottlehuber Thanks to: dim@ for sharing his insight on hackers@ ---------------------------------------------------------------------- So how about take following steps? 1. svn update -r 335058 /usr/src 2. Rebuild and reinstall /usr/sbin/syslogd and /usr/bin/wall on both host and jail. 3. Restart syslogd on both host and jail. And if the problem is dissapeared, then you should open bug report. Best, --- Yasuhiro KIMURA