[Bug 1918735] Re: fails to start in unprivileged container
> Doesn't seem to be fixed in Focal > Continuing regardless, as the handle is not privileged. Expect poor performance! that is fixed -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
Doesn't seem to be fixed in Focal (deploying Masakari Charm on Openstack with Juju 2.9.5) : Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync notice [MAIN ] Corosync Cluster Engine 3.0.3 starting up Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync info[MAIN ] Corosync built-in features: dbus monitoring watchdog augeas systemd xmlconf vqsim nozzle snmp pie relro bindnow Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync warning [MAIN ] Could not set SCHED_RR at priority 99: Operation not permitted (1) Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync warning [MAIN ] Could not set priority -2147483648: Permission denied (13) Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync warning [MAIN ] Could not increase RLIMIT_MEMLOCK, not locking memory: Operation not permitted (1) Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync notice [TOTEM ] Initializing transport (Kronosnet). Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync warning [TOTEM ] knet_handle_new failed, trying unprivileged: File name too long (36) Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync info[TOTEM ] totemknet initialized Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via force option 33: Operation not permitted Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Unable to set local socketpair receive buffer: File name too long Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] handle: Unable to initialize internal hostsockpair: File name too long Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 8 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 7 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 8 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 7 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 8 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 7 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 8 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 7 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 8 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 7 to value 8388608: capped at 425984 Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Continuing regardless, as the handle is not privileged. Expect poor performance! Jul 05 13:15:57 [15946] juju-97b917-3-lxd-3 corosync error [KNET ] transport: Failed to set socket buffer via option 8 to value 8388608: capped at 425984 Jul 05
[Bug 1918735] Re: fails to start in unprivileged container
** Changed in: corosync (Debian) Status: New => Fix Released -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
This bug was fixed in the package corosync - 3.0.3-2ubuntu2.1 --- corosync (3.0.3-2ubuntu2.1) focal; urgency=medium * d/p/lp1911904-Don-t-lock-all-current-and-future-memory-if-can-t-in.patch: - Don't mlockall() if setrlimit() fails (LP: #1911904) * d/p/lp1918735-try-unprivileged-knet-handle-new.patch: - Retry knet_handle_new without privileged flag (LP: #1918735) * d/t: don't skip tests now that we fixed crashing in container -- Dan Streetman Wed, 10 Mar 2021 13:00:12 -0500 ** Changed in: corosync (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
This bug was fixed in the package corosync - 3.0.3-2ubuntu3.1 --- corosync (3.0.3-2ubuntu3.1) groovy; urgency=medium * d/p/lp1911904-Don-t-lock-all-current-and-future-memory-if-can-t-in.patch: - Don't mlockall() if setrlimit() fails (LP: #1911904) * d/p/lp1918735-try-unprivileged-knet-handle-new.patch: - Retry knet_handle_new without privileged flag (LP: #1918735) * d/t: don't skip tests now that we fixed crashing in container -- Dan Streetman Wed, 10 Mar 2021 12:58:00 -0500 ** Changed in: corosync (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
root@lp1918735-f:~# dpkg -l | grep corosync ii corosync 3.0.3-2ubuntu2amd64 cluster engine daemon and utilities ii libcorosync-common4:amd643.0.3-2ubuntu2amd64 cluster engine common library root@lp1918735-f:~# 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:14:36 UTC; 12s ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 15358 (code=exited, status=15) Mar 24 13:14:36 lp1918735-f corosync[15358]: [TOTEM ] Initializing transport (Kronosnet). Mar 24 13:14:36 lp1918735-f corosync[15358]: [TOTEM ] knet_handle_new failed: File name too long (36) Mar 24 13:14:36 lp1918735-f corosync[15358]: [KNET ] transport: Failed to set socket buffer via force option 33: Operation not permitted Mar 24 13:14:36 lp1918735-f corosync[15358]: [KNET ] transport: Unable to set local socketpair receive buffer: File name too long Mar 24 13:14:36 lp1918735-f corosync[15358]: [KNET ] handle: Unable to initialize internal hostsockpair: File name too long Mar 24 13:14:36 lp1918735-f corosync[15358]: [MAIN ] Can't initialize TOTEM layer Mar 24 13:14:36 lp1918735-f corosync[15358]: [MAIN ] Corosync Cluster Engine exiting with status 15 at main.c:1531. Mar 24 13:14:36 lp1918735-f systemd[1]: corosync.service: Main process exited, code=exited, status=15/n/a Mar 24 13:14:36 lp1918735-f systemd[1]: corosync.service: Failed with result 'exit-code'. Mar 24 13:14:36 lp1918735-f systemd[1]: Failed to start Corosync Cluster Engine. root@lp1918735-f:~# dpkg -l | grep corosync ii corosync 3.0.3-2ubuntu2.1 amd64 cluster engine daemon and utilities ii libcorosync-common4:amd643.0.3-2ubuntu2.1 amd64 cluster engine common library root@lp1918735-f:~# 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:15:50 UTC; 6s ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 16869 (corosync) Tasks: 9 (limit: 76563) Memory: 84.0M CGroup: /system.slice/corosync.service └─16869 /usr/sbin/corosync -f Mar 24 13:15:50 lp1918735-f corosync[16869]: [QUORUM] Members[0]: Mar 24 13:15:50 lp1918735-f corosync[16869]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5] Mar 24 13:15:50 lp1918735-f corosync[16869]: [QB] server name: votequorum Mar 24 13:15:50 lp1918735-f corosync[16869]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3] Mar 24 13:15:50 lp1918735-f corosync[16869]: [QB] server name: quorum Mar 24 13:15:50 lp1918735-f corosync[16869]: [TOTEM ] A new membership (1.5) was formed. Members joined: 1 Mar 24 13:15:50 lp1918735-f corosync[16869]: [CPG ] downlist left_list: 0 received Mar 24 13:15:50 lp1918735-f corosync[16869]: [QUORUM] Members[1]: 1 Mar 24 13:15:50 lp1918735-f corosync[16869]: [MAIN ] Completed service synchronization, ready to provide service. Mar 24 13:15:50 lp1918735-f systemd[1]: Started Corosync Cluster Engine. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
root@lp1918735-g:~# dpkg -l|grep corosync ii corosync 3.0.3-2ubuntu3amd64 cluster engine daemon and utilities ii libcorosync-common4:amd64 3.0.3-2ubuntu3amd64 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
Hello Dan, or anyone else affected, Accepted corosync into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/corosync/3.0.3-2ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: corosync (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: corosync (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
This bug was fixed in the package corosync - 3.1.0-2ubuntu2 --- corosync (3.1.0-2ubuntu2) hirsute; urgency=medium * d/p/lp1911904-Don-t-lock-all-current-and-future-memory-if-can-t-in.patch: - Don't mlockall() if setrlimit() fails (LP: #1911904) * d/p/lp1918735-try-unprivileged-knet-handle-new.patch: - Retry knet_handle_new without privileged flag (LP: #1918735) * d/t: don't skip tests now that we fixed crashing in container -- Dan Streetman Wed, 10 Mar 2021 12:55:26 -0500 ** Changed in: corosync (Ubuntu Hirsute) Status: In Progress => Fix Released -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
** Changed in: corosync (Debian) Status: Unknown => New -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
** Bug watch added: Debian Bug tracker #985070 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985070 ** Also affects: corosync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985070 Importance: Unknown Status: Unknown -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
** Description changed: [impact] fails to start in container [test case] install corosync in container and check status root@corosync-f:~# 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 Thu 2021-03-11 21:28:52 UTC; 17s ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 14552 (code=exited, status=15) Mar 11 21:28:51 corosync-f corosync[14552]: [TOTEM ] Initializing transport (Kronosnet). Mar 11 21:28:52 corosync-f corosync[14552]: [TOTEM ] knet_handle_new failed: File name too long (36) Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Failed to set socket buffer via force option 33: Operation not permitted Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Unable to set local socketpair receive buffer: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] handle: Unable to initialize internal hostsockpair: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Can't initialize TOTEM layer Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Corosync Cluster Engine exiting with status 15 at main.c:1531. Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Main process exited, code=exited, status=15/n/a Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Failed with result 'exit-code'. Mar 11 21:28:52 corosync-f systemd[1]: Failed to start Corosync Cluster Engine. [regression potential] any regression would likely result in failure to start, or reduced performance of corosync [scope] this is needed in f/g/h corosync starts in a bionic container + + opened upstream PR + https://github.com/corosync/corosync/pull/623 ** Description changed: [impact] fails to start in container [test case] install corosync in container and check status root@corosync-f:~# 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 Thu 2021-03-11 21:28:52 UTC; 17s ago Docs: man:corosync man:corosync.conf man:corosync_overview Main PID: 14552 (code=exited, status=15) Mar 11 21:28:51 corosync-f corosync[14552]: [TOTEM ] Initializing transport (Kronosnet). Mar 11 21:28:52 corosync-f corosync[14552]: [TOTEM ] knet_handle_new failed: File name too long (36) Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Failed to set socket buffer via force option 33: Operation not permitted Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Unable to set local socketpair receive buffer: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] handle: Unable to initialize internal hostsockpair: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Can't initialize TOTEM layer Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Corosync Cluster Engine exiting with status 15 at main.c:1531. Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Main process exited, code=exited, status=15/n/a Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Failed with result 'exit-code'. Mar 11 21:28:52 corosync-f systemd[1]: Failed to start Corosync Cluster Engine. [regression potential] any regression would likely result in failure to start, or reduced performance of corosync [scope] this is needed in f/g/h corosync starts in a bionic container opened upstream PR https://github.com/corosync/corosync/pull/623 + + this is also related to bug 1911904 and bug 1828228 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
** Description changed: [impact] fails to start in container [test case] install corosync in container and check status root@corosync-f:~# 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 Thu 2021-03-11 21:28:52 UTC; 17s ago -Docs: man:corosync - man:corosync.conf - man:corosync_overview -Main PID: 14552 (code=exited, status=15) + Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled) + Active: failed (Result: exit-code) since Thu 2021-03-11 21:28:52 UTC; 17s ago + Docs: man:corosync + man:corosync.conf + man:corosync_overview + Main PID: 14552 (code=exited, status=15) Mar 11 21:28:51 corosync-f corosync[14552]: [TOTEM ] Initializing transport (Kronosnet). Mar 11 21:28:52 corosync-f corosync[14552]: [TOTEM ] knet_handle_new failed: File name too long (36) Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Failed to set socket buffer via force option 33: Operation not permitted Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] transport: Unable to set local socketpair receive buffer: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [KNET ] handle: Unable to initialize internal hostsockpair: File name too long Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Can't initialize TOTEM layer Mar 11 21:28:52 corosync-f corosync[14552]: [MAIN ] Corosync Cluster Engine exiting with status 15 at main.c:1531. Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Main process exited, code=exited, status=15/n/a Mar 11 21:28:52 corosync-f systemd[1]: corosync.service: Failed with result 'exit-code'. Mar 11 21:28:52 corosync-f systemd[1]: Failed to start Corosync Cluster Engine. - [regression potential] - TBD + any regression would likely result in failure to start, or reduced + performance of corosync [scope] this is needed in f/g/h corosync starts in a bionic container -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
> Also FYI this seems to be a bit of a re-surface of bug 1828228 yes, and that was unfortunately 'fixed' by just ignoring the error :( > are you intending to work-on/fix this yep, already fixed bug 1911904 upstream and will include this with sru for that ** Also affects: corosync (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: corosync (Ubuntu Hirsute) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: corosync (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: corosync (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: corosync (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: corosync (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: corosync (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: corosync (Ubuntu Hirsute) Status: New => In Progress ** Changed in: corosync (Ubuntu Focal) Status: New => In Progress ** Changed in: corosync (Ubuntu Groovy) Status: New => In Progress -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918735] Re: fails to start in unprivileged container
I can confirm the issue comparing LXD to VM guest. But given that the errors are about corosync being unable to set some device options - and not having an obvious "container mode" switch I wonder if that will end up needing upstream work. Also FYI this seems to be a bit of a re-surface of bug 1828228 => https://bugs.launchpad.net/auto-package-testing/+bug/1828228/comments/8 @Dan - are you intending to work-on/fix this with your SEG hat on or did you just spot and wanted to report it for us? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
