What does this "FAILED" message mean?

While booting up I can see this failed kernel message? Anyone know why or how to fix? Is this normal? I didn’t have it before. (Seems to have appeared last few days…My laptop seems to operate ok. I just get blank screen sometimes while gaming, not sure if it’s related? )

I doubt that the message is related to this. What does this show

systemctl --failed
1 Like

[xxx~]$ systemctl --failed
● systemd-sysctl.service loaded failed failed Apply Kernel Variables
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

There must be some variable loading that fails.

journalctl -b -0 | eos-sendlog
1 Like

systemctl status systemd-sysctl.service

might reveal some more details.

1 Like

Thanks @pebcak
Mine is working correctly. It might just show failed?

[ricklinux@kde-plasma ~]$ systemctl status systemd-sysctl.service

● systemd-sysctl.service - Apply Kernel Variables
     Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
     Active: active (exited) since Mon 2022-10-31 10:01:37 EDT; 14min ago
       Docs: man:systemd-sysctl.service(8)
    Process: 414 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
   Main PID: 414 (code=exited, status=0/SUCCESS)
        CPU: 3ms

Oct 31 10:01:37 kde-plasma systemd[1]: Starting Apply Kernel Variables...
Oct 31 10:01:37 kde-plasma systemd[1]: Finished Apply Kernel Variables.
[ricklinux@kde-plasma ~]$ 

Nov 01 00:03:59 xxx systemd-sysctl[407]: /etc/sysctl.d/vfs-cache-pressure.conf:1: Line is not an assignment, ignoring: 50
Nov 01 00:03:59 xxx systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
Nov 01 00:03:59 xxx systemd[1]: systemd-sysctl.service: Failed with result ‘exit-code’.
Nov 01 00:03:59 xxx systemd[1]: Failed to start Apply Kernel Variables.

Please use code tags around what you post.

1 Like

Look into this

/etc/sysctl.d/vfs-cache-pressure.conf:1: Line is not an assignment, ignoring: 50

1 Like

I don’t even have that file. What does it show?

cat /etc/sysctl.d/vfs-cache-pressure.conf
1 Like

It looks like an outdated file used on Garuda.

1 Like

That is a variable which

controls the tendency of the kernel to reclaim the memory which is used for caching of directory and inode objects.

It can be user-modified by creating that file.

1 Like

can i delete that file /etc/sysctl.d/vfs-cache-pressure.conf or how to set back to default again? I kept getting blank screen midway playing games and read elsewhere reducing vfs pressure cache might help, but seems I made error trying to reduce vfs cache pressure to 50? How to revert to default variable?

I don’t have that problem nor should most. Unless you have ancient low power hardware. :laughing:

1 Like

Yes, you could remove that file.
Then the default vale 100 will be used.


By the way, what says:

cat /etc/sysctl.d/vfs-cache-pressure.conf


Perhaps incorrectly configured?


will try delete and reboot.

That will work as you don’t need it.

1 Like

Ya I dont understand why I keep getting blank screen while gaming…
My machine MSI Modern14 AMD Ryzen 7 5700U with Radeon Graphics, 16Gb RAM, 512 Nvme storage .

It could be that you are missing some package or its a game platform issue? Do you have the proper lib 32 files installed also? Some of these game platforms require them. What game are you playing and on what? Steam? Lutris? etc

Edit: I would look to the specific game and platform you are playing for answers.

1 Like

Steam…playing “Stray” game