Proxmox sudden -- Reboot --

A

andzejsp

New Member
Mar 5, 2024
15
0
1
Hello, im struggling to determine why my device that runs proxmox started to suddenly reboot at random times.

SYS logs have no explanation that would lead me on to something. Where else can i look? What else can i do?

I started to notice that yesterday, who knows when it really started to happen.

This morning i disabled postfix as i usually do, because i dont have email configured, and it spams logs.

Then it was working good, i logged in to check if it was running, then went to other room and then -- Reboot --

I run this on brand new (2month old) protectli VP4650. I run many docker lxc containers. it was working fine last week. I didnt do any proxmox upgrades or anything like that. It was running 24h as it should because its my firewall.

I did upgrade from system menu in proxmox yesterday. And my web ui is at 8.1.4 version.

Code: 
Mar 05 06:53:47 firewall-boi pvedaemon[983]: <root@pam> successful auth for user 'root@pam'
Mar 05 06:54:40 firewall-boi pvedaemon[984]: <root@pam> starting task UPID:firewall-boi:000169C8:000FB6FF:65E6A590:srvstop:postfix:root@pam:
Mar 05 06:54:40 firewall-boi pvedaemon[92616]: stopping service postfix: UPID:firewall-boi:000169C8:000FB6FF:65E6A590:srvstop:postfix:root@pam:
Mar 05 06:54:40 firewall-boi systemd[1]: postfix.service: Deactivated successfully.
Mar 05 06:54:40 firewall-boi systemd[1]: Stopped postfix.service - Postfix Mail Transport Agent.
Mar 05 06:54:40 firewall-boi systemd[1]: Stopping postfix@-.service - Postfix Mail Transport Agent (instance -)...
Mar 05 06:54:40 firewall-boi pvedaemon[984]: <root@pam> end task UPID:firewall-boi:000169C8:000FB6FF:65E6A590:srvstop:postfix:root@pam: OK
Mar 05 06:54:40 firewall-boi postfix[92619]: Postfix is using backwards-compatible default settings
Mar 05 06:54:40 firewall-boi postfix[92619]: See http://www.postfix.org/COMPATIBILITY_README.html for details
Mar 05 06:54:40 firewall-boi postfix[92619]: To disable backwards compatibility use "postconf compatibility_level=3.6" and "postfix reload"
Mar 05 06:54:40 firewall-boi postfix/postfix-script[92625]: stopping the Postfix mail system
Mar 05 06:54:40 firewall-boi postfix/master[938]: terminating on signal 15
Mar 05 06:54:40 firewall-boi systemd[1]: postfix@-.service: Deactivated successfully.
Mar 05 06:54:40 firewall-boi systemd[1]: Stopped postfix@-.service - Postfix Mail Transport Agent (instance -).
Mar 05 07:17:01 firewall-boi CRON[103549]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 05 07:17:01 firewall-boi CRON[103550]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 05 07:17:01 firewall-boi CRON[103549]: pam_unix(cron:session): session closed for user root
Mar 05 07:29:45 firewall-boi pvedaemon[985]: <root@pam> successful auth for user 'root@pam'
Mar 05 07:48:42 firewall-boi systemd[1]: Starting apt-daily.service - Daily apt download activities...
Mar 05 07:48:42 firewall-boi systemd[1]: apt-daily.service: Deactivated successfully.
Mar 05 07:48:42 firewall-boi systemd[1]: Finished apt-daily.service - Daily apt download activities.
Mar 05 07:54:15 firewall-boi pvedaemon[983]: <root@pam> successful auth for user 'root@pam'
-- Reboot --
Mar 05 07:57:08 firewall-boi kernel: Linux version 6.5.13-1-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-1 (2024-02-05T13:50Z) ()
Mar 05 07:57:08 firewall-boi kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.13-1-pve root=/dev/mapper/pve-root ro quiet
Mar 05 07:57:08 firewall-boi kernel: KERNEL supported cpus:
Mar 05 07:57:08 firewall-boi kernel:   Intel GenuineIntel
Mar 05 07:57:08 firewall-boi kernel:   AMD AuthenticAMD
Mar 05 07:57:08 firewall-boi kernel:   Hygon HygonGenuine
Mar 05 07:57:08 firewall-boi kernel:   Centaur CentaurHauls
Mar 05 07:57:08 firewall-boi kernel:   zhaoxin   Shanghai
Mar 05 07:57:08 firewall-boi kernel: BIOS-provided physical RAM map:
Mar 05 07:57:08 firewall-boi kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] reserved
Mar 05 07:57:08 firewall-boi kernel: BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable
Mar 05 07:57:08 firewall-boi kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 05 07:57:08 firewall-boi kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000097672fff] usable
Mar 05 07:57:08 firewall-boi kernel: BIOS-e820: [mem 0x0000000097673000-0x0000000097673fff] reserved
Mar 05 07:57:08 firewall-boi kernel: BIOS-e820: [mem 0x0000000097674000-0x000000009767afff] usable


