The discussion in the systemd bug made it clear that this isn't a libvirt-bug.
It is a systemd issue since v~244.
[1] has a proposed fix, that if accepted we should backport to Focal.
This issue has the chance to clobber any output to journald, the libvirt
case just happened to be a nice trigger
Reported to systemd https://github.com/systemd/systemd/issues/15654
** Bug watch added: github.com/systemd/systemd/issues #15654
https://github.com/systemd/systemd/issues/15654
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix submitted upstream, let's see what comments on that will be
=> https://www.redhat.com/archives/libvir-list/2020-April/msg01474.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875708
Title:
Yeah tests show (c) isn't really needed so let me skip that.
Note: happens with systemd 245.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875708
Title:
Truncated messages during shutdown
To
This seems to be a combination of two effects in new systemd.
- The changing PID is due to the output reporting the PIDs of the gettext calls
used for translation.
- The gettext output is buffered and that output might be clobbered if programs
end too soon for systemd logging to pick it up
OK, thank you for looking at this bug!
It is indeed cosmetic, but some users with more serious problems with
libvirt may be sent to wrong paths if they see those messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok I can reproduce this in a container without much setup (no guests needed):
Watching the journal when running starr/stop:
root@f:~# systemctl start libvirt-guests
Apr 30 05:45:55 f systemd[1]: Starting Suspend/Resume Running libvirt Guests...
Apr 30 05:45:55 f systemd[1]: Finished
The truncated messages might just be an issue due to output buffering,
but lets analyze this one by one. First of all I'm wondering more about
the different PIDs in the output ...
I think I can see the same when I make the guests in a way that it runs a bit
longer:
from journalctl -u:
Apr 22
Hi Laurent,
this is very odd - it is a service that just has a start/end action.
I wonder how we could call this thrice on shutdown.
First of all - is this reproducible and showing every time so that we
can try to debug it a bit - or is it only sometimes? I'm assuming it is
reproducible since you
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1875708
Title:
Truncated messages during shutdown
To manage notifications
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875708
Title:
Truncated messages during shutdown
To manage notifications about this bug
Truncated messages can be seen on this screenshot.
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1875708/+attachment/5362744/+files/IMG_20200421_172920.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
12 matches
Mail list logo
