我在其中一台服务器的系统日志中不断收到以下错误消息:
# tail /var/log/syslog
Oct 29 13:48:40 myserver dbus[19617]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Oct 29 13:48:40 myserver dbus[19617]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Oct 29 13:49:05 myserver dbus[19617]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Oct 29 13:49:05 myserver dbus[19617]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Run Code Online (Sandbox Code Playgroud)
它们似乎与 ProFTPd 守护程序上的 FTP 登录相关:
# tail /var/log/proftpd/proftpd.log
2015-10-29 13:48:40,433 myserver proftpd[17872] myserver.example.com (remote.example.com[192.168.22.33]): USER switch: Login successful.
2015-10-29 13:48:40,460 myserver proftpd[17872] myserver.example.com (remote.example.com[192.168.22.33]): FTP session …Run Code Online (Sandbox Code Playgroud) 我最近升级到 Debian 9 的某些服务器现在每天都会产生一条奇怪的 syslog 消息(通过 logcheck 报告):
Oct 27 06:25:08 foo systemd[1]: user@65534.service: Killing process 12270 (kill) with signal SIGKILL.
Run Code Online (Sandbox Code Playgroud)
时间似乎是 cron.daily 的时间,服务的名称看起来像 nobody/nogroup 的 UID,但是为什么它会死掉,它首先在做什么?
那个时候有更多的系统日志行。该块重复了几次:
Oct 27 06:25:08 svn systemd[1]: Created slice User Slice of nobody.
Oct 27 06:25:08 svn systemd[1]: Starting User Manager for UID 65534...
Oct 27 06:25:08 svn systemd[1]: Started Session 1377 of user nobody.
Oct 27 06:25:08 svn systemd[12264]: Reached target Paths.
Oct 27 06:25:08 svn systemd[12264]: Listening on GnuPG cryptographic agent (access …Run Code Online (Sandbox Code Playgroud) 我实际上喜欢可预测的接口名称,我只想在 Debian dist-upgrade 后重新启动之前知道它们,以便我可以相应地更改它们/etc/network/interfaces。知道如何预测它们吗?