[SOLVED] Server stürtz dauernd ab

nakooe89

New Member
Nov 23, 2019
8
0
1
30
Hi leute, bräuchte mal einen rat

ich habe mir vor kurzem einen root vom Hetzner geholt und habe dort Proxmox raufinstalliert.
nach ungefär 1-5 tagen ist der server einfach aus der hauptroot.

habe von hetzner einen stresstest machen lassen.
root scheint inordnung.

von support her liegt das problem nicht an ihnen

daher frage ich euch weil ich nixx anderes installiert habe.

ich habe derzeit folgene hardware



Intel Core i7-3770
7x HDD SATA 4,0 TB Enterprise
4x RAM 8192 MB DDR3

derzeit installierte kernel
5.0.21-3-pve


Im syslog steht rein garnixx über einen shutdown oder störung.
aber der support meint es könnte nur daran liegen. wenn es wirklich daran liegen könnte würde ich einen anderen kernel installieren.


alternativ habe ich mir überlegt einen anderen server zu holen weil den ich aktuell bei der serverbörse mir geschnappt habe.

CPU intel® Xeon® E3-1270 v3 Quad-Core Haswell

Virtualisierung (Intel VT) ja

Arbeitsspeicher 32 GB ECC DDR3 RAM

HDD
4 x 10 TB
SATA 7200 rpm
Software-RAID Level optional


könnt ihr bitte helfen ? oder welche lösungsansätze ich habt

mit freundlichen grüßen nakooe

 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
13,890
459
103
Ob die hardware passt oder nicht, kann ich von hier nicht beurteilen, aber Hetzner verwendet hier Desktop/PC Komponenten für Serverbetrieb. Nicht wirklich eine sehr gute Wahl für ein stabiles System.

Probier noch den neuesten 5.3 Kernel, damit schliessen wir zumindest den 5.0 kernel als Ursache aus.

> apt-get install pve-kernel-5.3

Auch logs anschauen, ev. sieht man dort einen Hinweis.
 

nakooe89

New Member
Nov 23, 2019
8
0
1
30
also installiert hat er es einfach aber mal sehen ob der wieder aus geht! danke erst mal für dein hilfe
 

nakooe89

New Member
Nov 23, 2019
8
0
1
30
Nov 23 23:49:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:49:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:49:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:50:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:50:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:50:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:50:10 Proxmox-VE smartd[678]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 193 to 200
Nov 23 23:50:11 Proxmox-VE smartd[678]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 193 to 200
Nov 23 23:51:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:51:00 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:51:00 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:52:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:52:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:52:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:53:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:53:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:53:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:54:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:54:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:54:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:55:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:55:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:55:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:56:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:56:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:56:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:57:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:57:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:57:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:58:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:58:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:58:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 23 23:59:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 23 23:59:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 23 23:59:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 24 00:00:00 Proxmox-VE systemd[1]: Starting Proxmox VE replication runner...
Nov 24 00:00:00 Proxmox-VE systemd[1]: Starting Daily man-db regeneration...
Nov 24 00:00:00 Proxmox-VE systemd[1]: Starting Rotate log files...
Nov 24 00:00:01 Proxmox-VE systemd[1]: pvesr.service: Succeeded.
Nov 24 00:00:01 Proxmox-VE systemd[1]: Started Proxmox VE replication runner.
Nov 24 00:00:03 Proxmox-VE systemd[1]: Stopping LSB: Starts ProFTPD daemon...
Nov 24 00:00:04 Proxmox-VE proftpd[26361]: Stopping ftp server: proftpd.
Nov 24 00:00:04 Proxmox-VE systemd[1]: proftpd.service: Succeeded.
Nov 24 00:00:04 Proxmox-VE systemd[1]: Stopped LSB: Starts ProFTPD daemon.
Nov 24 00:00:04 Proxmox-VE systemd[1]: Starting LSB: Starts ProFTPD daemon...
Nov 24 00:00:05 Proxmox-VE proftpd[26369]: Starting ftp server: proftpd2019-11-24 00:00:05,347 Proxmox-VE proftpd[26376]: processing configuration directory '/etc/proftpd/conf.d/'
Nov 24 00:00:05 Proxmox-VE proftpd[26369]: .
Nov 24 00:00:05 Proxmox-VE systemd[1]: Started LSB: Starts ProFTPD daemon.
Nov 24 00:00:05 Proxmox-VE systemd[1]: Reloading PVE API Proxy Server.
Nov 24 00:00:06 Proxmox-VE pveproxy[26382]: send HUP to 1304
Nov 24 00:00:06 Proxmox-VE systemd[1]: Reloaded PVE API Proxy Server.
Nov 24 00:00:06 Proxmox-VE systemd[1]: Reloading PVE SPICE Proxy Server.
Nov 24 00:00:08 Proxmox-VE pveproxy[1304]: received signal HUP
Nov 24 00:00:08 Proxmox-VE spiceproxy[26384]: send HUP to 1309
Nov 24 00:00:08 Proxmox-VE systemd[1]: Reloaded PVE SPICE Proxy Server.
Nov 24 00:00:08 Proxmox-VE pveproxy[1304]: server closing
Nov 24 00:00:08 Proxmox-VE pveproxy[1304]: server shutdown (restart)
Nov 24 00:00:08 Proxmox-VE pvefw-logger[660]: received terminate request (signal)
Nov 24 00:00:08 Proxmox-VE pvefw-logger[660]: stopping pvefw logger
Nov 24 00:00:08 Proxmox-VE systemd[1]: Stopping Proxmox VE firewall logger...
Nov 24 00:00:09 Proxmox-VE spiceproxy[1309]: received signal HUP
Nov 24 00:00:09 Proxmox-VE spiceproxy[1309]: server closing
Nov 24 00:00:09 Proxmox-VE spiceproxy[1309]: server shutdown (restart)
Nov 24 00:00:09 Proxmox-VE systemd[1]: pvefw-logger.service: Succeeded.
Nov 24 00:00:09 Proxmox-VE systemd[1]: Stopped Proxmox VE firewall logger.
Nov 24 00:00:09 Proxmox-VE systemd[1]: Starting Proxmox VE firewall logger...
Nov 24 00:00:09 Proxmox-VE pvefw-logger[26396]: starting pvefw logger
Nov 24 00:00:09 Proxmox-VE systemd[1]: Started Proxmox VE firewall logger.
Nov 24 00:00:09 Proxmox-VE spiceproxy[1309]: restarting server
Nov 24 00:00:09 Proxmox-VE spiceproxy[1309]: starting 1 worker(s)
Nov 24 00:00:09 Proxmox-VE spiceproxy[1309]: worker 26404 started
Nov 24 00:00:09 Proxmox-VE systemd[1]: man-db.service: Succeeded.
Nov 24 00:00:09 Proxmox-VE systemd[1]: Started Daily man-db regeneration.





ist ganz komisch hat wer ne idee ????
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!