Hello Bert,
We are not yet fully disabling sysv related scripts because there are
systems that are not, yet, using systemd. Not for this case, but, one of
these examples is windows WSL environment, where systemd is not
supported yet. Just wanted to mention this to show there are some other
things to be taken in consideration when dropping support, entirely, for
sysv scripts, for example.
Just a quick example on corosync running inside WSL environment:
rafaeldtinoco@lenovo:~$ uname -a
Linux lenovo 4.4.0-18362-Microsoft #476-Microsoft Fri Nov 01 16:53:00 PST 2019
x86_64 x86_64 x86_64 GNU/Linux
rafaeldtinoco@lenovo:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.10
Release: 19.10
Codename: eoan
$ sudo corosync -f
Mar 20 01:49:47 notice [MAIN ] Corosync Cluster Engine 3.0.1 starting up
Mar 20 01:49:47 info [MAIN ] Corosync built-in features: dbus monitoring
watchdog augeas systemd xmlconf snmp pie relro bindnow
Mar 20 01:49:47 warning [MAIN ] Could not lock memory of service to avoid page
faults: Function not implemented (38)
Mar 20 01:49:47 notice [TOTEM ] Initializing transport (UDP/IP Unicast).
Mar 20 01:49:47 warning [TOTEM ] Could not set traffic priority: Protocol not
available (92)
Mar 20 01:49:47 notice [TOTEM ] The network interface [127.0.0.1] is now up.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
map access [0]
Mar 20 01:49:47 info [QB ] server name: cmap
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync configuration
service [1]
Mar 20 01:49:47 info [QB ] server name: cfg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster closed
process group service v1.01 [2]
Mar 20 01:49:47 info [QB ] server name: cpg
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync profile
loading service [4]
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync resource
monitoring service [6]
Mar 20 01:49:47 warning [WD ] Watchdog not enabled by configuration
Mar 20 01:49:47 warning [WD ] resource load_15min missing a recovery key.
Mar 20 01:49:47 warning [WD ] resource memory_used missing a recovery key.
Mar 20 01:49:47 info [WD ] no resources configured.
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync watchdog
service [7]
Mar 20 01:49:47 notice [QUORUM] Using quorum provider corosync_votequorum
Mar 20 01:49:47 notice [QUORUM] This node is within the primary component and
will provide service.
Mar 20 01:49:47 notice [QUORUM] Members[0]:
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync vote quorum
service v1.0 [5]
Mar 20 01:49:47 info [QB ] server name: votequorum
Mar 20 01:49:47 notice [SERV ] Service engine loaded: corosync cluster quorum
service v0.1 [3]
Mar 20 01:49:47 info [QB ] server name: quorum
Mar 20 01:49:47 notice [TOTEM ] adding new UDPU member {127.0.0.1}
Mar 20 01:49:47 notice [TOTEM ] A new membership (1:28) was formed. Members
joined: 1
Mar 20 01:49:47 warning [CPG ] downlist left_list: 0 received
Mar 20 01:49:47 notice [QUORUM] Members[1]: 1
Mar 20 01:49:47 notice [MAIN ] Completed service synchronization, ready to
provide service.
--
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/1809682
Title:
"systemctl enable corosync-qdevice.service" fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1809682/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
