Hi David,
just spotted this post from a couple of weeks ago -- I have the same
problem (Gluster volume not healing) since the upgrade from 7.x to 8.4.
Same exact errors on glustershd.log -- and same errors if I try to heal
manually.
Typically I can get the volume healed by killing the specific
I did have my /etc/hosts setup on all 3 of the oVirt Hosts in the format you
described, with the exception of the trailing "host1" and "host2". I only had
the FQDN in there.
I had an outage of almost an hour this morning that may or may not be related
to this. An "ETL Service" started, at
A/ & PTR records are pretty important.As long as you setup your /etc/hosts
jn the format like this you will be OK:
10.10.10.10 host1.anysubdomain.domain host110.10.10.11
host2.anysubdomain.domain host2
Usually the hostname is defined for each peer in the /var/lib/glusterd/peers.
Can you
As part of my troubleshooting earlier this morning, I gracefully shut down the
ovirt-engine so that it would come up on a different host (can't remember if I
mentioned that or not).
I just verified forward DNS on all 3 of the hosts.
All 3 resolve each other just fine, and are able to ping each
Hi David,
let's start with the DNS.Check that both nodes resolve each other (both A/
& PTR records).
If you set entries in /etc/hosts, check them out.
Also , check the output of 'hostname -s' & 'hostname -f' on both hosts.
Best Regards,Strahil
5 matches
Mail list logo
