On Mon, 5 Jun 2017 09:56:34 -0700
Rick Stevens wrote:
> What new nonsense hath systemd wrought?
Is this stuff running in a container of some sort? There have been
issues with systemd, selinux and containers in the past and CGROUP
errors often point at container creation/promotion issues.
Only if sshd is doing something with a container. I see my
sshd_config file says: "UsePrivilegeSeparation yes" (not sandbox)
and that's the only container-like thing I see in there.
As far as I know, I've been running this stuff for years
and this has never happened till this weekend. But maybe
it always happened and some recent update is now making it
show up in logwatch?