Hi,
I was trying to suppress user scope units that are considered failed due
to them requiring a SIGKILL. Typical log might be.
Oct 30 10:27:55 node989.example.ch systemd[1]: session-3804.scope:
Killing process 1550946 (node) with signal SIGKILL.
Oct 30 10:29:25 node989.example.ch systemd[1]: session-3804.scope: Still
around after SIGKILL. Ignoring.
Oct 30 10:29:25 node989.example.ch systemd[1]: session-3804.scope:
Failed with result 'timeout'.
Oct 30 10:29:25 node989.example.ch systemd[1]: session-3804.scope:
Consumed 1min 30.745s CPU time.
I doubt increasing the timeout will help. I had thought that a
# /etc/systemd/system/user-.slice.d/ignore-timeout.conf
[Slice]
SuccessExitStatus=SIGKILL
might help but alas SuccessExitStatus can only be set on a services it
seems.
Unfortunately the slice is not running inside the user service as its an
SSH session. (*)
user-12345.slice (#2235041)
→ user.invocation_id: 2e7b44d0a6e941b0a3bce61596f1c811
→ trusted.invocation_id: 2e7b44d0a6e941b0a3bce61596f1c811
├─user@12345.service … (#2235205)
│ → user.delegate: 1
│ → trusted.delegate: 1
│ → user.invocation_id: efcb2b8e231c4ef798354838a0f506d0
│ → trusted.invocation_id: efcb2b8e231c4ef798354838a0f506d0
│ └─init.scope (#2235245)
│ ├─910041 /usr/lib/systemd/systemd --user
│ └─910043 (sd-pam)
└─session-6568.scope (#2235445)
├─909805 sshd: me [priv]
├─910090 sshd: me@pts/35
├─910093 -bash
└─913356 sleep 900
Anyway to ignore that Scope unit timeout on shutdown of the scope.
Steve
(*) The fact that the login bash shell does not run inside the user
service with SSH is probably the underlying problem here.
Would be more than happy to change that if possible.
Alma 9, systemd-252-32.el9.
