unexpected reboot

mspielberger

Renowned Member
Mar 4, 2013
20
1
63
heya!

I am running Proxmox on a Hetzner EX 4S with a Hardware Raid an BBU.
Right now there are only two VMs running, a "live system" (Debian 5) and a SVN server (Ubuntu 12).

I was quite shocked to see that the server has rebooted two days ago without my doing of it.

I really do not know why this happened and Hetzner did not notice any issues with their infrastructure...

The syslog does not really show anything, just the reboot (the reboot happened at 16:12)

Mar 1 15:12:06 proxmox rrdcached[1482]: flushing old valuesMar 1 15:12:06 proxmox rrdcached[1482]: rotating journals
Mar 1 15:12:06 proxmox rrdcached[1482]: started new journal /var/lib/rrdcached/journal//rrd.journal.1362147126.501469
Mar 1 15:12:06 proxmox rrdcached[1482]: removing old journal /var/lib/rrdcached/journal//rrd.journal.1362139926.501452
Mar 1 15:17:01 proxmox /USR/SBIN/CRON[1013521]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 1 16:12:33 uniserver kernel: imklog 4.6.4, log source = /proc/kmsg started.
Mar 1 16:12:33 uniserver rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="1710" x-info="http://www.rsyslog.com"] (re)start
Mar 1 16:12:33 uniserver kernel: Initializing cgroup subsys cpuset
Mar 1 16:12:33 uniserver kernel: Initializing cgroup subsys cpu
Mar 1 16:12:33 uniserver kernel: Linux version 2.6.32-17-pve (root@maui) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Wed Nov 28 07:15:55 CET 2012
Mar 1 16:12:33 uniserver kernel: Command line: BOOT_IMAGE=/vmlinuz-2.6.32-17-pve root=/dev/mapper/proxmox-root ro nomodeset
Mar 1 16:12:33 uniserver kernel: KERNEL supported cpus:
Mar 1 16:12:33 uniserver kernel: Intel GenuineIntel
Mar 1 16:12:33 uniserver kernel: AMD AuthenticAMD
Mar 1 16:12:33 uniserver kernel: Centaur CentaurHauls
Mar 1 16:12:33 uniserver kernel: Linux version 2.6.32-17-pve (root@maui) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Wed Nov 28 07:15:55 CET 2012
Mar 1 16:12:33 uniserver kernel: Command line: BOOT_IMAGE=/vmlinuz-2.6.32-17-pve root=/dev/mapper/proxmox-root ro nomodeset
Mar 1 16:12:33 uniserver kernel: KERNEL supported cpus:
Mar 1 16:12:33 uniserver kernel: Intel GenuineIntel
Mar 1 16:12:33 uniserver kernel: AMD AuthenticAMD
Mar 1 16:12:33 uniserver kernel: Centaur CentaurHauls
.....

also here is the output of pveversion

pve-manager: 2.3-12 (pve-manager/2.3/ad9c5c05)running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-17
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-6
ksm-control-daemon: 1.1-1


I am quite at a loss here and am not sure what exactly is wrong :(

Hetnzer offered me to do a hardware check, but this would result in a 10-14h downtime which I currently can not afford :(

The server is supposed to be brand new and I have ordered it just a few weeks ago.

I hope you can help me out!

Best
Malte
 
When i check my syslog it has
Code:
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^$

this value before unexpected reboot i dont found anything about that.
 
I have only debian, ubuntu and centos OS in my kvm and lxc devices and i dont know how can i check am i using zfs

You would have choosen that FS during Proxmox installation (we are talking about the Filesystem ZFS being used on proxmox during install instead e.g. ext4, with the swap residing on ZFS and out outside of it. )
 
You would have choosen that FS during Proxmox installation (we are talking about the Filesystem ZFS being used on proxmox during install instead e.g. ext4, with the swap residing on ZFS and out outside of it. )

my etc/fstab is

proc /proc proc defaults 0 0
/dev/md/0 none swap sw 0 0
/dev/md/1 /boot ext3 defaults 0 0
/dev/md/2 /backup ext4 defaults 0 0
/dev/md/3 / ext4 defaults 0 0
/dev/md/4 /var/lib/vz ext4 defaults 0 0

i dont know where can i check it
 
The link i posted is not your issue then. Maybe makes sense to open your own topic - unless it is the exact same issue as, based on the information provided in post #1
 
Heya

I am very sorry to not have updated my issue!
The reboots were caused by faulty RAM which Hetzner replaced promtly (after checking them)

So exactly what @dietmar was suggesting

Sorry to be of no help and not "closing" my topic
 
I just had one of my Proxmox 3.4 servers reboot in the middle of the night. Couldn't find anything in the syslog to indicate a problem, it had been up for over 200 days. Where is the best place to look for clues?
 

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!