I dont want to think that it is a hardware failure :(... its just 2 months old. Is there a way i could find it out? Im not super knowledgeable in linux management. I would really appreciate any help.


Could it be that some eth device that is connected to the firewall device that runs proxmox is crashing it? I got some old tplink router connected to it for wifi.

My observations on cpu/memory usage - cpu stays below 1% and memory less than 4/32gb used. It crashed during night too. How i determined that? Logging into webui and check uptime on the node. :(.

My only options that i can do is:
1)memtest, as im suspicious of the cheap kingston ram, but it will have to be ran for hours.. :(
2)nuke system, clean install :( i was able to backup my containers yesterday but if the problem is container related then ill be bringing the bad juju on the clean install :(
3) idk what else to do...
 
Last edited:
Hi,
please provide the exact hardware details of the host (CPU, motherboard, RAM, ...) and check if you get any further output on a display attached directly to the machine when the host crashes (not all logs might make it to disk).

Bad memory is most definitely something you want to exclude by running an extended memory test.

Also, please make sure to have the latest firmware and microcode for your system installed, see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_firmware_updates
 
Chris said:
Hi,
please provide the exact hardware details of the host (CPU, motherboard, RAM, ...) and check if you get any further output on a display attached directly to the machine when the host crashes (not all logs might make it to disk).

Bad memory is most definitely something you want to exclude by running an extended memory test.

Also, please make sure to have the latest firmware and microcode for your system installed, see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_firmware_updates
Click to expand...
Catching crash on screen will be almost impossible because the reboots are random, onec every few hours. sometimes 2h sometimes 5, sometimes few minutes. I could monitor it but it will take days to catch it :(.

Can you tell me how to check if im on latest microcode?

Bellow all the info i could get given my knowledge.

Code: 
root@firewall-boi:~# lscpu
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  8
  On-line CPU(s) list:   0-7
Vendor ID:               GenuineIntel
  BIOS Vendor ID:        GenuineIntel
  Model name:            Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
    BIOS Model name:     Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz  CPU @ 2.1GHz
    BIOS CPU family:     12
    CPU family:          6
    Model:               166
    Thread(s) per core:  2
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            1
    CPU(s) scaling MHz:  87%
    CPU max MHz:         4200.0000
    CPU min MHz:         400.0000
    BogoMIPS:            4199.88
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xt
                         opology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_
                         lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clfl
                         ushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp vnmi pku ospke md_clear flush_l1d arch_capabilities
Virtualization features:
  Virtualization:        VT-x
Caches (sum of all):    
  L1d:                   128 KiB (4 instances)
  L1i:                   128 KiB (4 instances)
  L2:                    1 MiB (4 instances)
  L3:                    6 MiB (1 instance)
NUMA:                  
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
Vulnerabilities:        
  Gather data sampling:  Vulnerable: No microcode
  Itlb multihit:         KVM: Mitigation: VMX disabled
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Mitigation; Clear CPU buffers; SMT vulnerable
  Retbleed:              Mitigation; Enhanced IBRS
  Spec rstack overflow:  Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds:                 Mitigation; Microcode
  Tsx async abort:       Not affected
 
 
 
 
root@firewall-boi:~# lspci
00:00.0 Host bridge: Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Comet Lake UHD Graphics (rev 05)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH-LP Shared SRAM
00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
00:1a.0 SD Host controller: Intel Corporation Device 02c4
00:1c.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #5 (rev f0)
00:1c.5 PCI bridge: Intel Corporation Device 02bd (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device 02be (rev f0)
00:1c.7 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port (rev f0)
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.1 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #10 (rev f0)
00:1d.3 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #12 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller
00:1f.3 Audio device: Intel Corporation Comet Lake PCH-LP cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH-LP SMBus Host Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake SPI (flash) Controller
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
02:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
03:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
06:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
08:00.0 Non-Volatile memory controller: Shenzhen Longsys Electronics Co., Ltd. Device 1602 (rev 01)



root@firewall-boi:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


root@firewall-boi:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
loop0          7:0    0   20G  0 loop
loop1          7:1    0    4G  0 loop
loop2          7:2    0    8G  0 loop
loop3          7:3    0    8G  0 loop
loop4          7:4    0    8G  0 loop
loop5          7:5    0    8G  0 loop
loop6          7:6    0    8G  0 loop
loop7          7:7    0   24G  0 loop
loop8          7:8    0    8G  0 loop
loop9          7:9    0   24G  0 loop
loop10         7:10   0    8G  0 loop
loop11         7:11   0    8G  0 loop
loop12         7:12   0    8G  0 loop
loop13         7:13   0  400G  0 loop
loop14         7:14   0  220G  0 loop
loop15         7:15   0   40G  0 loop
loop16         7:16   0   60G  0 loop
loop17         7:17   0  110G  0 loop
loop18         7:18   0    8G  0 loop
loop19         7:19   0    8G  0 loop
loop20         7:20   0   24G  0 loop
mmcblk0      179:0    0 14.6G  0 disk
mmcblk0boot0 179:8    0    4M  1 disk
mmcblk0boot1 179:16   0    4M  1 disk
nvme0n1      259:0    0  1.9T  0 disk
├─nvme0n1p1  259:1    0 1007K  0 part
├─nvme0n1p2  259:2    0    1G  0 part /boot/efi
└─nvme0n1p3  259:3    0  1.9T  0 part
  ├─pve-swap 252:0    0  7.6G  0 lvm  [SWAP]
  └─pve-root 252:1    0  1.9T  0 lvm  /
 
 
root@firewall-boi:~# cat /proc/meminfo
MemTotal:       32725112 kB
MemFree:        23620780 kB
MemAvailable:   29053328 kB
Buffers:          376780 kB
Cached:          5546356 kB
SwapCached:        41332 kB
Active:          4578412 kB
Inactive:        3845844 kB
Active(anon):    2437108 kB
Inactive(anon):   281516 kB
Active(file):    2141304 kB
Inactive(file):  3564328 kB
Unevictable:         124 kB
Mlocked:               0 kB
SwapTotal:       7983100 kB
SwapFree:        7834876 kB
Zswap:                 0 kB
Zswapped:              0 kB
Dirty:               340 kB
Writeback:             0 kB
AnonPages:       2498904 kB
Mapped:          1553772 kB
Shmem:            217480 kB
KReclaimable:     187116 kB
Slab:             355692 kB
SReclaimable:     187116 kB
SUnreclaim:       168576 kB
KernelStack:       22092 kB
PageTables:        41608 kB
SecPageTables:         0 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    24345656 kB
Committed_AS:   13077012 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      111188 kB
VmallocChunk:          0 kB
Percpu:            14912 kB
HardwareCorrupted:     0 kB
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
ShmemPmdMapped:        0 kB
FileHugePages:         0 kB
FilePmdMapped:         0 kB
Unaccepted:            0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
Hugetlb:               0 kB
DirectMap4k:      387172 kB
DirectMap2M:    11014144 kB
DirectMap1G:    23068672 kB


root@firewall-boi:~# cat /proc/version
Linux version 6.5.13-1-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-1 (2024-02-05T13:50Z)


root@firewall-boi:~# grep microcode /proc/cpuinfo | uniq
microcode       : 0xf0

root@firewall-boi:~# dmesg | grep microcode
[    0.182435] GDS: Vulnerable: No microcode
[    0.558807] microcode: Microcode Update Driver: v2.2.


The specs on the device is:
Code: 
VP4650-6PortIntel®i5×1  
Memory:Kingston ValueRAM, SODIMM, DDR4, 32 GB, 2666 MHz, CL19 (KVR26S19D8/32)
Storage(M.2NVMeorM.2SATASSD):SSD 2TB SSD Lexar NM790 2TB M.2 2280 PCI-E x4 Gen4 NVMe (LNM790X002T-RNNNG)
OperatingSystem(Pre-installedM.2):None
Storage(2.5"SSD):None
OperatingSystem(Pre-installed2.5"SSD):None
WiFiModule:None
4G/5GModem:None
External5GLTEModemWallMountBrackets:None
DINRailKit:None
TPM:None
Vault:VP4650-Core
BIOS:coreboot(OpenSource)BIOS
PowerCable:EUPowerCable(IECTypes"E"and"F")
Labels:PortReferenceLabels

It is a custom device by Protectli company, with custom motherboard i think. Model of the device is VP4650. All i can change is nvme storage and sodimm ram modules.


Later this evening ill try to do memtest. Did proxmox came with memtest preinstalled? I forgot what the boot menu looked like, its been long time since i had to plug a screen to it.

EDIT:
Added this
Code: 
root@firewall-boi:~# pveversion --verbose
proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5: 6.5.13-1
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve2
 
Last edited:
Its a fanless system AFAIK, in my personal experience, after overloading it with LXC's/VM's, high NIC activity (6 2.5's on that model AFAIK), mem activity + nvme etc. its bound to overheat at some stage. Also check the power brick supply.
Just my 2 cents!
 
  • Like
Reactions: Chris
gfngfn256 said:
Its a fanless system AFAIK, in my personal experience, after overloading it with LXC's/VM's, high NIC activity (6 2.5's on that model AFAIK), mem activity + nvme etc. its bound to overheat at some stage. Also check the power brick supply.
Just my 2 cents!
Click to expand...
How would you suggest i check power brick? I dont exactly have lab bench available to check it with prongs etc.. Any home made recommendations on how to check it?

The system reboots when its not doing any compute, like i said it rebooted in the night while i was sleeping and nothing was being done on the network/lxc containers.

Yes its warm to touch, but its designed to be like that. Id say its around 40C, warmer than human but still am able to hold hand on it. The case i mean. Not sure about internals.
 
andzejsp said:
How would you suggest i check power brick? I dont exactly have lab bench available to check it with prongs etc.. Any home made recommendations on how to check it?
Click to expand...
Well if thats the case, check the Voltage and Amps rating of the current (supplied?) brick, and try to match it with another available one, maybe higher Amps but SAME VOLTAGE.
Haven't got any other ideas on testing current one without special equipment.
 
gfngfn256 said:
Well if thats the case, check the Voltage and Amps rating of the current (supplied?) brick, and try to match it with another available one, maybe higher Amps but SAME VOLTAGE.
Haven't got any other ideas on testing current one without special equipment.
Click to expand...
But if it was a power issue then the system would crash when it would be under heavy load, like booting, or starting lxc containers etc. But it never fails during those times, it fails when its idle, at 0-2% CPU usage.

I got some old un-calibrated multimeter, i doubt it will show me precise values, but thats another vector i could use to trouble shoot. Thanks.

My spidey senses are tingling thinking that its a ram issue. Never had ram failures since ddr3. Maybe i was just unlucky.. Other than ram, idk what else on all-in-one SOC type build could fail, if not the whole board, but you gotta be Louis Rossmann to find the correct ppbus of sorts to trouble shoot.

But the Chris guy told about microcode update. How can i check which version im on? I posted the outputs of microcode thingies in previous posts, it looks like the one from the documentation page, so im not sure if i should try to update it or not.
 
I did this, and it seem no error on the NVME tho i got 13 unsafe shutdowns :(

Code: 
smartctl -t long -a /dev/nvme0n1

root@firewall-boi:~# smartctl -t long -a /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.13-1-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Lexar SSD NM790 2TB
Serial Number:                      NKK699R004737P2202
Firmware Version:                   11296
PCI Vendor/Subsystem ID:            0x1d97
IEEE OUI Identifier:                0xcaf25b
Total NVM Capacity:                 2,048,408,248,320 [2.04 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,048,408,248,320 [2.04 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            caf25b 035e000151
Local Time is:                      Tue Mar  5 14:34:32 2024 EET
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x02):         Cmd_Eff_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     90 Celsius
Critical Comp. Temp. Threshold:     95 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.50W       -        -    0  0  0  0        0       0
 1 +     5.80W       -        -    1  1  1  1        0       0
 2 +     3.60W       -        -    2  2  2  2        0       0
 3 -   0.0500W       -        -    3  3  3  3     5000   10000
 4 -   0.0025W       -        -    4  4  4  4     8000   45000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        40 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    9,130,375 [4.67 TB]
Data Units Written:                 7,688,031 [3.93 TB]
Host Read Commands:                 132,594,203
Host Write Commands:                102,959,448
Controller Busy Time:               170
Power Cycles:                       20
Power On Hours:                     1,026
Unsafe Shutdowns:                   13
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    5
Critical Comp. Temperature Time:    9
Temperature Sensor 1:               40 Celsius
Temperature Sensor 2:               35 Celsius
Thermal Temp. 1 Total Time:         151

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

EDIT:

While im not home yet, checking upon the device i can see that it crashed few times, seeing those holes in memory usage and network traffic. Ar you can see, the cpu mostly stay below 1%, im doubting that something is overheating, SMART on nvme (hot component) said it was 40C.

Im going with hunch that its a bad ram module :(

journalctl -f

Doesnt show any activity at all.

1709645115177.png
 
Last edited:
Quick question, do i need to worry about these yellow errors? They show up whenever i do stuff with lxc that is running docker

EDIT:
well as soon as i was starting to do things with the device, like apt update/upgrade the lxc containers, it crashed.


last output:

Code: 
Mar 05 17:12:29 firewall-boi kernel: br-4e964e86e5ff: port 2(veth8ec4ee1) entered blocking state
Mar 05 17:12:29 firewall-boi kernel: br-4e964e86e5ff: port 2(veth8ec4ee1) entered forwarding state
Mar 05 17:12:31 firewall-boi pvedaemon[94222]: starting lxc termproxy UPID:firewall-boi:0001700E:000EDF68:65E7365F:vncproxy:212:root@pam:
Mar 05 17:12:31 firewall-boi pvedaemon[986]: <root@pam> starting task UPID:firewall-boi:0001700E:000EDF68:65E7365F:vncproxy:212:root@pam:
Mar 05 17:12:31 firewall-boi pvedaemon[985]: <root@pam> successful auth for user 'root@pam'
Mar 05 17:12:32 firewall-boi pvestatd[955]: modified cpu set for lxc/200: 0-1
Mar 05 17:13:01 firewall-boi pvedaemon[985]: <root@pam> successful auth for user 'root@pam'
Mar 05 17:13:46 firewall-boi pvedaemon[986]: <root@pam> end task UPID:firewall-boi:0001700E:000EDF68:65E7365F:vncproxy:212:root@pam: OK
Mar 05 17:13:46 firewall-boi pvedaemon[985]: <root@pam> starting task UPID:firewall-boi:000172C5:000EFCE3:65E736AA:vncproxy:211:root@pam:
Mar 05 17:13:46 firewall-boi pvedaemon[94917]: starting lxc termproxy UPID:firewall-boi:000172C5:000EFCE3:65E736AA:vncproxy:211:root@pam:
Mar 05 17:13:46 firewall-boi pvedaemon[984]: <root@pam> successful auth for user 'root@pam'
Mar 05 17:14:01 firewall-boi pvedaemon[985]: <root@pam> end task UPID:firewall-boi:000172C5:000EFCE3:65E736AA:vncproxy:211:root@pam: OK
Mar 05 17:14:04 firewall-boi pvedaemon[985]: <root@pam> starting task UPID:firewall-boi:00017398:000F03E9:65E736BC:vncproxy:211:root@pam:
Mar 05 17:14:04 firewall-boi pvedaemon[95128]: starting lxc termproxy UPID:firewall-boi:00017398:000F03E9:65E736BC:vncproxy:211:root@pam:
Mar 05 17:14:04 firewall-boi pvedaemon[984]: <root@pam> successful auth for user 'root@pam'
Mar 05 17:14:57 firewall-boi kernel: br-03a083494198: port 1(veth15135a2) entered disabled state
Mar 05 17:14:57 firewall-boi kernel: vethb3e51c6: renamed from eth0
Mar 05 17:14:57 firewall-boi kernel: br-03a083494198: port 1(veth15135a2) entered disabled state
Mar 05 17:14:57 firewall-boi kernel: veth15135a2 (unregistering): left allmulticast mode
Mar 05 17:14:57 firewall-boi kernel: veth15135a2 (unregistering): left promiscuous mode
Mar 05 17:14:57 firewall-boi kernel: br-03a083494198: port 1(veth15135a2) entered disabled state
Mar 05 17:14:57 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth5051163) entered disabled state
Mar 05 17:14:57 firewall-boi kernel: vethb77cc16: renamed from eth0
Mar 05 17:14:57 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth5051163) entered disabled state
Mar 05 17:14:58 firewall-boi kernel: veth5051163 (unregistering): left allmulticast mode
Mar 05 17:14:58 firewall-boi kernel: veth5051163 (unregistering): left promiscuous mode
Mar 05 17:14:58 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth5051163) entered disabled state
Mar 05 17:14:58 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth239678b) entered disabled state
Mar 05 17:14:58 firewall-boi kernel: veth89838c4: renamed from eth0
Mar 05 17:14:58 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth239678b) entered disabled state
Mar 05 17:14:58 firewall-boi kernel: veth239678b (unregistering): left allmulticast mode
Mar 05 17:14:58 firewall-boi kernel: veth239678b (unregistering): left promiscuous mode
Mar 05 17:14:58 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth239678b) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(vethb8ff41e) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: veth91eaac3: renamed from eth0
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 2(vetha7b81b5) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: veth7b2e13c: renamed from eth0
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(vethb8ff41e) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: vethb8ff41e (unregistering): left allmulticast mode
Mar 05 17:15:08 firewall-boi kernel: vethb8ff41e (unregistering): left promiscuous mode
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(vethb8ff41e) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 2(vetha7b81b5) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: vetha7b81b5 (unregistering): left allmulticast mode
Mar 05 17:15:08 firewall-boi kernel: vetha7b81b5 (unregistering): left promiscuous mode
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 2(vetha7b81b5) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: overlayfs: fs on '/var/lib/docker/overlay2/check-overlayfs-support2693862200/lower2' does not support file handles, falling back to xino=off.
Mar 05 17:15:08 firewall-boi kernel: overlayfs: fs on '/var/lib/docker/overlay2/metacopy-check371506657/l1' does not support file handles, falling back to xino=off.
Mar 05 17:15:08 firewall-boi kernel: overlayfs: fs on '/var/lib/docker/overlay2/l/GIKMAZNZMZTS5LVLFLMLYSAPJ4' does not support file handles, falling back to xino=off.
Mar 05 17:15:08 firewall-boi kernel: overlayfs: fs on '/var/lib/docker/overlay2/l/R3TLLLRHNRVFX6CZCUVGXRFT2S' does not support file handles, falling back to xino=off.
Mar 05 17:15:08 firewall-boi kernel: overlayfs: fs on '/var/lib/docker/overlay2/l/65MVY6BOVFXPWAHBIAIJLMSJWM' does not support file handles, falling back to xino=off.
Mar 05 17:15:08 firewall-boi kernel: overlayfs: fs on '/var/lib/docker/overlay2/l/PSNGFSH3JYH7GP2OCTB5CNTX3J' does not support file handles, falling back to xino=off.
Mar 05 17:15:08 firewall-boi kernel: overlayfs: fs on '/var/lib/docker/overlay2/l/3Q2WGPHTAXJ2BTCPNI2RT4NOPJ' does not support file handles, falling back to xino=off.
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth87ede45) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth87ede45) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: veth87ede45: entered allmulticast mode
Mar 05 17:15:08 firewall-boi kernel: veth87ede45: entered promiscuous mode
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth87ede45) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth87ede45) entered forwarding state
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 1(veth29fe1ad) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 1(veth29fe1ad) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: veth29fe1ad: entered allmulticast mode
Mar 05 17:15:08 firewall-boi kernel: veth29fe1ad: entered promiscuous mode
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 1(veth29fe1ad) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 1(veth29fe1ad) entered forwarding state
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth0e1146b) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth0e1146b) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: veth0e1146b: entered allmulticast mode
Mar 05 17:15:08 firewall-boi kernel: veth0e1146b: entered promiscuous mode
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth0e1146b) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth0e1146b) entered forwarding state
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 2(veth0d2b6bd) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 2(veth0d2b6bd) entered disabled state
Mar 05 17:15:08 firewall-boi kernel: veth0d2b6bd: entered allmulticast mode
Mar 05 17:15:08 firewall-boi kernel: veth0d2b6bd: entered promiscuous mode
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 2(veth0d2b6bd) entered blocking state
Mar 05 17:15:08 firewall-boi kernel: br-03a083494198: port 2(veth0d2b6bd) entered forwarding state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth87ede45) entered disabled state
Mar 05 17:15:09 firewall-boi kernel: br-03a083494198: port 1(veth29fe1ad) entered disabled state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth0e1146b) entered disabled state
Mar 05 17:15:09 firewall-boi kernel: br-03a083494198: port 2(veth0d2b6bd) entered disabled state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(veth1bdcb4d) entered blocking state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(veth1bdcb4d) entered disabled state
Mar 05 17:15:09 firewall-boi kernel: veth1bdcb4d: entered allmulticast mode
Mar 05 17:15:09 firewall-boi kernel: veth1bdcb4d: entered promiscuous mode
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(veth1bdcb4d) entered blocking state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(veth1bdcb4d) entered forwarding state
Mar 05 17:15:09 firewall-boi kernel: eth0: renamed from veth0f75c78
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(veth1bdcb4d) entered disabled state
Mar 05 17:15:09 firewall-boi kernel: br-03a083494198: port 1(veth29fe1ad) entered blocking state
Mar 05 17:15:09 firewall-boi kernel: br-03a083494198: port 1(veth29fe1ad) entered forwarding state
Mar 05 17:15:09 firewall-boi kernel: eth0: renamed from veth046d279
Mar 05 17:15:09 firewall-boi kernel: eth0: renamed from veth3050dfb
Mar 05 17:15:09 firewall-boi kernel: eth0: renamed from veth75362a4
Mar 05 17:15:09 firewall-boi kernel: eth0: renamed from veth56ca1c1
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(veth1bdcb4d) entered blocking state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 3(veth1bdcb4d) entered forwarding state
Mar 05 17:15:09 firewall-boi kernel: br-03a083494198: port 2(veth0d2b6bd) entered blocking state
Mar 05 17:15:09 firewall-boi kernel: br-03a083494198: port 2(veth0d2b6bd) entered forwarding state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth87ede45) entered blocking state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 1(veth87ede45) entered forwarding state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth0e1146b) entered blocking state
Mar 05 17:15:09 firewall-boi kernel: br-e6ccdbd7d5c5: port 2(veth0e1146b) entered forwarding state
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 06DF8240EAF: from=<root@firewall-boi.local>, size=14030, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 07616240EB7: from=<root@firewall-boi.local>, size=27570, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 05E96240EAC: from=<root@firewall-boi.local>, size=27573, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 02EEE240F0C: from=<root@firewall-boi.local>, size=14031, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 0104C240EF0: from=<root@firewall-boi.local>, size=27572, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 01CA6240ED4: from=<root@firewall-boi.local>, size=27574, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 04758240F16: from=<root@firewall-boi.local>, size=27573, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 0375A240EC7: from=<root@firewall-boi.local>, size=14033, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 027DF240EEC: from=<root@firewall-boi.local>, size=27579, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 0567D240EE8: from=<root@firewall-boi.local>, size=14032, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 03EB5240CE5: from=<root@firewall-boi.local>, size=27577, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 06650240BB9: from=<root@firewall-boi.local>, size=14033, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 04ED7240E11: from=<root@firewall-boi.local>, size=27577, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: 000CB240ED7: from=<root@firewall-boi.local>, size=14033, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: F332A240EC5: from=<root@firewall-boi.local>, size=14031, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/qmgr[942]: F2679240C73: from=<root@firewall-boi.local>, size=14031, nrcpt=1 (queue active)
Mar 05 17:15:10 firewall-boi postfix/smtp[99064]: connect to gmail-smtp-in.l.google.com[2a00:1450:4010:c01::1b]:25: Network is unreachable
Mar 05 17:15:10 firewall-boi postfix/smtp[99062]: connect to gmail-smtp-in.l.google.com[2a00:1450:4010:c01::1b]:25: Network is unreachable
Mar 05 17:15:10 firewall-boi postfix/smtp[99066]: connect to gmail-smtp-in.l.google.com[2a00:1450:4010:c01::1b]:25: Network is unreachable
Mar 05 17:15:40 firewall-boi postfix/smtp[99063]: connect to gmail-smtp-in.l.google.com[64.233.161.26]:25: Connection timed out
Mar 05 17:15:40 firewall-boi postfix/smtp[99064]: connect to gmail-smtp-in.l.google.com[64.233.161.26]:25: Connection timed out
Mar 05 17:15:40 firewall-boi postfix/smtp[99063]: connect to gmail-smtp-in.l.google.com[2a00:1450:4010:c01::1b]:25: Network is unreachable
Mar 05 17:15:40 firewall-boi postfix/smtp[99066]: connect to gmail-smtp-in.l.google.com[64.233.161.26]:25: Connection timed out
Mar 05 17:15:40 firewall-boi postfix/smtp[99065]: connect to gmail-smtp-in.l.google.com[64.233.161.26]:25: Connection timed out
Mar 05 17:15:40 firewall-boi postfix/smtp[99062]: connect to gmail-smtp-in.l.google.com[64.233.161.26]:25: Connection timed out
Mar 05 17:15:40 firewall-boi postfix/smtp[99065]: connect to gmail-smtp-in.l.google.com[2a00:1450:4010:c01::1b]:25: Network is unreachable
Mar 05 17:15:40 firewall-boi postfix/smtp[99065]: connect to alt1.gmail-smtp-in.l.google.com[2404:6800:4008:c13::1b]:25: Network is unreachable

