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> In-Reply-To: <BDE2979C-728D-4B29-B105-03FFC9A31EF1@ellael.org> References: <BDE2979C-728D-4B29-B105-03FFC9A31EF1@ellael.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180617145029.GB44323>