I've always done a reverse peer probe from another node in the pool. Make
sure you're hosts file or DNS is working correctly and then peer probe the
opposite node.
you can actually have gluster recognise other names that each node is known
as such as IP, fqdn, shortname.
I wouldn't edit the peer file if I were you. You can play nasty tricks on
gluster index by editing or adding in peer files while gluster is running.
On Mar 15, 2017 6:55 AM, "Gandalf Corvotempesta" <
gandalf.corvotempesta at gmail.com> wrote:
> I can confirm this
> Any solution?
>
> Il 14 mar 2017 8:11 PM, "Sergei Gerasenko" <gerases at
gmail.com> ha scritto:
>
>> Hi everybody,
>>
>> Easy question: the output of *gluster peer status* on some of the hosts
>> in the cluster has the hostname for all but one member of the cluster,
>> which is listed by its ip. Is there an easy way to fix it? I know the
>> information is coming from the peer files and I could edit the peer
files
>> directly, but can this be done through cli tools?
>>
>> Thanks,
>> Sergei
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170315/d9dc18f0/attachment.html>