Dependency failed for session? WTF?

Anyone know what this gibberish that shows up in my logwatch means? Dependency failed for Session 10084 of user nvtest.: 1 Time(s) Dependency failed for Session 10363 of user nvtest.: 1 Time(s) ... Dependency failed for User Manager for UID 25130.: 59 Time(s) session-10084.scope: Job session-10084.scope/start failed with result 'dependency'.: 1 Time(s) session-10363.scope: Job session-10363.scope/start failed with result 'dependency'.: 1 Time(s) ... user-25130.slice: Start request repeated too quickly.: 118 Time(s) user(a)25130.service: Failed at step CGROUP spawning /usr/lib/systemd/systemd: No such file or directory: 196 Time(s) user(a)25130.service: Job user(a)25130.service/start failed with result 'dependency'.: 59 Time(s) Notes: User nvtest is UID 25130 tomh> ls -l /usr/lib/systemd/systemd -rwxr-xr-x 1 root root 1641008 Feb 7 08:05 /usr/lib/systemd/systemd* The CGROUP error makes no sense because /usr/lib/systemd/systemd clearly does exist. User nvtest is used to run testbeds via ssh, all those errors almost certainly happened when a test run was using my system as a remote test target and logging in via ssh for each individual test to run a specific remote program (not a normal shell, though that remote program usually starts a shell). Meanwhile, despite all these silly errors in the log, the actual test run appeared to work fine. What new nonsense hath systemd wrought?