shutdown all vps in same time

Exner

Member
Apr 14, 2022
30
0
6
Is this because of the increased RAM 100% for server or because of CPU?

when i check task history i find

But it happened before or after the shutdown I wonder idk

systlog
Sep 08 19:56:38 helens sshd[1280607]: Disconnected from invalid user eq 85.236.173.182 port 58681 [preauth]
-- Reboot --
Sep 08 19:58:37 helens kernel: Linux version 5.15.35-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.15.35-2 (Thu, 05 May 2022 13:54:35 +0200) ()
Sep 08 19:58:37 helens kernel: Command line: BOOT_IMAGE=/vmlinuz-5.15.35-1-pve root=UUID=bbd544e2-4dc9-47de-aba6-9162c55ac4ed ro nomodeset iommu=pt
Sep 08 19:58:37 helens kernel: KERNEL supported cpus:
Sep 08 19:58:37 helens kernel: Intel GenuineIntel
Sep 08 19:58:37 helens kernel: AMD AuthenticAMD
Sep 08 19:58:37 helens kernel: Hygon HygonGenuine
Sep 08 19:58:37 helens kernel: Centaur CentaurHauls
Sep 08 19:58:37 helens kernel: zhaoxin Shanghai
Sep 08 19:58:37 helens kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 08 19:58:37 helens kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 08 19:58:37 helens kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 08 19:58:37 helens kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Sep 08 19:58:37 helens kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Sep 08 19:58:37 helens kernel: x86/fpu: xstate_offset[9]: 832, xstate_sizes[9]: 8
Sep 08 19:58:37 helens kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
Sep 08 19:58:37 helens kernel: signal: max sigframe size: 3376
Sep 08 19:58:37 helens kernel: BIOS-provided physical RAM map:
Sep 08 19:58:37 helens kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Sep 08 19:58:37 helens kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Sep 08 19:58:37 helens kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009bfefff] usable
Sep 08 19:58:37 helens kernel: BIOS-e820: [mem 0x0000000009bff000-0x0000000009ffffff] reserved
Sep 08 19:58:37 helens kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Sep 08 19:58:37 helens kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
5111111111111.PNG
40.PNG
511111111111e.PNG
 
Last edited:
But it happened before or after the shutdown I wonder idk
The "Sart all VMs and Containers" task is run after the server is started and will start VMs and Containers that have the "Start on boot" option enabled and are not managed by HA.
 
Why the server rebooted is hard to say with the information provided. If there is not enough RAM available, the OOM (out of memory) killer usually kills a process that is using up a lot of RAM. On a Proxmox VE server, this is a VM in most cases. But it should not trigger a reboot.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!