Question Lockdown: filwrpr: /dev/mem,kmem,port is restricted

[hbongers]

Lately I've been seeing a lot of log messages (hundreds daily) like this one:
Nov 8 10:18:14 plesk kernel: Lockdown: filwrpr: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7

This is the only Plesk server with these messages.
I've installed a fully new one for testing but it doesn't show these messages either.

This is an Almalinux 9.2 machine on vmware.
SecureBoot is enabled as is SELinux.

Can anyone give me a clue where to look?

 

[Peter Debik]

This issue is not linked to Plesk. I have moved it to "Open Topics".
Please see kernel_lockdown(7) - Linux manual page on the "Kernel Lockdown" situation.
I suggest asking the question on unix.stackexchange.com, as you are more likely to get appropriate assistance there.
Edit: Wrong information here.

 

[Peter Debik]

@hbongers I must apologize. I did not pay attention to the detail, in this case the filename "filwrpr". A Plesk tech expert pointed this out and told me that this is a Plesk file, so the issue is Plesk-related. What we don't know though is what is happening. It could still be an issue with the operating system, specifically the virtualization environment.

Would you please send me - in a private message - details:
- Your operating system and version
- The VMWare type and version
- Your Plesk license number PLSK. ... ... ...
We can then check how to proceed with this case.

 

[Jan Schumacher]

"Lockdown: X: Y is restricted, see man kernel_lockdown.7" messages in the kernel log - Red Hat Customer Portal

Below kernel messages logged in /var/log/messages & dmesg Lockdown: rhsmcertd-worke: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Lockdown: sosreport: debugfs access is restricted; see man...

access.redhat.com

disable secure boot is the solution here.