The server became kreshetsya. Help me to understand

123
Avatar 130
#11
Miracle:

I would be grateful for any educated advice.

You comrades write correctly, there is little information.

Without this information, the only thing I can advise is to see if your virtual machine is no swap, and ends with the memory it can lead to reboot to kilyaniyu processes and hanging up.

And in the long run you need to ask your hosting company, suddenly have a problem with iron and server Ruban with your virtual machine.

Avatar 816
#12
Miracle:
friends. I am willing to understand himself. I just need your help.

Well, I'll try to help.

Let us complete information about the server to start.

Не стоит плодить сущности без необходимости
M2 318
#13

Miracle,

vmcore files - this memory images, which makes the kdump, when the crash the kernel Linux. Information are not needed here.

Miracle:
vmcore-dmesg.txt

theoretically it can be information that will help in resolving the issue

questions:

1) What server - virtual or physical? If the virtual - what type of virtualization?

2) What OS is worth? Operating system and version.

3) What is the number of memory available? How much of it is occupied on average? Infu on htop / top can look.

4) Which of the heavy installed on the server?

------------------- Крутые VPS и дедики. Качество по разумной цене (http://cp.inferno.name/view.php?product=1212&gid=1) VPS25OFF - скидка 25% на первый платеж по ссылке выше
Avatar 219
#14

It would be nice otezki logs for time Crush with at least

/ Var / log / dmesg

/ Var / log / messages

M 349
#15
andreyka:
Let us complete information about the server to start.

centos 7

32 grga

2TB

hetsner

that a specific need? it's all that came to mind)

mark2011:
4) Which of the heavy installed on the server?

I do not know. seems OK.

---------- Posted 17.06.2020 at 13:53 ----------

treshnyuk:
/ Var / log / messages



16 Jun 08 1:58:01 systemd: Started Session 5686 of user root.
16 Jun 08 1:58:01 systemd: Removed slice User Slice of root.
16 Jun 08 2:00:50 journal: Runtime journal is using 8.0M (max allowed 1.5G, trying to leave 2.3G free of 15.5G available in † 'current limit 1.5G).
Jun 16 2:00:50 08 kernel: Initializing cgroup subsys cpuset
Jun 16 2:00:50 08 kernel: Initializing cgroup subsys cpu
Jun 16 2:00:50 08 kernel: Initializing cgroup subsys cpuacct
Jun 16 2:00:50 08 kernel: Linux version 3.10.0-1127.10.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC)) # 1 3 SMP Wed Jun 2020 14:28:03 UTC
Jun 16 08 2:00:50 kernel: Command line: BOOT_IMAGE = / vmlinuz-3.10.0-1127.10.1.el7.x86_64 root = / dev / vg / root ro nomodeset rd.auto = 1 crashkernel = auto LANG = en_US .UTF-8
Jun 16 2:00:50 08 kernel: e820: BIOS-provided physical RAM map:
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000c6bd9fff] usable
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000c6bda000-0x00000000c6be0fff] ACPI NVS
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000c6be1000-0x00000000c7026fff] usable
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000c7027000-0x00000000c75b7fff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000c75b8000-0x00000000d8dacfff] usable
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000d8dad000-0x00000000d8e36fff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000d8e37000-0x00000000d8e90fff] usable
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000d8e91000-0x00000000d8fc8fff] ACPI NVS
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000d8fc9000-0x00000000d9ffefff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000d9fff000-0x00000000d9ffffff] usable
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000db000000-0x00000000df1fffff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 16 08 2:00:50 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081edfffff] usable
Jun 16 08 2:00:50 kernel: NX (Execute Disable) protection: active
Jun 16 2:00:50 08 kernel: SMBIOS 2.7 present.
Jun 16 08 2:00:50 kernel: DMI: MSI MS-7816 / H87-G43 (MS-7816), BIOS V2.14B6 08/23/2013
Jun 16 2:00:50 08 kernel: e820: last_pfn = 0x81ee00 max_arch_pfn = 0x400000000
Jun 16 08 2:00:50 kernel: PAT configuration [0-7]: WB WC UC- UC WB WP UC- UC
Jun 16 2:00:50 08 kernel: total RAM covered: 32670M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 64K # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 128K # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 256K # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 512K # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 1M # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 2M # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 4M # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 8M # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 16M # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 32M # 011num_reg: 10 # 011lose cover RAM: -18M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 64M # 011num_reg: 10 # 011lose cover RAM: -18M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 128M # 011num_reg: 10 # 011lose cover RAM: -16M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 256M # 011num_reg: 10 # 011lose cover RAM: -16M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 512M # 011num_reg: 10 # 011lose cover RAM: -16M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 1G # 011num_reg: 10 # 011lose cover RAM: -512M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 2G # 011num_reg: 10 # 011lose cover RAM: -1536M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 4G # 011num_reg: 10 # 011lose cover RAM: -3584M
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 8G # 011num_reg: 10 # 011lose cover RAM: -7G
Jun 16 2:00:50 08 kernel: * BAD * gran_size: 64K # 011chunk_size: 16G # 011num_reg: 10 # 011lose cover RAM: -14G
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 32G # 011num_reg: 10 # 011lose cover RAM: 2M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 64G # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 128G # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 64K # 011chunk_size: 256G # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 128K # 011chunk_size: 128K # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 128K # 011chunk_size: 256K # 011num_reg: 10 # 011lose cover RAM: 238M
Jun 16 2:00:50 08 kernel: gran_size: 128K # 011chunk_size: 512K # 011num_reg: 10 # 011lose cover RAM: 238M




