Date: Tue, 25 Apr 2023 20:44:22 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271069] syslogd service inside client jail requires restart before server jail receives logs Message-ID: <bug-271069-227-NRtMOaZFJa@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271069-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271069 Siva Mahadevan <me@svmhdvn.name> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |me@svmhdvn.name --- Comment #2 from Siva Mahadevan <me@svmhdvn.name> --- I'm just going to use `sockstat -l6` since this is an IPv6-only setup. I tried something simpler and noticed something interesting. After running `service jail onestart logs` on the jailhost, `sockstat -l6` on both the jailhost and inside the logs jail does *NOT* show `syslogd`. However, once I run `service syslogd restart` inside the jail, `sockstat -l6` shows syslogd successfully. I think this is a simpler repro and showcases the same problem, since on the client side, failure to bind to the address and port will be the root cause of the problem. Let me know if you still need the full syslog output (and at which point in time in the repro?). -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271069-227-NRtMOaZFJa>