LINUX.ORG.RU
ФорумAdmin

VPS намертво зависает и запускается systemd-coredump.

 ,


0

1
Oct 13 03:26:04 clients systemd-journald[27376]: Journal started
Oct 13 03:26:13 clients systemd-journald[27376]: System journal (/var/log/journal/2ff026d56bfb409ea1ccd8842dc4e1b9) is 2.0G, max 4.0G, 1.9G free.
Oct 13 03:26:21 clients kernel: audit: type=1701 audit(1570933136.813:1254719): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=245 comm="systemd-jour
nal" exe="/usr/lib/systemd/systemd-journald" sig=6 res=1
Oct 13 03:26:25 clients systemd[1]: systemd-journald.service: State 'stop-watchdog' timed out. Terminating.
Oct 13 03:26:36 clients systemd-coredump[27365]: Process 245 (systemd-journal) of user 0 dumped core.
Oct 13 03:26:41 clients systemd-coredump[27365]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.cd438447dcbf4849a43a4d3d3c7126
e8.245.1570933136000000.lz4
Oct 13 03:26:43 clients systemd-coredump[27365]: Stack trace of thread 245:
Oct 13 03:26:46 clients systemd-coredump[27365]: #0  0x00007f30ea245593 n/a (libsystemd-shared-242.so)
Oct 13 03:26:57 clients systemd-coredump[27365]: #1  0x00007f30ea24b149 n/a (libsystemd-shared-242.so)
Oct 13 03:27:00 clients systemd-coredump[27365]: #2  0x00007f30ea24e4c7 n/a (libsystemd-shared-242.so)
Oct 13 03:27:03 clients systemd-coredump[27365]: #3  0x00007f30ea24e9fb sd_event_dispatch (libsystemd-shared-242.so)
Oct 13 03:27:05 clients systemd-coredump[27365]: #4  0x00007f30ea24ebc1 sd_event_run (libsystemd-shared-242.so)
Oct 13 03:27:18 clients systemd-coredump[27365]: #5  0x00005578f27fb5d1 n/a (systemd-journald)
Oct 13 03:27:23 clients systemd-coredump[27365]: #6  0x00007f30ea48fee3 __libc_start_main (libc.so.6)
Oct 13 03:27:32 clients systemd-coredump[27365]: #7  0x00005578f27fdbbe n/a (systemd-journald)
Oct 13 03:27:39 clients systemd-coredump[27365]: Stack trace of thread 27364:
Oct 13 03:27:50 clients systemd-coredump[27365]: #0  0x00007f30ea48e330 n/a (libc.so.6)
Oct 13 03:27:55 clients systemd-coredump[27365]: #1  0x00007f30ea4f4077 __libc_thread_freeres (libc.so.6)
Oct 13 03:29:34 clients systemd-journald[27378]: Journal started
Oct 13 03:29:37 clients systemd-journald[27378]: System journal (/var/log/journal/2ff026d56bfb409ea1ccd8842dc4e1b9) is 2.0G, max 4.0G, 1.9G free.
Oct 13 03:29:38 clients systemd-coredump[27365]: #2  0x00007f30e9a905a5 start_thread (libpthread.so.0)
Oct 13 03:29:39 clients systemd-coredump[27365]: #3  0x00007f30ea5650e3 __clone (libc.so.6)
Oct 13 03:29:43 clients systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
Oct 13 03:29:50 clients systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
Oct 13 03:29:58 clients kernel: audit: type=1131 audit(1570935252.894:1254720): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald
 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 13 03:30:04 clients systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Oct 13 03:30:06 clients systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
Oct 13 03:30:10 clients systemd[1]: systemd-journal-flush.service: Succeeded.
Oct 13 03:30:14 clients systemd[1]: Stopped Flush Journal to Persistent Storage.
Oct 13 03:30:15 clients kernel: audit: type=1131 audit(1570936194.725:1254721): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-
flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 03:30:16 clients systemd[1]: Stopping Flush Journal to Persistent Storage...
Oct 13 03:30:18 clients systemd[1]: Stopped Journal Service.
Oct 13 03:30:19 clients kernel: audit: type=1130 audit(1570936249.012:1254722): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald
 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 03:30:20 clients kernel: audit: type=1131 audit(1570936251.147:1254723): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald
 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 03:30:26 clients systemd[1]: Starting Journal Service...
Oct 13 03:30:27 clients systemd[1]: systemd-journald.service: Start operation timed out. Terminating.
Oct 13 03:30:27 clients systemd[1]: systemd-journald.service: Main process exited, code=killed, status=15/TERM
Oct 13 03:30:28 clients systemd[1]: systemd-journald.service: Failed with result 'timeout'.
Oct 13 03:30:29 clients systemd[1]: Failed to start Journal Service.
Oct 13 03:30:29 clients systemd[1]: Dependency failed for Flush Journal to Persistent Storage.
Oct 13 03:30:31 clients systemd[1]: systemd-journal-flush.service: Job systemd-journal-flush.service/start failed with result 'dependency'.
Oct 13 03:30:32 clients kernel: audit: type=1130 audit(1570937079.887:1254724): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald
 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 13 03:30:34 clients kernel: audit: type=1131 audit(1570937082.275:1254725): pid=365 uid=0 auid=4294967295 ses=4294967295 msg='unit=api.imes.su co
mm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 13 03:30:36 clients systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Oct 13 03:30:42 clients systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 2.
Oct 13 03:30:51 clients systemd[1]: Stopped Journal Service.
Oct 13 03:30:54 clients kernel: audit: type=1130 audit(1570937095.025:1254726): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald
 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 03:30:57 clients kernel: audit: type=1131 audit(1570937095.218:1254727): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald
 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 13 03:31:00 clients systemd[1]: Starting Journal Service...
Oct 13 03:31:06 clients kernel: audit: type=1305 audit(1570937152.530:1254728): op=set audit_enabled=1 old=1 auid=4294967295 ses=4294967295 res=1

Это последние строки из journalctl до принудительной перезагрузки.
Т.к. к серверу не удаётся подключиться. Процессор забит на 100%.
Вывод команды coredumpctl list пуст.
Такая хрень происходит только с двумя VPS-ками из 6.
Началось это пару-тройку месяцев назад.
Происходит не часто, пока что всего 4 раза такое было.
По 2 раза на 2 VPS-ках.

systemd 242 (242.84-2-arch)
+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid
Linux clients 5.2.9-arch1-1-ARCH #1 SMP PREEMPT Fri Aug 16 11:29:43 UTC 2019 x86_64 GNU/Linux


Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.