sysctl: Unable to configure some kernel parameters

[andi456]

Hi,

for some reason sysctl does not want to start:

Code: Select all

 * Configuring kernel parameters ...
sysctl: Schlüssel »net.core.default_qdisc« wird gesetzt: Datei oder Verzeichnis nicht gefunden
 * Unable to configure some kernel parameters                                                     [ !! ]
 * ERROR: sysctl failed to start

I've not configured any file for sysctl and can only tell that cat /proc/sys/net/core/default_qdisc shows the following value:

Code: Select all

pfifo_fast

Where does sysctl search for the corresponding file? Or do I need to load some kernel module in order to make the error go away?

Kind regards,

Andreas

Edit: corrected the path to default_qdisc

[Navar]

Where does sysctl search for the corresponding file? Or do I need to load some kernel module in order to make the error go away?

Roughly translated:

Code: Select all

Key »net.core.default_qdisc« is set: File or directory not found

See man 8 sysctl
Also see /etc/init.d/sysctl script, which parses the respective .conf files, captures any return code failures and generates the output you provided.

[andi456]

Sorry, I forgot to translate the output into english, which you did correctly.

The questions remain: Where does sysctl expect the corresponding file? Or do I need to load some kernel module for that to find it?

[Navar]

Maybe check the output of this:

Code: Select all

# sysctl net.core.default_qdisc
net.core.default_qdisc = pfifo_fast

https://bugs.launchpad.net/ubuntu/+bug/2003027 may also be related, if you're on systemd, as I'm openrc here. This makes a similar mention but is otherwise looking like a dead end, https://github.com/Chikage0o0/Linux-NetSpeed/issues/56

The prior mentions should give you areas to look into the respective .conf files.

[pietinger]

The questions remain: Where does sysctl expect the corresponding file? [...]

"man sysctl" says:

