From owner-freebsd-stable@freebsd.org  Sun Jun 17 14:50:32 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 2AF401021D95
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 17 Jun 2018 14:50:32 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from mail.in-addr.com (mail.in-addr.com
 [IPv6:2a01:4f8:191:61e8::2525:2525])
 (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 BB70970F3E
 for <freebsd-stable@FreeBSD.org>; Sun, 17 Jun 2018 14:50:31 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from gjp by mail.in-addr.com with local (Exim 4.91 (FreeBSD))
 (envelope-from <gpalmer@freebsd.org>)
 id 1fUZ0f-0005Ws-OG; Sun, 17 Jun 2018 15:50:29 +0100
Date: Sun, 17 Jun 2018 15:50:29 +0100
From: Gary Palmer <gpalmer@freebsd.org>
To: Michael Grimm <trashcan@ellael.org>
Cc: freebsd-stable@FreeBSD.org
Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282
Message-ID: <20180617145029.GB44323@in-addr.com>
References: <BDE2979C-728D-4B29-B105-03FFC9A31EF1@ellael.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BDE2979C-728D-4B29-B105-03FFC9A31EF1@ellael.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: gpalmer@freebsd.org
X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false
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: Sun, 17 Jun 2018 14:50:32 -0000

On Sun, Jun 17, 2018 at 04:27:33PM +0200, Michael Grimm wrote:
> 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 
> 	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. 
> 
> What did I miss?
> Anyone else with a silenced syslogd?
> Anyone running my setup with a noisy syslogd?

Hi,

UDP is connectionless, so the client has no way of knowing if the
connection succeeded or not.  If you put in port 515 I suspect you'd
get the same result from your 'nc' attempt.

Is syslogd on the host running with '-s'?  If so, that'll stop it
from accepting any remote log events.

Regards,

Gary