☰

升级到 Fedora 22 后出现大量 systemd 消息

tag-icon • tag-icon fedora logs systemd
升级到 Fedora 22 后出现大量 systemd 消息

我将多个系统升级到 Fedora 22。升级后，我每隔 10-20 秒就会看到大量消息systemd：

Aug 27 15:30:09 host.example.org systemd[1]: Created slice user-494.slice. 
Aug 27 15:30:09 host.example.org systemd[1]: Starting user-494.slice. 
Aug 27 15:30:09 host.example.org systemd[1]: Starting User Manager for UID 494... 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Default. 
Aug 27 15:30:09 host.example.org systemd[29383]: Startup finished in 8ms. 
Aug 27 15:30:09 host.example.org systemd[1]: Started User Manager for UID 494. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Default. 
Aug 27 15:30:09 host.example.org audit[1]: <audit-1130> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@494 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 
Aug 27 15:30:09 host.example.org systemd-logind[636]: Removed session 1016. 
Aug 27 15:30:09 host.example.org systemd[1]: Stopping User Manager for UID 494... 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Default. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Default. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Basic System. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Sockets. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Timers. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopped target Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Stopping Paths. 
Aug 27 15:30:09 host.example.org systemd[29383]: Reached target Shutdown. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Shutdown. 
Aug 27 15:30:09 host.example.org systemd[29383]: Starting Exit the Session... 
Aug 27 15:30:09 host.example.org systemd[29383]: Received SIGRTMIN+24 from PID 29392 (kill). 
Aug 27 15:30:09 host.example.org systemd[1]: Stopped User Manager for UID 494. 
Aug 27 15:30:09 host.example.org audit[1]: <audit-1131> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@494 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 
Aug 27 15:30:09 host.example.org systemd[1]: Removed slice user-494.slice. 
Aug 27 15:30:09 host.example.org systemd[1]: Stopping user-494.slice.

知道它们可能是什么吗？

答案1

就我而言，在 Debian 8 上，我设法通过设置关闭这些过多的消息systemd：

在/etc/systemd/user.conf: LogLevel=notice

在/etc/systemd/system.conf: LogLevel=notice

然后/etc/systemd/journald.conf: MaxLevelSyslog=notice应用更改：systemctl restart systemd-journald- 请小心这一点，因为不会记录任何调试消息（例如：邮件日志将大部分为空），许多日志分析器将不再工作。

了解更多信息，man systemd

相关内容