[Pkg-libvirt-maintainers] Bug#867379: lead or red herring - around the systemd status of libvirtd

[Christian Ehrhardt]

I happened to find, that whenever the service is in the "bad state" so it
will loose the containers on restart it also misses this section in
"systemctl status"
    Tasks: 19 (limit: 32768)
   Memory: 7.7M
      CPU: 89ms

I compared to other systemd tools looking at this data:
- systemd-cgls matches the control group output and is good in all cases.
  The missing entries are more for accounting it seems.

- systemd-cgtop reports the number of tasks and memory even in the bad
  state where "systemctl status" does not

Looking further from there I found more by comparing
  $ systemctl show libvirtd

Comparison
1. exec start lists pid as 0 in bad case
2. Task/CPU/Mem tracking is near infinit values in bad case (unset?)

The pid listed in the good case his it's own PID, the bad case has 0.
MainPID=16252
[...]
ExecMainPID=16252
[...]
ExecStart ... pid=16252   <- here the bad case has 0

Note: analyzing that is already in the script I linked in the initial
report. So no update for that on this bug update.

I can't reproduce otherwise than uninstall/reinstall of the package yet.
But there the service is re-started by the maintainer scripts - checking if
I can find anything there to trim down the repro narrowing down what is
happening.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20170706/c6a3b073/attachment.html>