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 ..
l
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-0a402628c6a
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.lo
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 (loc
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_subm
5 matches
Mail list logo