a stop job is running for PVE local....

[Slavka]

Hi

after installation, the server did not restart and freezes




after configuration
root@Node-3:/etc/default# cat pve-ha-manager
# select watchdog module (default is softdog)
WATCHDOG_MODULE=ipmi_watchdog


root@Node-3:/etc/default# cat grub

GRUB_CMDLINE_LINUX="reboot=bios" ( or reboot=acpi)

and

root@Node-3:/etc/modules-load.d# cat ipmi_watchdog.conf
ipmi_watchdog



When you try to shut down the server or restart, it waits on 'a stop job is running for PVE local HA Resource manager daemon (xx/ no limit)'

after 20 minutes, a message about forced reboot appears

after a few minutes, the server reboots

several times the reboot was as follows


there are no virtual machines on this server



Hardware :
Lenovo ThinkSystem SN550
network : Flex System CN4054S 4-port 10Gb Virtual Fabric Adapter


Software
root@Node-3:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)
pve-manager: 6.1-5 (running version: 6.1-5/9bf06119)
pve-kernel-5.3: 6.1-1
pve-kernel-helper: 6.1-1
pve-kernel-5.3.13-1-pve: 5.3.13-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve2
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-10
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-2
pve-cluster: 6.1-3
pve-container: 3.0-16
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-4
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
root@Node-3:~#



I ask for help in configuring the server

 

[fiona]

Hi,
are you using CephFS? There was an issue with the ordering in networking.service, that got triggered for certain setups, see this thread. A fix is available in ifupdown2 (2.0.1-1+pve3).

 

[Slavka]

Hi,
are you using CephFS? There was an issue with the ordering in networking.service, that got triggered for certain setups, see this thread. A fix is available in ifupdown2 (2.0.1-1+pve3).

thanks for the answer
No, i use lvm
Ceph is not installed

root@Node-3:/# apt show ifupdown2
Package: ifupdown2
Version: 2.0.1-1+pve3
Priority: optional
Section: admin

What else can you try?




Ps : I apologize for possible errors, I copy from google translate

 

[Slavka]

Maybe we should install CephFS ?

 

[fiona]

Maybe we should install CephFS ?

That's not very likely to help, since your issue is probably not the same as in the thread I linked to and that only occurred when CephFS was installed.

 

[fiona]

So the problem only started after you configured the IPMI watchdog?
Please try using the following line in your /etc/modprobe.d/ipmi_watchdog.conf so that it knows which action to take:

options ipmi_watchdog action=power_cycle panic_wdt_timeout=10

Afterwards reload the module.