---------- Posted 17.06.2020 at 13:54 ----------

log at this time is very long. here I can not insert. Does it make sense?
treshnyuk:
/ Var / log / dmesg

there are no such file

отец сыночка, лапочки дочки и еще одного сыночка
Avatar 151

This log "lift", and need just a little earlier to watch what was happening at the time of the "fall".

M 349
#17

everything here is

16 Jun 08 1:46:01 systemd: Created slice User Slice of root.
16 Jun 08 1:46:01 systemd: Started Session 5664 of user root.
16 Jun 08 1:46:01 systemd: Started Session 5663 of user root.
16 Jun 08 1:46:01 systemd: Started Session 5665 of user root.
16 Jun 08 1:46:01 systemd: Removed slice User Slice of root.
16 Jun 08 1:48:01 systemd: Created slice User Slice of root.
16 Jun 08 1:48:01 systemd: Started Session 5666 of user root.
16 Jun 08 1:48:01 systemd: Started Session 5668 of user root.
16 Jun 08 1:48:01 systemd: Started Session 5667 of user root.
16 Jun 08 1:48:01 systemd: Removed slice User Slice of root.
16 Jun 08 1:50:01 systemd: Created slice User Slice of root.
16 Jun 08 1:50:01 systemd: Started Session 5669 of user root.
16 Jun 08 1:50:01 systemd: Started Session 5671 of user root.
16 Jun 08 1:50:01 systemd: Started Session 5672 of user root.
16 Jun 08 1:50:01 systemd: Started Session 5670 of user root.
16 Jun 08 1:50:01 systemd: Created slice User Slice of munin.
16 Jun 08 1:50:01 systemd: Started Session 5673 of user munin.
16 Jun 08 1:50:01 systemd: Removed slice User Slice of munin.
16 Jun 08 1:50:01 systemd: Removed slice User Slice of root.
16 Jun 08 1:52:01 systemd: Created slice User Slice of root.
16 Jun 08 1:52:01 systemd: Started Session 5675 of user root.
16 Jun 08 1:52:01 systemd: Started Session 5676 of user root.
16 Jun 08 1:52:01 systemd: Started Session 5674 of user root.
16 Jun 08 1:52:02 systemd: Removed slice User Slice of root.
16 Jun 08 1:54:01 systemd: Created slice User Slice of root.
16 Jun 08 1:54:01 systemd: Started Session 5679 of user root.
16 Jun 08 1:54:01 systemd: Started Session 5677 of user root.
16 Jun 08 1:54:01 systemd: Started Session 5678 of user root.
16 Jun 08 1:54:01 systemd: Removed slice User Slice of root.
16 Jun 08 1:55:01 systemd: Created slice User Slice of munin.
16 Jun 08 1:55:01 systemd: Started Session 5680 of user munin.
16 Jun 08 1:55:01 systemd: Removed slice User Slice of munin.
16 Jun 08 1:56:01 systemd: Created slice User Slice of root.
16 Jun 08 1:56:01 systemd: Started Session 5683 of user root.
16 Jun 08 1:56:01 systemd: Started Session 5681 of user root.
16 Jun 08 1:56:01 systemd: Started Session 5682 of user root.
16 Jun 08 1:56:02 systemd: Removed slice User Slice of root.
16 Jun 08 1:58:01 systemd: Created slice User Slice of root.
16 Jun 08 1:58:01 systemd: Started Session 5685 of user root.
16 Jun 08 1:58:01 systemd: Started Session 5684 of user root.
16 Jun 08 1:58:01 systemd: Started Session 5686 of user root.

The only difference from the above that this piece

Jun 15 23:58:02 08 systemd: Removed slice User Slice of root.
Jun 16 00:00:01 08 systemd: Starting update of the root trust anchor for DNSSEC validation in unbound ...
Jun 16 00:00:01 08 systemd: Created slice User Slice of root.
Jun 16 00:00:01 08 systemd: Started Session 5463 of user root.
Jun 16 00:00:01 08 systemd: Started Session 5467 of user root.
Jun 16 00:00:01 08 systemd: Started Session 5464 of user root.
Jun 16 00:00:01 08 systemd: Started Session 5468 of user root.
Jun 16 00:00:01 08 systemd: Created slice User Slice of munin.
Jun 16 00:00:01 08 systemd: Started Session 5469 of user munin.
Jun 16 00:00:01 08 systemd: Started Session 5470 of user root.
Jun 16 00:00:01 08 systemd: Started Session 5466 of user root.
Jun 16 00:00:01 08 systemd: Started Session 5465 of user root.
Jun 16 00:00:01 08 systemd: Started Session 5471 of user root.
Jun 16 00:00:01 08 systemd: Started update of the root trust anchor for DNSSEC validation in unbound.
Jun 16 00:00:01 08 systemd: Removed slice User Slice of munin.
M 349
#18

I thought someone would?

E 124
#19
Miracle:
I thought someone would?

Yes - hire a system administrator to let him $ 100 and he's 15 minutes will cause server crashes

Avatar 816
#20
Miracle:
I thought someone would?

Yes, the thought is - is not enough information.

What type of server - virtual or physical?

Version of the kernel?

Unusual lines in the log?

Without this information, you simply can not help.

123

To post a new comment, please log in or register