3

when we run the sysctl -p on our rhel 7.2 server1 we get

sysctl -p
fs.file-max = 500000
vm.swappiness = 10
vm.vfs_cache_pressure = 50
sysctl: cannot stat /proc/sys/pcie_aspm: No such file or directory
net.core.somaxconn = 1024

# ls /proc/sys/pcie_aspm
ls: cannot access /proc/sys/pcie_aspm: No such file or directory

but when we run the sysctl -p on other server2 as

we get good results without error as

sysctl -p
fs.file-max = 500000
vm.swappiness = 10
vm.vfs_cache_pressure = 50
net.core.somaxconn = 1024

the file - /proc/sys/pcie_aspm not exist on this server also ( server2 )

so why sysctl -p failed on server1?

yael
  • 12,598
  • 51
  • 169
  • 303

2 Answers2

6

As revealed in the comments, there’s a

pcie_aspm=off

line in one of the files which sysctl -p reads. This causes sysctl to attempt to write to /proc/sys/pcie_aspm; if that doesn’t exist (and it won’t, it’s not a valid sysctl entry, it’s a kernel boot parameter), you’ll get the error shown in your question.

Stephen Kitt
  • 411,918
  • 54
  • 1,065
  • 1,164
2

The parameter may be not supported by the kernel due to the inexistence of PciExpress subsytem.

Or it can be also the pcie_aspm is disabled.

Reda Salih
  • 1,724
  • 4
  • 9