Proxmox shutdown randomly
- Thread starter bit2gb
- Start date
What is the output of the following commands? It would be great if you could post it using the function Insert->Code (that is the three dots in the tool bar) of our forum.
Code:
pveversion -v
cat /etc/pve/corosync.conf
systemctl status pvedaemon
Code:
root@d3:~# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-25-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-13
pve-kernel-4.15.18-25-pve: 4.15.18-53
pve-kernel-4.15.18-12-pve: 4.15.18-36
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-41
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-55
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
Code:
root@d3:~# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: d1
nodeid: 1
quorum_votes: 1
ring0_addr: x.x.x.x
}
node {
name: d3
nodeid: 3
quorum_votes: 1
ring0_addr: x.x.x.x
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: HZone
config_version: 6
interface {
bindnetaddr: x.x.x.x
ringnumber: 0
}
ip_version: ipv4
secauth: on
version: 2
}
Code:
systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset
Active: active (running) since Wed 2020-02-12 21:06:52 EET; 13h ago
Process: 1942 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCES
Main PID: 1969 (pvedaemon)
Tasks: 15 (limit: 4915)
Memory: 42.3G
CPU: 31min 59.596s
CGroup: /system.slice/pvedaemon.service
├─ 1969 pvedaemon
├─ 2498 task UPID:d3:000009C2:004C0FF1:5E450F3C:qmigrate:6003:root@pa
├─ 2507 /bin/bash -c set -o pipefail && pvesm export local:6003/vm-60
├─ 2508 /usr/bin/perl /usr/sbin/pvesm export local:6003/vm-6003-disk-
├─ 2509 /usr/bin/ssh -e none -o BatchMode=yes -o HostKeyAlias=d1 root
├─ 2513 dd if=/var/lib/vz/images/6003/vm-6003-disk-0.qcow2 bs=4k
├─ 2705 pvedaemon worker
├─ 3475 task UPID:d3:00000D93:004C2562:5E450F72:vncshell::root@pam:
├─ 3476 /usr/bin/perl /usr/bin/termproxy 5901 --path /nodes/d3 --perm
├─ 3592 /bin/login -fDid you modify anything else except masking the ip addresses in the corosync configuration file? Your screenshots indicates that there is a syntax error somewhere in it.
Could you also post the following?
Still, the shutdown is a different problem. You can start by investigating all the log files that a normal Debian writes for shutdowns.
Could you also post the following?
Code:
pvecm status
corosync -t
diff /etc/corosync/corosync.conf /etc/pve/corosync.conf && echo okStill, the shutdown is a different problem. You can start by investigating all the log files that a normal Debian writes for shutdowns.