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@25130.service: Failed at step CGROUP spawning /usr/lib/systemd/systemd: No such file or directory: 196 Time(s) user@25130.service: Job user@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?
On 06/05/2017 04:35 AM, Tom Horsley wrote:
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@25130.service: Failed at step CGROUP spawning /usr/lib/systemd/systemd: No such file or directory: 196 Time(s) user@25130.service: Job user@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?
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. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - "People tell me I look at the dark side. That's not true. I have - - the heart of a small boy......in a jar right here on my desk." - - -- Stephen King - ----------------------------------------------------------------------
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?
-
Rick Stevens -
Tom Horsley