本文介绍了一次Raspberry Pi中systemd-journal进程导致CPU占用过高的故障排查经历。通过使用top命令发现systemd-journal为CPU占用最高的进程，并通过journalctl命令查看到了错误日志，显示为“Bad file descriptor”。最终通过重启解决了问题。
Raspberry Pi CPU and Trouble Shooting
When I do top on my raspberry Pi, I saw something wrong there.
14651 root 20 0 9948 6960 6740 R 99.8 0.7 7:18.46 systemd-journal
The system-journal is always the top and taking a lot of CPU.
> sudo journalctl
[sudo] password for carl:
-- Logs begin at Wed 2016-08-31 13:24:14 CDT, end at Wed 2016-08-31 13:52:34 CDT. --
Aug 31 13:24:14 raspberrypi1 dhcpcd[597]: vethacac5b2: dhcp if_readrawpacket: Bad file descriptor
Aug 31 13:24:14 raspberrypi1 dhcpcd[597]: vethacac5b2: dhcp if_readrawpacket: Bad file descriptor
It shows that dhcp if_readrawpacket: Bad file descriptor
Reboot the system. It is good now.
References:
https://bbs.archlinux.org/viewtopic.php?id=148823
When I do top on my raspberry Pi, I saw something wrong there.
14651 root 20 0 9948 6960 6740 R 99.8 0.7 7:18.46 systemd-journal
The system-journal is always the top and taking a lot of CPU.
> sudo journalctl
[sudo] password for carl:
-- Logs begin at Wed 2016-08-31 13:24:14 CDT, end at Wed 2016-08-31 13:52:34 CDT. --
Aug 31 13:24:14 raspberrypi1 dhcpcd[597]: vethacac5b2: dhcp if_readrawpacket: Bad file descriptor
Aug 31 13:24:14 raspberrypi1 dhcpcd[597]: vethacac5b2: dhcp if_readrawpacket: Bad file descriptor
It shows that dhcp if_readrawpacket: Bad file descriptor
Reboot the system. It is good now.
References:
https://bbs.archlinux.org/viewtopic.php?id=148823
扫一扫
2万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
