You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
services loosing track of their Tasks
Missing the line like: "Tasks: 16 (limit: 32768)" on sytsemctl status output
Steps to reproduce the problem
TL;DR a systemctl daemon-reload triggers the bug, but the following sequence outlines the issue.
It does:
check all running services and proves they "know" about their tasks.
Then it calls daemon reload
proves all services "forgot" their Tasks
Restarts a service (any of them does the trick)
shows that now all services remember their tasks again
#!/bin/bash
SERVICES="$(systemctl list-units --type=service | grep -v -E '(user|getty)' | awk '/running/{print $1}')"
status () {
for srv in $SERVICES; do
printf "%40s%s\n" "$srv : " "$(systemctl status $srv | grep Tasks)"
done
}
status
systemctl daemon-reload
status
# any service restart would do
systemctl restart cron.service
status
I happened to realize that while the output of "systemctl status " does not list the tasks other system tools like systemd-cgtop work as expected
This might sound like an "just bad output" issue, but in fact I got to this analysis by tracing down a debian bug which looses all libvirt-lxc containers on a service restart when coming from that bad state.
I might overlook something, but since it seems fairly reproducible and it exceeds my systemd-foo now.
So I hoped filing this bug might help get some experts to reproduce, comment and look into it.
The text was updated successfully, but these errors were encountered:
This seems to have been fixed by #5619, but the patch has not been backported yet. Is there any chance you could apply the patch and check that it works for you?
Hi,
thanks for pointing out the potential fix.
It applied with just a few offsets to latest Ubuntu so I went and built an experimental package in a ppa.
Verifying with that proved to be the fix I need.
It fixes the simple reproduction case that I listed above, as well as resolving the issue of the service loosing all containers if restarted from the "bad state".
Thanks a lot, closing as upstream the fix is known and good.
Submission type: Bug report
systemd version the issue has been seen with:
233-10 (Debian)
233-8ubuntu2 (Ubuntu)
232-21ubuntu2 (Ubuntu)
Used distribution
Expected behaviour:
keeping track of Tasks on daemon-reload
Unexpected behaviour
services loosing track of their Tasks
Missing the line like: "Tasks: 16 (limit: 32768)" on sytsemctl status output
Steps to reproduce the problem
TL;DR a systemctl daemon-reload triggers the bug, but the following sequence outlines the issue.
It does:
A sample output of such looks like:
Additional notes:
I might overlook something, but since it seems fairly reproducible and it exceeds my systemd-foo now.
So I hoped filing this bug might help get some experts to reproduce, comment and look into it.
The text was updated successfully, but these errors were encountered: