Modifying the pre/post-inst files I found that really virtlogd is just
active by this sysv accident that is left.
For virtlockd as outlined it fails to enable at:
$ deb-systemd-invoke start virtlockd.service
virtlockd.service is a disabled or a static unit, not starting it.
virtlogd behaves the same way in regard to this command.
Well actually this should be correct I think.
The socket is enabled:
# systemctl status virtlockd.socket
● virtlockd.socket - Virtual machine lock manager socket
Loaded: loaded (/lib/systemd/system/virtlockd.socket; enabled; vendor
preset: enabled)
Active: active (listening) since Mon 2017-11-06 14:22:48 UTC; 13min ago
Listen: /var/run/libvirt/virtlockd-sock (Stream)
And the service is inactive (by being indirect) as it is an
Also=virtlockd.socket
# systemctl status virtlockd.service
● virtlockd.service - Virtual machine lock manager
Loaded: loaded (/lib/systemd/system/virtlockd.service; indirect; vendor
preset: enabled)
Active: inactive (dead)
Docs: man:virtlockd(8)
http://libvirt.org
I was able to activate it through that socket and this matches
https://libvirt.org/locking-lockd.html#sanlock
All that said, I'll suggest that change to provide the defaults file
correctly to Debian now.
** Description changed:
- Not sure this is an issue yet or a problem with my test setup I have
- seen this.
+ virtlockd has no defaults file installed /etc/default/virtlockd
- But worth to document and trace down at sometime.
- On Artful I have seen:
- Setting up libvirt-daemon-system (3.6.0-1ubuntu6) ...
- virtlockd.service is a disabled or a static unit, not starting it.
+ This was partially fixed in my contrib to Debian, but our removal of the
+ related sysv script rendered it non-working again (Debian didn't have
+ that for some time so they are broken as well).
- Matching that:
- $ sudo systemctl status virtlockd --no-pager
- ● virtlockd.service - Virtual machine lock manager
- Loaded: loaded (/lib/systemd/system/virtlockd.service; indirect; vendor
preset: enabled)
- Active: inactive (dead)
- Docs: man:virtlockd(8)
- http://libvirt.org
-
- As I said it might be my test env, but that should be checked in more
- detail as soon as time permits.
+ Note:
+ I also evaluated that it is correct that the service isn't started after
install - that is ok (socket activated, details see below).
** Summary changed:
- virtlockd not starting
+ /etc/default/virtlockd not installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729516
Title:
/etc/default/virtlockd not installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1729516/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
