Hi, I have one problematic node, and identified a culprit why vdsmd service can't start: -- The unit libvirtd-tls.socket has entered the 'failed' state with result 'service-start-limit-hit'. Aug 13 15:00:45 node14.starlett.lv systemd[1]: Closed Libvirt TLS IP socket. -- Subject: Unit libvirtd-tls.socket has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support Node was installed on clean CentOS Stream from oVirt Web (not oVirt node disk image), and was working fine until recent problem with certificates. Can't reinstall/reconfigure node from oVirt Web since it is marked as non-responsive. How to fix this? Thanks in advance for any help. --------------------- [root@node14 vdsm]# cat /etc/centos-release CentOS Stream release 8 [root@node14 vdsm]# rpm -qa | grep vdsm vdsm-api-4.40.100.2-1.el8.noarch vdsm-hook-openstacknet-4.40.100.2-1.el8.noarch vdsm-client-4.40.100.2-1.el8.noarch vdsm-network-4.40.100.2-1.el8.x86_64 vdsm-hook-vhostmd-4.40.100.2-1.el8.noarch vdsm-4.40.100.2-1.el8.x86_64 vdsm-http-4.40.100.2-1.el8.noarch vdsm-common-4.40.100.2-1.el8.noarch vdsm-hook-fcoe-4.40.100.2-1.el8.noarch vdsm-python-4.40.100.2-1.el8.noarch vdsm-jsonrpc-4.40.100.2-1.el8.noarch vdsm-hook-ethtool-options-4.40.100.2-1.el8.noarch vdsm-yajsonrpc-4.40.100.2-1.el8.noarch [root@node14 vdsm]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts [root@node14 vdsm]# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● libvirtd.service loaded failed failed Virtualization daemon ● libvirtd-admin.socket loaded failed failed Libvirt admin socket ● libvirtd-ro.socket loaded failed failed Libvirt local read-only socket ● libvirtd-tls.socket loaded failed failed Libvirt TLS IP socket ● libvirtd.socket loaded failed failed Libvirt local socket