[SOLVED] PVE 6.3-2 The server automatically restarts at 11 o'clock every Saturday

left3721

New Member
Jan 23, 2021
8
0
1
41
Use 2 physical hosts, 1 doll host, and 3 to form a cluster. Use the HA function, and the physical host will automatically restart every Saturday at around 11 am every Saturday.

The motherboard motherboard uses Supermicro X11DPL-I cpu silver 4214 memory 128G ISCSI shared storage made by DELL server.

There is no problem from Monday to Friday, the X11DPL-I motherboard has closed watchdog and CPU energy saving
 
Bash:
 pvecm status
Cluster information
-------------------
Name:             Tailin
Config Version:   5
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Sat Jan 23 14:34:31 2021
Quorum provider:  corosync_votequorum
Nodes:            3
Node ID:          0x00000001
Ring ID:          1.518
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   3
Highest expected: 3
Total votes:      3
Quorum:           2 
Flags:            Quorate

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 10.0.50.200 (local)
0x00000002          1 10.0.50.201
0x00000003          1 10.0.50.202

Bash:
pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.78-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-2
pve-kernel-helper: 6.3-2
pve-kernel-5.4.78-1-pve: 5.4.78-1
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-1
libpve-common-perl: 6.3-1
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1
 
Last edited:
Are the switches rebooted at that particular time?
Are backups running?
What happens at that point in time?
 
Is there cleaning personal working there?
I had it in the past that the pulled power cables to attach / connect their gear :rolleyes:

Was asking for backup because I have read that someone had issues withcorosync and increased network latency caused by backup.
 
Well then the question is: what happens in your infrastructure at that specific point in time?
 
The pve version is upgraded to 6.3-3
Print these logs on the monitor screen
[ 9012.290894] sd 11:0:0:0: alua: supports implicit TPGS [ 9012.291820] sd 11:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 0 rel port 2 [ 9012.301257] sd 11:0:0:0: alua: port group 00 state A preferred supports tolusNA [ 9012.301267] sd 12:0:0:0: alua: supports implicit TPGS [ 9012.302634] sd 12:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 1 rel port 5 [ 9012.312181] sd 13:0:0:0: alua: supports implicit TPGS [ 9012.312835] sd 13:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 0 rel port 1 [ 9012.313211] sd 12:0:0:0: alua: port group 01 state N non-preferred supports tolusNA [ 9012.321497] sd 14:0:0:0: alua: supports implicit TPGS [ 9012.322155] sd 14:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 1 rel port 6 [ 9012.325218] sd 13:0:0:0: alua: port group 00 state A preferred supports tolusNA [ 9012.340078] sd 14:0:0:0: alua: port group 01 state N non-preferred supports tolusNA [ 9031.532516] sd 11:0:0:0: alua: supports implicit TPGS [ 9031.534679] sd 11:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 0 rel port 2 [ 9031.543552] sd 12:0:0:0: alua: supports implicit TPGS [ 9031.544228] sd 12:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 1 rel port 5 [ 9031.548971] sd 11:0:0:0: alua: port group 00 state A preferred supports tolusNA [ 9031.553820] sd 13:0:0:0: alua: supports implicit TPGS [ 9031.554477] sd 13:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 0 rel port 1 [ 9031.560976] sd 12:0:0:0: alua: port group 01 state N non-preferred supports tolusNA [ 9031.563529] sd 14:0:0:0: alua: supports implicit TPGS [ 9031.564188] sd 14:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 1 rel port 6 [ 9031.564970] sd 13:0:0:0: alua: port group 00 state A preferred supports tolusNA [ 9031.587085] sd 14:0:0:0: alua: port group 01 state N non-preferred supports tolusNA [ 9051.915124] sd 11:0:0:0: alua: supports implicit TPGS [ 9051.916542] sd 11:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 0 rel port 2 [ 9051.925404] sd 12:0:0:0: alua: supports implicit TPGS [ 9051.926087] sd 12:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 1 rel port 5 [ 9051.928754] sd 11:0:0:0: alua: port group 00 state A preferred supports tolusNA [ 9051.935605] sd 13:0:0:0: alua: supports implicit TPGS [ 9051.936264] sd 13:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 0 rel port 1 [ 9051.936704] sd 12:0:0:0: alua: port group 01 state N non-preferred supports tolusNA [ 9051.944886] sd 14:0:0:0: alua: supports implicit TPGS [ 9051.945538] sd 14:0:0:0: alua: device naa.600c0ff00050786231bab35f01000000 port group 1 rel port 6 [ 9051.948759] sd 13:0:0:0: alua: port group 00 state A preferred supports tolusNA [ 9051.956710] sd 14:0:0:0: alua: port group 01 state N non-preferred supports tolusNA

I don't know what will happen
 
Last edited:
修改参数后,周六和周日没有重新启动
GRUB_CMDLINE_LINUX_DEFAULT =“ consoleblank = 0 intel_idle.max_cstate = 1” [/ ICODE]