root@lp1918735-g:~# dpkg -l|grep corosync
ii corosync 3.0.3-2ubuntu3 amd64
cluster engine daemon and utilities
ii libcorosync-common4:amd64 3.0.3-2ubuntu3 amd64
cluster engine common library
root@lp1918735-g:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-03-24 13:10:31 UTC; 17s
ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Main PID: 2886 (code=exited, status=15)
Mar 24 13:10:31 lp1918735-g corosync[2886]: [TOTEM ] Initializing transport
(Kronosnet).
Mar 24 13:10:31 lp1918735-g corosync[2886]: [TOTEM ] knet_handle_new failed:
File name too long (36)
Mar 24 13:10:31 lp1918735-g corosync[2886]: [KNET ] transport: Failed to set
socket buffer via force option 33: Operation not permitted
Mar 24 13:10:31 lp1918735-g corosync[2886]: [KNET ] transport: Unable to set
local socketpair receive buffer: File name too long
Mar 24 13:10:31 lp1918735-g corosync[2886]: [KNET ] handle: Unable to
initialize internal hostsockpair: File name too long
Mar 24 13:10:31 lp1918735-g corosync[2886]: [MAIN ] Can't initialize TOTEM
layer
Mar 24 13:10:31 lp1918735-g corosync[2886]: [MAIN ] Corosync Cluster Engine
exiting with status 15 at main.c:1531.
Mar 24 13:10:31 lp1918735-g systemd[1]: corosync.service: Main process exited,
code=exited, status=15/n/a
Mar 24 13:10:31 lp1918735-g systemd[1]: corosync.service: Failed with result
'exit-code'.
Mar 24 13:10:31 lp1918735-g systemd[1]: Failed to start Corosync Cluster Engine.
root@lp1918735-g:~# dpkg -l|grep corosync
ii corosync 3.0.3-2ubuntu3.1 amd64
cluster engine daemon and utilities
ii libcorosync-common4:amd64 3.0.3-2ubuntu3.1 amd64
cluster engine common library
root@lp1918735-g:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor
preset: enabled)
Active: active (running) since Wed 2021-03-24 13:12:16 UTC; 7s ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Main PID: 4880 (corosync)
Tasks: 9 (limit: 76563)
Memory: 84.2M
CGroup: /system.slice/corosync.service
└─4880 /usr/sbin/corosync -f
Mar 24 13:12:16 lp1918735-g corosync[4880]: [QUORUM] Members[0]:
Mar 24 13:12:16 lp1918735-g corosync[4880]: [SERV ] Service engine loaded:
corosync vote quorum service v1.0 [5]
Mar 24 13:12:16 lp1918735-g corosync[4880]: [QB ] server name: votequorum
Mar 24 13:12:16 lp1918735-g corosync[4880]: [SERV ] Service engine loaded:
corosync cluster quorum service v0.1 [3]
Mar 24 13:12:16 lp1918735-g corosync[4880]: [QB ] server name: quorum
Mar 24 13:12:16 lp1918735-g corosync[4880]: [TOTEM ] A new membership (1.5)
was formed. Members joined: 1
Mar 24 13:12:16 lp1918735-g corosync[4880]: [CPG ] downlist left_list: 0
received
Mar 24 13:12:16 lp1918735-g corosync[4880]: [QUORUM] Members[1]: 1
Mar 24 13:12:16 lp1918735-g corosync[4880]: [MAIN ] Completed service
synchronization, ready to provide service.
Mar 24 13:12:16 lp1918735-g systemd[1]: Started Corosync Cluster Engine.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918735
Title:
fails to start in unprivileged container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1918735/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
