You are not logged in.

#1 2017-10-10 13:24:54

Hasbeen
Member
Registered: 2017-10-10
Posts: 3

Unknown option "nsdelegate" ~ Systemd update problem [SOLVED]

After upgrading the following packages on my system:

[2017-10-10 14:13] [PACMAN] starting full system upgrade
[2017-10-10 14:13] [ALPM] transaction started
[2017-10-10 14:13] [ALPM] upgraded bubblewrap (0.1.8-1 -> 0.2.0-1)
[2017-10-10 14:13] [ALPM] upgraded p11-kit (0.23.8-1 -> 0.23.9-1)
[2017-10-10 14:13] [ALPM] upgraded ca-certificates-mozilla (3.33-1 -> 3.33-2)
[2017-10-10 14:13] [ALPM] upgraded libsystemd (234.11-9 -> 235.0-1)
[2017-10-10 14:13] [ALPM] upgraded device-mapper (2.02.174-2 -> 2.02.175-1)
[2017-10-10 14:13] [ALPM] upgraded nss (3.33-1 -> 3.33-2)
[2017-10-10 14:13] [ALPM] upgraded pambase (20130928-1 -> 20171006-1)
[2017-10-10 14:13] [ALPM] warning: /etc/systemd/journald.conf installed as /etc/systemd/journald.conf.pacnew
[2017-10-10 14:13] [ALPM] upgraded systemd (234.11-9 -> 235.0-1)
[2017-10-10 14:14] [ALPM] upgraded firefox (56.0-1 -> 56.0.1-1)
[2017-10-10 14:14] [ALPM] upgraded thin-provisioning-tools (0.7.2-1 -> 0.7.3-2)
[2017-10-10 14:14] [ALPM] upgraded lvm2 (2.02.174-2 -> 2.02.175-1)
[2017-10-10 14:14] [ALPM] upgraded krita (3.3.0-1 -> 3.3.1-1)
[2017-10-10 14:14] [ALPM] upgraded systemd-sysvcompat (234.11-9 -> 235.0-1)
[2017-10-10 14:14] [ALPM] transaction completed
[2017-10-10 14:14] [ALPM] running '90-linux-lts.hook'...
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Starting build: 4.9.54-1-lts
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Image generation successful
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S       autodetect
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Starting build: 4.9.54-1-lts
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2017-10-10 14:14] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2017-10-10 14:14] [ALPM-SCRIPTLET] ==> Image generation successful
[2017-10-10 14:14] [ALPM] running 'gtk-update-icon-cache.hook'...
[2017-10-10 14:14] [ALPM] running 'systemd-hwdb.hook'...
[2017-10-10 14:14] [ALPM] running 'systemd-sysusers.hook'...
[2017-10-10 14:14] [ALPM] running 'systemd-tmpfiles.hook'...
[2017-10-10 14:14] [ALPM] running 'systemd-update.hook'...
[2017-10-10 14:14] [ALPM] running 'update-ca-trust.hook'...
[2017-10-10 14:14] [ALPM] running 'update-desktop-database.hook'...

I get that error in journalctl output:

Oct 10 14:26:28 archintel kernel: cgroup: cgroup2: unknown option "nsdelegate"

and that one in dmesg output:

[   19.665648] systemd[1]: systemd 235 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN default-hierarchy=hybrid)
[   19.665821] systemd[1]: Detected architecture x86-64.
[   19.665966] systemd[1]: Set hostname to <archintel>.
[   19.777358] systemd[1]: File /usr/lib/systemd/system/systemd-journald.service:33 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[   19.777361] systemd[1]: Proceeding WITHOUT firewalling in effect!
[   19.780613] systemd[1]: File /usr/lib/systemd/system/systemd-udevd.service:32 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[   19.780616] systemd[1]: Proceeding WITHOUT firewalling in effect!
[   19.812956] systemd[1]: File /usr/lib/systemd/system/systemd-logind.service:34 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[   19.812959] systemd[1]: Proceeding WITHOUT firewalling in effect!
[   19.815835] systemd[1]: Reached target Login Prompts.
[   19.830680] EXT4-fs (dm-2): re-mounted. Opts: data=ordered
[   19.876062] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   19.877703] systemd-journald[310]: Received request to flush runtime journal from PID 1
[   19.887890] ip6_tables: (C) 2000-2006 Netfilter Core Team

I can guarantee that anything else in the dmesg output is same as before as I have an obsession of checking dmesg output daily. c:

The contents of the journald.conf file:

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See journald.conf(5) for details.

[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=1000
SystemMaxUse=200M
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K

The old journald.conf file has been overwritten by the new .pacnew file; the only difference between them was "SystemMaxUse" uncommented.

What should I do about it? Is that a serious issue to take care of?

Edit: I use the latest LTS kernel release.

2#Edit: I realized that I had upgraded the kernel yesterday, though I always do reboot after updating critical packages on my system so I believe the error wasn't caused by the kernel update. I'm not sure though.

[2017-10-09 19:22] [ALPM] upgraded linux-lts (4.9.53-1 -> 4.9.54-1)
[2017-10-09 19:22] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2017-10-09 19:23] [ALPM] upgraded linux-lts-headers (4.9.53-1 -> 4.9.54-1)

3#Edit: That could be related to the issue: https://github.com/systemd/systemd/pull/6294

A new mount option, "nsdelegate", was added to cgroup v2 to address this issue. The flag is meangingful only when mounting cgroup v2 in the init namespace and makes a cgroup namespace a delegation boundary. The kernel feature is pending for v4.13.

looks good, but let's wait for the v235 cycle for this

Last edited by Hasbeen (2017-10-10 17:56:18)

Offline

#2 2017-10-10 14:48:29

kmacleod
Member
Registered: 2009-03-27
Posts: 12

Re: Unknown option "nsdelegate" ~ Systemd update problem [SOLVED]

I have the same journal entry:

kernel: cgroup: cgroup2: unknown option "nsdelegate"

However, I am still on kernel 4.12 (I can't update to 4.13 because of a wifi issue).

I assume from reading the linked systemd issue (from your #3 edit) that we'll see this log entry whenever using systemd 235 while kernel < 4.13.  If you're on LTS you're not on 4.13.

I'm going to ignore it because it looks like it falls back if not supported:

this commit makes systemd try "nsdelegate" first when trying to mount cgroup v2 and fall back if the option is not supported

Offline

#3 2017-10-10 17:53:54

Hasbeen
Member
Registered: 2017-10-10
Posts: 3

Re: Unknown option "nsdelegate" ~ Systemd update problem [SOLVED]

kmacleod wrote:

I have the same journal entry:

kernel: cgroup: cgroup2: unknown option "nsdelegate"

However, I am still on kernel 4.12 (I can't update to 4.13 because of a wifi issue).

I assume from reading the linked systemd issue (from your #3 edit) that we'll see this log entry whenever using systemd 235 while kernel < 4.13.  If you're on LTS you're not on 4.13.

Thanks for sharing! By the way, I did a little more research on my own, and it turns out that the Systemd warnings in the dmesg output as seen in my first post concern another features that were brought to Systemd 235 that aren't supported by the LTS kernel yet.

http://0pointer.net/blog/ip-accounting- … stemd.html

The three options are thin wrappers around kernel functionality introduced with Linux 4.11: the control group eBPF hooks.

It looks like it's all going to be gone once LTS 4.14 kernel is released.
In that case, I'm going to mark the topic as solved as there's nothing to complain about further.

Last edited by Hasbeen (2017-10-10 18:04:20)

Offline

Board footer

Powered by FluxBB