如何在 debian 11 中停止“rsyslogd”和“systemd-journal”高 CPU 使用率?

如何在 debian 11 中停止“rsyslogd”和“systemd-journal”高 CPU 使用率?

我正在运行 Debian 11 mini,我观察到rsyslogd & systemd-journalcpu 使用率达到 100%,原因是什么?如何停止?

 1599 root      20   0   54128  24832   2396 S 109.2   5.3   1:06.98 rsyslogd                                                             
  935 root      20   0   29108   5872   5200 R  42.9   1.3   0:26.99 systemd-journal

任何帮助将非常感激!

答案1

感谢@Artem S. Tashkinov,我尝试了该命令journalctf -f,并观察到以下日志

[  107.041208] export_store: status -16
[  108.441202] export_store: status -16
[  108.741202] export_store: status -16
[  110.314120] gpio-1023 (sysfs): gpiod_request: status -16
[  110.412046] gpio-1023 (sysfs): gpiod_request: status -16
[  110.412052] export_store: status -16
[  112.694120] export_store: status -16
[  125.412004] gpio-1023 (sysfs): gpiod_request: status -16
[  125.412011] export_store: status -16
[  125.934120] gpio-1023 (sysfs): gpiod_request: status -16
[  126.441204] export_store: status -16
[  133.141201] gpio-1023 (sysfs): gpiod_request: status -16
[  133.141208] export_store: status -16
[  133.241204] gpio-1023 (sysfs): gpiod_request: status -16
[  133.412015] gpio-1023 (sysfs): gpiod_request: status -16
[  133.412022] export_store: status -16
[  138.704120] export_store: status -16
[  139.341207] gpio-1023 (sysfs): gpiod_request: status -16
[  139.741203] gpio-1023 (sysfs): gpiod_request: status -16
[  144.412047] gpio-1023 (sysfs): gpiod_request: status -16
[  144.412054] export_store: status -16
[  145.341205] gpio-1023 (sysfs): gpiod_request: status -16
[  146.412061] gpio-1023 (sysfs): gpiod_request: status -16
[  146.412068] export_store: status -16
[  148.154120] export_store: status -16
[  148.412030] gpio-1023 (sysfs): gpiod_request: status -16
[  148.412037] export_store: status -16
[  150.534120] gpio-1023 (sysfs): gpiod_request: status -16
[  152.412049] gpio-1023 (sysfs): gpiod_request: status -16
[  152.412055] export_store: status -16
[  152.464120] gpio-1023 (sysfs): gpiod_request: status -16

在这里我了解到问题出在 GPIO 1023 上。

所以现在我已经禁用了,现在好了。

相关内容