当我调查以常规方式重新启动的服务器时,我开始查看“最后一个”实用程序,但问题是我无法找到这些列的确切含义。当然,我已经查看了那个人,但它不包含此信息。
root@webservice1:/etc# last reboot
reboot system boot 3.2.13-grsec-xxx Thu Apr 12 09:44 - 09:58 (00:13)
reboot system boot 3.2.13-grsec-xxx Thu Apr 12 09:34 - 09:43 (00:08)
reboot system boot 3.2.13-grsec-xxx Thu Apr 12 09:19 - 09:33 (00:13)
reboot system boot 3.2.13-grsec-xxx Thu Apr 12 08:51 - 09:17 (00:25)
reboot system boot 3.2.13-grsec-xxx Thu Apr 12 00:11 - 09:17 (09:05)
reboot system boot 3.2.13-grsec-xxx Wed Apr 11 19:40 - 09:17 (13:36)
reboot system boot 3.2.13-grsec-xxx Sun Apr 8 22:06 - 09:17 …
Run Code Online (Sandbox Code Playgroud) 我在 CentOS 7 上有一个新安装的版本,我已经从 EPEL 存储库安装了 syslog-ng。
~: yum list | grep syslog
syslog-ng.x86_64 3.5.6-1.el7 @epel
Run Code Online (Sandbox Code Playgroud)
当我尝试通过 systemctl 启动它时,它失败如下:
/usr/lib/systemd/system: systemctl start syslog-ng
Job for syslog-ng.service failed. See 'systemctl status syslog-ng.service' and 'journalctl -xn' for details.
Run Code Online (Sandbox Code Playgroud)
查看日志时,我们可以看到它们依赖于“开始”正常的套接字,但该过程返回有关参数不正确的错误,如下所示:
May 07 17:26:15 superserver.company.corp systemd[1]: Starting Syslog Socket.
May 07 17:26:15 superserver.company.corp systemd[1]: Listening on Syslog Socket.
May 07 17:26:15 superserver.company.corp systemd[1]: Starting System Logger Daemon...
May 07 17:26:15 superserver.company.corp systemd[1]: syslog-ng.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 07 17:26:15 superserver.company.corp systemd[1]: Failed …
Run Code Online (Sandbox Code Playgroud)