Самопроизвольный Logout при стресс тесте системы через утилиту STRESS_NG

[Лексимус]

Добрый день!

На только установленном Debian 9 запускаю утилиту STRESS_NG на тестирование памяти. Утилита гоняет ядра процессора и память. Но через какое то время просто происходит Logout!
И система просто предлагает авторизироваться, но при авторизации всё закрыто.
В настройках ничего нет что может к этому привести. Время Logout по разному.
Думал что не исправность оборудования, но на втором идентичном сервере одно и то же.
Сервер HP DL360 G7

Вот выжимка примерно того где это происходит:

Код Выделить Развернуть


Apr 16 20:52:12 server systemd[1]: systemd-journald.service: Main process exited, code=killed, status=9/KILL
Apr 16 20:52:12 server liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="13080" x-info="http://www.rsyslog.com"] start
Apr 16 20:52:12 server systemd[1]: systemd-journald.service: Unit entered failed state.
Apr 16 20:52:12 server systemd[1]: Starting Flush Journal to Persistent Storage...
Apr 16 20:52:12 server systemd[1]: Started Flush Journal to Persistent Storage.
Apr 16 20:52:21 server systemd[1]: dbus.service: Main process exited, code=killed, status=9/KILL
Apr 16 20:52:21 server systemd[1]: dbus.service: Unit entered failed state.
Apr 16 20:52:21 server systemd[1]: dbus.service: Failed with result 'signal'.
Apr 16 20:52:21 server systemd[1]: Started D-Bus System Message Bus.
Apr 16 20:52:21 server systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.login1': Device or resource busy
Apr 16 20:52:21 server systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL
Apr 16 20:52:21 server systemd[1]: systemd-udevd.service: Unit entered failed state.
Apr 16 20:52:21 server systemd[1]: systemd-udevd.service: Failed with result 'signal'.
Apr 16 20:52:21 server systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=9/KILL
Apr 16 20:52:21 server systemd[1]: systemd-timesyncd.service: Unit entered failed state.
Apr 16 20:52:21 server systemd[1]: systemd-timesyncd.service: Failed with result 'signal'.
Apr 16 20:52:21 server systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart.
Apr 16 20:52:21 server systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Apr 16 20:52:21 server systemd[1]: Stopped Network Time Synchronization.
Apr 16 20:52:21 server systemd[1]: Starting Network Time Synchronization...
Apr 16 20:52:21 server systemd[1]: Stopped udev Kernel Device Manager.
Apr 16 20:52:21 server systemd[1]: Starting udev Kernel Device Manager...
Apr 16 20:52:21 server systemd[1]: Starting User Manager for UID 0...
Apr 16 20:52:21 server systemd[1]: Started udev Kernel Device Manager.
Apr 16 20:52:21 server systemd[13160]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 16 20:52:21 server systemd[13160]: Reached target Timers.
Apr 16 20:52:21 server systemd[13160]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 16 20:52:21 server systemd[13160]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 16 20:52:21 server systemd[13160]: Listening on GnuPG cryptographic agent (access for web browsers).
Apr 16 20:52:21 server systemd[13160]: Reached target Sockets.
Apr 16 20:52:21 server systemd[13160]: Reached target Paths.
Apr 16 20:52:21 server systemd[13160]: Reached target Basic System.
Apr 16 20:52:21 server systemd[13160]: Reached target Default.
Apr 16 20:52:21 server systemd[13160]: Startup finished in 31ms.
Apr 16 20:52:21 server systemd[1]: Started User Manager for UID 0.
Apr 16 20:52:21 server systemd[1]: Stopping User Manager for UID 0...
Apr 16 20:52:21 server systemd[13160]: Stopped target Default.
Apr 16 20:52:21 server systemd[13160]: Stopped target Basic System.
Apr 16 20:52:21 server systemd[13160]: Stopped target Timers.
Apr 16 20:52:21 server systemd[13160]: Stopped target Sockets.
Apr 16 20:52:21 server systemd[13160]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 16 20:52:21 server systemd[13160]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 16 20:52:21 server systemd[13160]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 16 20:52:21 server systemd[13160]: Closed GnuPG cryptographic agent (access for web browsers).
Apr 16 20:52:21 server systemd[13160]: Reached target Shutdown.
Apr 16 20:52:21 server systemd[13160]: Starting Exit the Session...
Apr 16 20:52:21 server systemd[13160]: Stopped target Paths.
Apr 16 20:52:21 server systemd[13160]: Received SIGRTMIN+24 from PID 13168 (kill).
Apr 16 20:52:21 server systemd[1]: Stopped User Manager for UID 0.
Apr 16 20:52:21 server systemd[1]: Removed slice User Slice of root.
Apr 16 20:52:21 server systemd[1]: Started Network Time Synchronization.
Apr 16 20:52:21 server systemd-timesyncd[13158]: Synchronized to time server 79.111.152.13:123 (0.debian.pool.ntp.org).
Apr 16 20:53:42 server systemd[1]: systemd-logind.service: Start operation timed out. Terminating.
Apr 16 20:53:42 server systemd[1]: Failed to start Login Service.
Apr 16 20:53:42 server systemd[1]: systemd-logind.service: Unit entered failed state.
Apr 16 20:53:42 server systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Apr 16 20:53:42 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Apr 16 20:53:42 server systemd[1]: Stopped Login Service.
Apr 16 20:53:42 server systemd[1]: Starting Login Service...
Apr 16 20:55:13 server systemd[1]: systemd-logind.service: Start operation timed out. Terminating.
Apr 16 20:55:13 server systemd[1]: Failed to start Login Service.
Apr 16 20:55:13 server systemd[1]: systemd-logind.service: Unit entered failed state.
Apr 16 20:55:13 server systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Apr 16 20:55:13 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Apr 16 20:55:13 server systemd[1]: Stopped Login Service.
Apr 16 20:55:13 server systemd[1]: Starting Login Service...
Apr 16 20:56:43 server systemd[1]: systemd-logind.service: Start operation timed out. Terminating.
Apr 16 20:56:43 server systemd[1]: Failed to start Login Service.
Apr 16 20:56:43 server systemd[1]: systemd-logind.service: Unit entered failed state.
Apr 16 20:56:43 server systemd[1]: systemd-logind.service: Failed with result 'timeout'.
Apr 16 20:56:43 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Apr 16 20:56:43 server systemd[1]: Stopped Login Service.
Apr 16 20:56:43 server systemd[1]: Starting Login Service...
Apr 16 20:57:36 server dbus[13153]: [system] Reloaded configuration
Apr 16 20:57:36 server dbus[13153]: [system] Reloaded configuration
Apr 16 20:58:03 server dbus[13153]: [system] Reloaded configuration
Apr 16 20:58:04 server systemd[1]: Reloading.
Apr 16 20:58:04 server systemd[1]: Started Login Service.
Apr 16 20:58:04 server systemd[1]: Created slice User Slice of root.
Apr 16 20:58:04 server systemd[1]: Starting User Manager for UID 0...
Apr 16 20:58:04 server systemd[1]: Started Session 6 of user root.
Apr 16 20:58:04 server systemd[1]: Started Session 5 of user root.
Apr 16 20:58:04 server systemd[16766]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 16 20:58:04 server systemd[16766]: Reached target Timers.
Apr 16 20:58:04 server systemd[16766]: Listening on GnuPG cryptographic agent (access for web browsers).
Apr 16 20:58:04 server systemd[16766]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 16 20:58:04 server systemd[16766]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 16 20:58:04 server systemd[16766]: Reached target Sockets.
Apr 16 20:58:04 server systemd[16766]: Reached target Paths.
Apr 16 20:58:04 server systemd[16766]: Reached target Basic System.
Apr 16 20:58:04 server systemd[16766]: Reached target Default.
Apr 16 20:58:04 server systemd[16766]: Startup finished in 8ms.
Apr 16 20:58:04 server systemd[1]: Started User Manager for UID 0.
Apr 16 20:58:08 server dbus[13153]: [system] Reloaded configuration
Apr 16 20:58:09 server systemd[1]: Reloading.
Apr 16 20:58:09 server systemd[1]: Reloading.
Apr 16 20:58:16 server systemd[1]: Reloading.
Cообщение объединено 18 апреля 2018, 09:30:19
Я так понял что проблема возникает в том что SYSTEMD не реагирует и его другая служба перезапускает. Как от этого отказаться?