Code: Select all

       /proc/sys
       /etc/sysctl.d/*.conf
       /run/sysctl.d/*.conf
       /usr/local/lib/sysctl.d/*.conf
       /usr/lib/sysctl.d/*.conf
       /lib/sysctl.d/*.conf
       /etc/sysctl.conf

[...] Or do I need to load some kernel module for that to find it?

No

[Perfect Gentleman]

Got the same

Code: Select all

 ~ $ sudo rc-service sysctl restart
 * Configuring kernel parameters ...
sysctl: setting key "net.core.default_qdisc": No such file or directory
 * Unable to configure some kernel parameters                                                                                                        [ !! ]
 * ERROR: sysctl failed to start

Code: Select all

 ~ $ cat /proc/sys/net/core/default_qdisc
fq_pie

[andi456]

Just for the record. I'm on openrc too.

[Navar]

Code: Select all

Symbol: NET_SCHED [=y]
Type  : bool
Defined at net/sched/Kconfig:6
  Prompt: QoS and/or fair queueing
  Depends on: NET [=y]
  Location:
    -> Networking support (NET [=y])
      -> Networking options
(1)     -> QoS and/or fair queueing (NET_SCHED [=y])
Selects: NET_SCH_FIFO [=y]

[pietinger]

I am also on OpenRC (with KDE/Plasma) and dont have this problem ... even with a manually configured kernel WITHOUT CONFIG_NET_SCHED enabled ... because there is no file with this setting.

I had the hope that someone knows which package installs such a file ... if it is unknown we should search in all directories ... e.g. ->

Code: Select all

# grep "" /usr/lib/sysctl.d/*
/usr/lib/sysctl.d/00protected-links.conf:fs.protected_symlinks = 1
/usr/lib/sysctl.d/00protected-links.conf:fs.protected_hardlinks = 1
/usr/lib/sysctl.d/40-ping_group_range.conf:# ping(8) without CAP_NET_ADMIN and CAP_NET_RAW
/usr/lib/sysctl.d/40-ping_group_range.conf:# The upper limit is set to 2^31-1. Values greater than that get rejected by
/usr/lib/sysctl.d/40-ping_group_range.conf:# the kernel because of this definition in linux/include/net/ping.h:
/usr/lib/sysctl.d/40-ping_group_range.conf:#   #define GID_T_MAX (((gid_t)~0U) >> 1)
/usr/lib/sysctl.d/40-ping_group_range.conf:-net.ipv4.ping_group_range = 0 2147483647

(this is mine; a stable system with almost everything as default)

... and if there is no file which helps us to detect the package then please search also in all other sysctl.conf-folders ... it must be come from somewhere ...

[Perfect Gentleman]

Code: Select all

~ $ grep "" /usr/lib/sysctl.d/*
/usr/lib/sysctl.d/00protected-links.conf:fs.protected_symlinks = 1
/usr/lib/sysctl.d/00protected-links.conf:fs.protected_hardlinks = 1
/usr/lib/sysctl.d/40-ping_group_range.conf:# ping(8) without CAP_NET_ADMIN and CAP_NET_RAW
/usr/lib/sysctl.d/40-ping_group_range.conf:# The upper limit is set to 2^31-1. Values greater than that get rejected by
/usr/lib/sysctl.d/40-ping_group_range.conf:# the kernel because of this definition in linux/include/net/ping.h:
/usr/lib/sysctl.d/40-ping_group_range.conf:#   #define GID_T_MAX (((gid_t)~0U) >> 1)
/usr/lib/sysctl.d/40-ping_group_range.conf:-net.ipv4.ping_group_range = 0 2147483647
/usr/lib/sysctl.d/50-default.conf:#  This file is part of systemd.
/usr/lib/sysctl.d/50-default.conf:#
/usr/lib/sysctl.d/50-default.conf:#  systemd is free software; you can redistribute it and/or modify it
/usr/lib/sysctl.d/50-default.conf:#  under the terms of the GNU Lesser General Public License as published by
/usr/lib/sysctl.d/50-default.conf:#  the Free Software Foundation; either version 2.1 of the License, or
/usr/lib/sysctl.d/50-default.conf:#  (at your option) any later version.
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# See sysctl.d(5) and core(5) for documentation.
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# To override settings in this file, create a local file in /etc
/usr/lib/sysctl.d/50-default.conf:# (e.g. /etc/sysctl.d/90-override.conf), and put any assignments
/usr/lib/sysctl.d/50-default.conf:# there.
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# System Request functionality of the kernel (SYNC)
/usr/lib/sysctl.d/50-default.conf:#
/usr/lib/sysctl.d/50-default.conf:# Use kernel.sysrq = 1 to allow all keys.
/usr/lib/sysctl.d/50-default.conf:# See https://docs.kernel.org/admin-guide/sysrq.html for a list
/usr/lib/sysctl.d/50-default.conf:# of values and keys.
/usr/lib/sysctl.d/50-default.conf:kernel.sysrq = 16
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# Append the PID to the core filename
/usr/lib/sysctl.d/50-default.conf:kernel.core_uses_pid = 1
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# Source route verification
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.default.rp_filter = 2
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.*.rp_filter = 2
/usr/lib/sysctl.d/50-default.conf:-net.ipv4.conf.all.rp_filter
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# Do not accept source routing
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.default.accept_source_route = 0
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.*.accept_source_route = 0
/usr/lib/sysctl.d/50-default.conf:-net.ipv4.conf.all.accept_source_route
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# Promote secondary addresses when the primary address is removed
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.default.promote_secondaries = 1
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.*.promote_secondaries = 1
/usr/lib/sysctl.d/50-default.conf:-net.ipv4.conf.all.promote_secondaries
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# ping(8) without CAP_NET_ADMIN and CAP_NET_RAW
/usr/lib/sysctl.d/50-default.conf:# The upper limit is set to 2^31-1. Values greater than that get rejected by
/usr/lib/sysctl.d/50-default.conf:# the kernel because of this definition in linux/include/net/ping.h:
/usr/lib/sysctl.d/50-default.conf:#   #define GID_T_MAX (((gid_t)~0U) >> 1)
/usr/lib/sysctl.d/50-default.conf:# That's not so bad because values between 2^31 and 2^32-1 are reserved on
/usr/lib/sysctl.d/50-default.conf:# systemd-based systems anyway: https://systemd.io/UIDS-GIDS#summary
/usr/lib/sysctl.d/50-default.conf:-net.ipv4.ping_group_range = 0 2147483647
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# Fair Queue CoDel packet scheduler to fight bufferbloat
/usr/lib/sysctl.d/50-default.conf:-net.core.default_qdisc = fq_codel
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# Enable hard and soft link protection
/usr/lib/sysctl.d/50-default.conf:fs.protected_hardlinks = 1
/usr/lib/sysctl.d/50-default.conf:fs.protected_symlinks = 1
/usr/lib/sysctl.d/50-default.conf:
/usr/lib/sysctl.d/50-default.conf:# Enable regular file and FIFO protection
/usr/lib/sysctl.d/50-default.conf:fs.protected_regular = 1
/usr/lib/sysctl.d/50-default.conf:fs.protected_fifos = 1
/usr/lib/sysctl.d/50-pid-max.conf:#  This file is part of systemd.
/usr/lib/sysctl.d/50-pid-max.conf:#
/usr/lib/sysctl.d/50-pid-max.conf:#  systemd is free software; you can redistribute it and/or modify it
/usr/lib/sysctl.d/50-pid-max.conf:#  under the terms of the GNU Lesser General Public License as published by
/usr/lib/sysctl.d/50-pid-max.conf:#  the Free Software Foundation; either version 2.1 of the License, or
/usr/lib/sysctl.d/50-pid-max.conf:#  (at your option) any later version.
/usr/lib/sysctl.d/50-pid-max.conf:
/usr/lib/sysctl.d/50-pid-max.conf:# See sysctl.d(5) and core(5) for documentation.
/usr/lib/sysctl.d/50-pid-max.conf:
/usr/lib/sysctl.d/50-pid-max.conf:# To override settings in this file, create a local file in /etc
/usr/lib/sysctl.d/50-pid-max.conf:# (e.g. /etc/sysctl.d/90-override.conf), and put any assignments
/usr/lib/sysctl.d/50-pid-max.conf:# there.
/usr/lib/sysctl.d/50-pid-max.conf:
/usr/lib/sysctl.d/50-pid-max.conf:# Bump the numeric PID range to make PID collisions less likely.
/usr/lib/sysctl.d/50-pid-max.conf:# 2^22 and 2^15 is possible maximum of 64bit and 32bit kernels respectively.
/usr/lib/sysctl.d/50-pid-max.conf:kernel.pid_max = 4194304
/usr/lib/sysctl.d/README:Files in this directory contain configuration for systemd-sysctl.service, a
/usr/lib/sysctl.d/README:service to configure sysctl kernel parameters.
/usr/lib/sysctl.d/README:
/usr/lib/sysctl.d/README:See man:sysctl.d(5) for explanation of the configuration file format, and
/usr/lib/sysctl.d/README:man:sysctl(8) and man:systemd-sysctl.service(8) for a description of when and
/usr/lib/sysctl.d/README:how this configuration is applied.
/usr/lib/sysctl.d/README:
/usr/lib/sysctl.d/README:Use 'systemd-analyze cat-config sysctl.d' to display the effective config.

Code: Select all

~ $ equery b /usr/lib/sysctl.d/50-default.conf
 * Searching for /usr/lib/sysctl.d/50-default.conf ... 
sys-apps/systemd-utils-259-r2 (/usr/lib/sysctl.d/50-default.conf)

Code: Select all

 ~ $ equery b /usr/lib/sysctl.d/50-pid-max.conf 
 * Searching for /usr/lib/sysctl.d/50-pid-max.conf ... 
sys-apps/systemd-utils-259-r2 (/usr/lib/sysctl.d/50-pid-max.conf)

Code: Select all

 ~ $ sudo rm /usr/lib/sysctl.d/50-*.conf

Code: Select all

 ~ $ sudo rc-service sysctl restart
 * Configuring kernel parameters 

[sam_]

bug 969014 -> https://gitlab.com/procps-ng/procps/-/issues/410

[pietinger]

[...]

Code: Select all

~ $ equery b /usr/lib/sysctl.d/50-default.conf
 * Searching for /usr/lib/sysctl.d/50-default.conf ... 
sys-apps/systemd-utils-259-r2 (/usr/lib/sysctl.d/50-default.conf)

Code: Select all

 ~ $ equery b /usr/lib/sysctl.d/50-pid-max.conf 
 * Searching for /usr/lib/sysctl.d/50-pid-max.conf ... 
sys-apps/systemd-utils-259-r2 (/usr/lib/sysctl.d/50-pid-max.conf)

Perfect Gentleman,

thank you for this information ... so we have an answer:
At the moment we have no problem with stable systemd-utils-255.18 (I have) and there is already an open bug for testing 259-r2 ... and we have two double lines:

Code: Select all

/usr/lib/sysctl.d/00protected-links.conf:fs.protected_symlinks = 1
/usr/lib/sysctl.d/00protected-links.conf:fs.protected_hardlinks = 1
...
/usr/lib/sysctl.d/50-default.conf:fs.protected_hardlinks = 1
/usr/lib/sysctl.d/50-default.conf:fs.protected_symlinks = 1

[andi456]

Ok,

after skimming through various bug reports, I found this one https://bugs.gentoo.org/969014 and installed the latest sys-process/procps-4.0.5-r4. The error message (in german) is even more confusing but at least the sysctl service does start now.

I'm not sure whether I should consider the issue as solved or not.

Kind regards,

Andreas

[sam_]

Ok,

after skimming through various bug reports, I found this one https://bugs.gentoo.org/969014 and installed the latest sys-process/procps-4.0.5-r4. The error message (in german) is even more confusing but at least the sysctl service does start now.

I'm not sure whether I should consider the issue as solved or not.

Kind regards,

Andreas

Didn't I link to it above? If it is still showing an error message, please file a (new) bug, as I don't think it should do that. '-' should mean that any diagnostics are suppressed, at least if it doesn't exist.

[andi456]

Sorry, I first clicked on the second link and then somehow forgot about your first link and got there later on.

After restarting the sysctl service the german message looks like this:

Code: Select all

sysctl: Schlüssel »net.core.default_qdisc«, wird ignoriert wird gesetzt: Datei oder Verzeichnis nicht gefunden

This roughly translates to "Key »net.core.default_qdisc« is being ignored and set: File or directory not found."

The service, as I've already mentioned, starts up though.

[Navar]

Again, you're quick to misinterpret me. My responses were directly tied to all of the OP's Q&A.

I am also on OpenRC (with KDE/Plasma) and dont have this problem ... even with a manually configured kernel WITHOUT CONFIG_NET_SCHED enabled ... because there is no file with this setting.

I had the hope that someone knows which package installs such a file ... if it is unknown we should search in all directories ... e.g. ->

Code: Select all

# grep "" /usr/lib/sysctl.d/*
/usr/lib/sysctl.d/00protected-links.conf:fs.protected_symlinks = 1
/usr/lib/sysctl.d/00protected-links.conf:fs.protected_hardlinks = 1
/usr/lib/sysctl.d/40-ping_group_range.conf:# ping(8) without CAP_NET_ADMIN and CAP_NET_RAW
/usr/lib/sysctl.d/40-ping_group_range.conf:# The upper limit is set to 2^31-1. Values greater than that get rejected by
/usr/lib/sysctl.d/40-ping_group_range.conf:# the kernel because of this definition in linux/include/net/ping.h:
/usr/lib/sysctl.d/40-ping_group_range.conf:#   #define GID_T_MAX (((gid_t)~0U) >> 1)
/usr/lib/sysctl.d/40-ping_group_range.conf:-net.ipv4.ping_group_range = 0 2147483647

First, why would the DE/WM environment, if any, matter here? It is largely irrelevant.

I have the exact same output. I don't think this was a useful endeavor, arguably any more than the more exhaustive one I did below before posting the kernel menu mention, which is exactly why I posted it. OP is using openrc like us, not the larger response with someone running systemd which went in some other direction. OP had already directly/indirectly by us (again, why?) both been given mention for locations to try to grep in fishing for a needle in the haystack, file wise.

Follow-ups mentioned bugs referencing net_sch_* missing selection associations. The fifo one aforementioned that OP showed as the default set should have been the one I mentioned in the kernel settings that selects that. I have that and only that:

Code: Select all

amd300 /usr/src/linux # grep -i "_net.sch.*[ym]$" .config
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_FIFO=y
amd300 /usr/src/linux # grep -iR 'net\.core' /proc/sys /etc/sysctl.d/ /run/sysctl.d/ /usr/local/lib/sysctl.d/ /usr/lib/sysctl.d/ /lib/sysctl.d/ /etc/ 2>/dev/null
amd300 /usr/src/linux # 
amd300 /usr/src/linux # grep -iR 'pfifo' /proc/sys /etc/sysctl.d/ /run/sysctl.d/ /usr/local/lib/sysctl.d/ /usr/lib/sysctl.d/ /lib/sysctl.d/ /etc/ 2>/dev/null
/proc/sys/net/core/default_qdisc:pfifo_fast
amd300 /usr/src/linux #

It takes a few seconds to toggle that kernel config entry or to at least check what you have set under same, rebuild if needed and test.

Instead, we're assuming an open syscall failure because of the error message. Which is fine, if it's on your end to debug, which neither you nor I have the OP's failure to test; nor am I seeing any related reference to same in the expected aforementioned locations. The only .*net.*fifo.* entry I have in my .config settings is via the above, which the kernel setup explains why it got selected. The bug reports refer to 1 other maybe related net_sch_ as well in trying to make a determination or establish a pattern behind troubleshooting the issue(s). Occam's Razor. Sysctl is about affecting kernel settings at runtime, which can mean issues are as much about kernel configuration issues than any .conf file concerns.

The output shown here and Q&A responses from the OP are exactly why I responded as I did to aid in troubleshooting.

[AdrianEllison]

I just ran into this issue too, NET_SCH_FQ_CODEL wasn't enabled :-

Code: Select all

│ Symbol: NET_SCH_FQ_CODEL [=y]
  │ Type  : tristate  
  │ Defined at net/sched/Kconfig:277
  │   Prompt: Fair Queue Controlled Delay AQM (FQ_CODEL)
  │   Depends on: NET [=y] && NET_SCHED [=y]  
  │   Location:
  │     -> Networking support (NET [=y])
  │       -> Networking options
  │         -> QoS and/or fair queueing (NET_SCHED [=y])
  │ (2)       -> Fair Queue Controlled Delay AQM (FQ_CODEL) (NET_SCH_FQ_CODEL [=y])

│

[bruda]

I just ran into this issue too, NET_SCH_FQ_CODEL wasn't enabled :-

Code: Select all

│ Symbol: NET_SCH_FQ_CODEL [=y]
  │ Type  : tristate  
  │ Defined at net/sched/Kconfig:277
  │   Prompt: Fair Queue Controlled Delay AQM (FQ_CODEL)
  │   Depends on: NET [=y] && NET_SCHED [=y]  
  │   Location:
  │     -> Networking support (NET [=y])
  │       -> Networking options
  │         -> QoS and/or fair queueing (NET_SCHED [=y])
  │ (2)       -> Fair Queue Controlled Delay AQM (FQ_CODEL) (NET_SCH_FQ_CODEL [=y])

│

That is right on the money and is caused by sys-apps/systemd-utils-259.3 rather than any kernel configuration. The queue discipline is set in /usr/lib/sysctl.d/50-default.conf (which belongs to sys-apps/systemd-utils) to CODEL. Earlier versions of sys-apps/systemd-utils do not set any queue discipline.

[sam_]

It's related to kernel configuration because it won't show up with certain configuration. Anyway, filed [bug=971227]bug 971227[/bug] now after someone reminded us earlier.

[pietinger]

I just ran into this issue too, NET_SCH_FQ_CODEL wasn't enabled

This means you have an old procps package ->
https://gitlab.com/FireBurn/gentoo/-/co ... d4d7dc40e8
(If you update your system to the newest sys-process/procps you should not get any error even without this kernel option NET_SCH_FQ_CODEL)

[AdrianEllison]

(If you update your system to the newest sys-process/procps you should not get any error even without this kernel option NET_SCH_FQ_CODEL)

sys-process/procps-4.0.5-r3 is the current stable version and that's what's installed here.

[pietinger]

sys-process/procps-4.0.5-r3 is the current stable version and that's what's installed here.

Yes, I am also on both latest stable versions:

Code: Select all

# emerge -pv systemd-utils procps

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 2.16 s (backtrack: 0/20).

[ebuild   R    ] sys-process/procps-4.0.5-r3:0/1-ng::gentoo  USE="elogind kill ncurses nls (unicode) -modern-top (-selinux) -skill -static-libs -systemd -test" 1.483 KiB
[ebuild   R    ] sys-apps/systemd-utils-259.3::gentoo  USE="acl kmod tmpfiles udev -boot -kernel-install -secureboot (-selinux) (-split-usr) -sysusers -test -ukify" PYTHON_SINGLE_TARGET="python3_13 -python3_11 -python3_12 -python3_14" 0 KiB

Total: 2 packages (2 reinstalls), Size of downloads: 1.483 KiB

but I have disabled QoS completely in my kernel configuration:

Code: Select all

# CONFIG_NET_SCHED is not set

... and so I have not the problem ... even with the latest systemd-utils.

[sam_]

4.0.5-r4 is the first fixed version and as I said, I filed a stablereq for it earlier and it's stable now.