1709651740561.png
 
Last edited:
Hello, just thought I'd mention this as a similar thing has started to happen to me and I wondered whether they might be related.
 
reg_ed said:
Hello, just thought I'd mention this as a similar thing has started to happen to me and I wondered whether they might be related.
Click to expand...
Not sure if its related...

I tried to stress it while it was on proxmox. I ran jellyfin from 3 instances to 3 devices. And after few minutes it started doing this (https://streamable.com/20pzz1) and while it was doing this, proxmox was not responding, and every device that was connected to it via ethernet port was disconnected from network.

My test connection was this: TPLink Archer C7 router LAN > Protectli Vault (the bad device) and my PC. PC was not able to connect to any website. Felt like the ethernet was spammed too. And after i unplugged the bad seizure inducing device the PC was able to connect to google.

So does anyone know what could this mean? Could it be CPU dead? Or maybe the proxmox got corrupted and started doing this using the hw?..

Im going to try to reinstall it. Not sure if i should "BUY" another storage for this, becasue i used some kind no brand LEXAR nvme becasue it was cheaper option :(..



1709670017513.png
1709670035924.png
 
So I understand you have One stick of 32gb RAM. What type is it? I see from the picture image that its running at 2112mhz. This is odd to me. As I would assume you're using DDR4, and per specs of Intel i5-10210U, you can (should) be using one of the following:
Code: 
Memory Types:
DDR4-2666, LPDDR3-2133, LPDDR4-2933

If I were you, and you have another RAM module, try swapping it in, just to see result - eliminating RAM possibility.
 
gfngfn256 said:
So I understand you have One stick of 32gb RAM. What type is it? I see from the picture image that its running at 2112mhz. This is odd to me. As I would assume you're using DDR4, and per specs of Intel i5-10210U, you can (should) be using one of the following:
Code: 
Memory Types:
DDR4-2666, LPDDR3-2133, LPDDR4-2933

If I were you, and you have another RAM module, try swapping it in, just to see result - eliminating RAM possibility.
Click to expand...
The ram module was selected according to the manufacturer supported ram list. Protectli by default comes with this type of ram.

In my situation i have concluded that the problem was not with proxmox, unfortunately, but the problem is with hardware :(.

When the device is conneted to my local network, whole network, all devices, are getting DDOSED. Meaning when you open browser and try to access your router management webui, which should load very fast, it takes 40s to load. Speed test showed me speeds of 10mbps while im on a gigabit connection. Disconnecting the protectli device from network immediately improved my local network traffic and restored it to normal condition.

Maybe i was doing something wrong, but first few months everything was working good, only last weekend that it all went down the toilet :(..

Please tell me if i did something wrong, but the device has 6x eth ports, I bridged them all into vmbr0 so that they act as a switch of sorts. All was forking like this first few months no problems. Was bridging them made them short out or something?
 
Hello, I am having the same issues since the weekend with my Hetzner server were PVE 8.1.4 is installed with the latest updates. Or at least this is when I noticed it.
The server is randomly rebooting and I have no clue to why. The system has been running fine for nearly a year.
 
Last edited:
eeeeb said:
Hello, I am having the same issues since the weekend with my Hetzner server were PVE 8.1.4 is installed with the latest updates. Or at least this is when I noticed it.
The server is randomly rebooting and I have no clue to why. The system has been running fine for nearly a year.
Click to expand...
Connect a monitor and see if you see something on the screen during the reboot process.. This is how i noticed that the device hardware was failing and it didnt write error logs onto disk because it sort of (BLUESCREENED OF DEAD) with lots of other colors.
 
andzejsp said:
Connect a monitor and see if you see something on the screen during the reboot process.. This is how i noticed that the device hardware was failing and it didnt write error logs onto disk because it sort of (BLUESCREENED OF DEAD) with lots of other colors.
Click to expand...
I am not sure how I would do this as I wrote this is a Hetzner server. They have a remote KVM hardware, but then I would need to be logged into it and notice it. hmmm
 
eeeeb said:
I am not sure how I would do this as I wrote this is a Hetzner server. They have a remote KVM hardware, but then I would need to be logged into it and notice it. hmmm
Click to expand...
Oh, im not familiar with that heinz or what was it. If you have a posibility to connect to hardware and see the output that would be the best to be sure.

You too have no errors in the syslogs?

try to journalctl -f and try to catch some before it crashes...
 
andzejsp said:
Oh, im not familiar with that heinz or what was it. If you have a posibility to connect to hardware and see the output that would be the best to be sure.

You too have no errors in the syslogs?

try to journalctl -f and try to catch some before it crashes...
Click to expand...
There is nothing relevant in the logs before the sudden "-- Reboot --".
The memory looked fine during my test, perhaps it is the filesystem or the "disks".
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back