On 17. Jun 2018, at 16:27, Michael Grimm <trash...@ellael.org> 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.

I do believe that this commit might be the cause: 
https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revision=335059&view=markup&sortby=file

But I do have to admit, that I do not understand what changed and what would 
cause my syslogd become silenced, though.

Any hints?

> 
> 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?
> 
> Thank you in advance and regards,
> Michael
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to