
What is the content of '/rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/' ? Usually when you restart the broker & agent, they will check if the links exist and are recreated again. You can try to set the host into maintenance (local), then stop ovirt-ha-agent & ovirt-ha-broker . Then start the broker and after it -> the agent. You can increase the log level via : /etc/ovirt-hosted-engine-ha/agent-log.conf /etc/ovirt-hosted-engine-ha/broker-log.conf (Don't forget to restart the service). Best Regards, Strahil NikolovOn Dec 7, 2019 17:22, Stefan Wolf <shb256@gmail.com> wrote:
and here is the broker.log
MainThread::INFO::2019-12-07 15:20:03,563::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started MainThread::INFO::2019-12-07 15:20:03,564::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors MainThread::INFO::2019-12-07 15:20:03,564::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free MainThread::INFO::2019-12-07 15:20:03,565::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network MainThread::INFO::2019-12-07 15:20:03,566::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free MainThread::INFO::2019-12-07 15:20:03,566::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health MainThread::INFO::2019-12-07 15:20:03,567::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load MainThread::INFO::2019-12-07 15:20:03,567::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain MainThread::INFO::2019-12-07 15:20:03,568::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge MainThread::INFO::2019-12-07 15:20:03,569::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load MainThread::INFO::2019-12-07 15:20:03,569::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network MainThread::INFO::2019-12-07 15:20:03,574::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine MainThread::INFO::2019-12-07 15:20:03,575::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine MainThread::INFO::2019-12-07 15:20:03,576::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge MainThread::INFO::2019-12-07 15:20:03,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health MainThread::INFO::2019-12-07 15:20:03,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain MainThread::INFO::2019-12-07 15:20:03,577::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors MainThread::INFO::2019-12-07 15:20:03,651::storage_backends::373::ovirt_hosted_engine_ha.lib.storage_backends::(connect) Connecting the storage MainThread::INFO::2019-12-07 15:20:03,652::storage_server::349::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Connecting storage server MainThread::INFO::2019-12-07 15:20:03,716::storage_server::356::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Connecting storage server MainThread::INFO::2019-12-07 15:20:03,748::storage_server::413::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Refreshing the storage domain MainThread::WARNING::2019-12-07 15:20:06,985::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/hosted-engine.lockspace'
maybe it helps
bye shb _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KECDUEVCHP3OSU...

the contet is [root@kvm380 ~]# ls /rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/ -lha ls: Zugriff auf /rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/hosted-engine.lockspace nicht möglich: Der Socket ist nicht verbunden ls: Zugriff auf /rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/hosted-engine.metadata nicht möglich: Der Socket ist nicht verbunden insgesamt 512 drwxr-xr-x. 2 vdsm kvm 67 20. Nov 09:20 . drwxr-xr-x. 6 vdsm kvm 64 7. Dez 12:08 .. l?????????? ? ? ? ? ? hosted-engine.lockspace l?????????? ? ? ? ? ? hosted-engine.metadata I ve already tryed to stop and start the broker again, ovirt-ha-agant will not start. And as wrote i ve done a complete reinstall of the ovirt host bye stefan

Hi Stefan, it seems that there is some conflict on brick level (that's why it is ?????????).Just move the files in the brick to another location and then restart the broker and agent: [root@kvm380 ~]# mkdir /root/broken_stuff; mv /gluster_bricks/engine/engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/* /root/broken_stuff/ Then repeat for the rest of the gluster bricks. Next, list the contents from your post again and it should be empty - > then you can stop and then start ovirt-ha-broker and ovirt-ha-agent:hosted-engine --set-maintenance --mode=globalsystemctl stop ovirt-ha-broker ovirt-ha-agentsystemctl start ovirt-ha-broker; systemctl start ovirt-ha-agent Next observe what is going on: tail -f /var/log/ovirt-hosted-engine-ha/{agent,broker}.log After several minutes the links will be created and the agent will know what to do with the engine. Don't forget to remove the maintenance , once you verify that all hosts have running ovirt-ha-broker & ovirt-ha-agent. Best Regards,Strahil Nikolov В събота, 7 декември 2019 г., 22:55:14 ч. Гринуич+2, Stefan Wolf <shb256@gmail.com> написа: the contet is [root@kvm380 ~]# ls /rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/ -lha ls: Zugriff auf /rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/hosted-engine.lockspace nicht möglich: Der Socket ist nicht verbunden ls: Zugriff auf /rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/hosted-engine.metadata nicht möglich: Der Socket ist nicht verbunden insgesamt 512 drwxr-xr-x. 2 vdsm kvm 67 20. Nov 09:20 . drwxr-xr-x. 6 vdsm kvm 64 7. Dez 12:08 .. l?????????? ? ? ? ? ? hosted-engine.lockspace l?????????? ? ? ? ? ? hosted-engine.metadata I ve already tryed to stop and start the broker again, ovirt-ha-agant will not start. And as wrote i ve done a complete reinstall of the ovirt host bye stefan _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HCM6XS7FBSDQLX...

you are right, thank you now it is up and running again [root@kvm380 ~]# ls /rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern\:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/ -lha insgesamt 0 drwxr-xr-x. 2 vdsm kvm 67 1. Jan 1970 . drwxr-xr-x. 6 vdsm kvm 64 7. Dez 12:08 .. lrwxrwxrwx. 1 vdsm kvm 132 8. Dez 06:49 hosted-engine.lockspace -> /var/run/vdsm/storage/36663740-576a-4498-b28e-0a402628c6a7/de9b53fb-6c86-4036-9f1c-1f08d1828e2f/d41a5061-94b8-4e0d-84ec-8af0c547955a lrwxrwxrwx. 1 vdsm kvm 132 8. Dez 06:49 hosted-engine.metadata -> /var/run/vdsm/storage/36663740-576a-4498-b28e-0a402628c6a7/aec89d8d-0c7c-42b8-8889-1713d7e8a667/39ec2ecd-57b5-4424-8666-d7b673b1e8b6
participants (3)
-
Stefan Wolf
-
Strahil
-
Strahil Nikolov