On Sun, Jul 2, 2017 at 5:38 AM, Mike DePaulo <mikedep...@gmail.com> wrote:

> Hi everyone,
>
> I have ovirt 4.1.1/4.1.2 running on 3 hosts with a gluster hosted engine.
>
> I was working on setting up a network for gluster storage and
> migration. The addresses for it will be 10.0.20.x, rather than
> 192.168.1.x for the management network.  However, I switched gluster
> storage and migration back over to the management network.
>
> I updated and rebooted one of my hosts (death-star, 10.0.20.52) and on
> reboot, the glusterd service would start, but wouldn't seem to work.
> The engine webgui reported that its bricks were down, and commands
> like this would fail:
>
> [root@death-star glusterfs]# gluster pool list
> pool list: failed
> [root@death-star glusterfs]# gluster peer status
> peer status: failed
>
> Upon further investigation, I had under /var/lib/glusterd/peers/ the 2
> existing UUID files, plus a new 3rd one:
> [root@death-star peers]# cat 10.0.20.53
> uuid=00000000-0000-0000-0000-000000000000
> state=0
> hostname1=10.0.20.53
>

[Adding gluster-users]

How did you add this peer "10.0.20.53"? Is this another interface for an
existing peer?


> I moved that file out of there, restarted glusterd, and now gluster is
> working again.
>
> I am guessing that this is a bug. Let me know if I should attach other
> log files; I am not sure which ones.
>
> And yes, 10.0.20.53 is the IP of one of the other hosts.
>
> -Mike
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to