![Ubuntu 报告触发器重新启动并以崩溃结束](https://linux22.com/image/936050/Ubuntu%20%E6%8A%A5%E5%91%8A%E8%A7%A6%E5%8F%91%E5%99%A8%E9%87%8D%E6%96%B0%E5%90%AF%E5%8A%A8%E5%B9%B6%E4%BB%A5%E5%B4%A9%E6%BA%83%E7%BB%93%E6%9D%9F.png)
我有一台机器,它整夜不停地运行加密挖矿软件 gpu。有时它会多次触发 ubuntu 报告,直到崩溃。它首先创建 root 用户切片,然后开始触发报告:
Mar 24 01:27:35 r9 systemd[1]: Created slice User Slice of root.
Mar 24 01:27:35 r9 systemd[1]: Starting User Manager for UID 0...
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 01:27:36 r9 systemd[13968]: Starting D-Bus User Message Bus Socket.
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG network certificate management daemon.
Mar 24 01:27:36 r9 systemd[13968]: Started Pending report trigger for Ubuntu Report.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Paths.
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 01:27:36 r9 systemd[13968]: Listening on REST API socket for snapd user session agent.
Mar 24 01:27:36 r9 systemd[13968]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Timers.
Mar 24 01:27:36 r9 systemd[13968]: Listening on D-Bus User Message Bus Socket.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Sockets.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Basic System.
Mar 24 01:27:36 r9 systemd[1]: Started User Manager for UID 0.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Default.
Mar 24 01:27:36 r9 systemd[13968]: Startup finished in 35ms.
然后它关闭它:
Mar 24 01:27:36 r9 systemd[1]: Stopping User Manager for UID 0...
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Default.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Basic System.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Timers.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Paths.
Mar 24 01:27:36 r9 systemd[13968]: Stopped Pending report trigger for Ubuntu Report.
Mar 24 01:27:36 r9 systemd[13968]: Stopped target Sockets.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 24 01:27:36 r9 systemd[13968]: Closed D-Bus User Message Bus Socket.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG network certificate management daemon.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 24 01:27:36 r9 systemd[13968]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 24 01:27:36 r9 systemd[13968]: Closed REST API socket for snapd user session agent.
Mar 24 01:27:36 r9 systemd[13968]: Reached target Shutdown.
Mar 24 01:27:36 r9 systemd[13968]: Starting Exit the Session...
Mar 24 01:27:36 r9 systemd[13968]: Received SIGRTMIN+24 from PID 13986 (kill).
Mar 24 01:27:36 r9 systemd[1]: Stopped User Manager for UID 0.
Mar 24 01:27:36 r9 systemd[1]: Removed slice User Slice of root.
它会不断重复,直到系统因内存问题崩溃:
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message"
有人能告诉我“ubuntu 报告的报告触发器”是什么吗?为什么它会反复启动和停止?
我正在使用 ubuntu 18.04 和内核 5.4.0-54-generic。
问候
答案1
Ubuntu 报告 (https://github.com/ubuntu/ubuntu-report) 是一项服务,它:
此工具将收集并报告当前硬件、分区和会话信息的指标。此信息不能用于识别单台机器,并且在发送到服务器之前显示。
每次启动时都会运行。您的输出似乎显示正常行为。
您的输出似乎没有显示它“反复启动和停止“在一次启动周期内。如果确实如此,那将是一个错误。
请注意,此工具100% 开源。您可以审核代码以查看其功能。您可以轻松查看发送的报告(尝试一下:ubuntu-report show
或查看man ubuntu-report
。这里没有秘密,也没有个人信息。
答案2
崩溃是由于将数据刷新到磁盘花费的时间太长并导致“echo 0 > /proc/sys/kernel/hung_task_timeout_secs”错误造成的。ubuntu 报告与此无关
通过设置以下变量来修复它
vm.dirty_background_ratio vm.dirty_ratio