<div dir="ltr"><div>There are probably DNS entries or <span style="font-family:monospace,monospace">/etc/hosts</span> entries with the public IP Addresses that the host names (gluster1, gluster2, gluster3) are getting resolved to.</div><div><span style="font-family:monospace,monospace">/etc/resolv.conf</span> would tell which is the default domain searched for the node names and the DNS servers which respond to the queries.<br></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 5, 2019 at 12:14 PM Hu Bert <<a href="mailto:revirii@googlemail.com">revirii@googlemail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Good morning,<br>
<br>
i have a replicate 3 setup with 2 volumes, running on version 5.3 on<br>
debian stretch. This morning i upgraded one server to version 5.4 and<br>
rebooted the machine; after the restart i noticed that:<br>
<br>
- no brick process is running<br>
- gluster volume status only shows the server itself:<br>
gluster volume status workdata<br>
Status of volume: workdata<br>
Gluster process TCP Port RDMA Port Online Pid<br>
------------------------------------------------------------------------------<br>
Brick gluster1:/gluster/md4/workdata N/A N/A N N/A<br>
NFS Server on localhost N/A N/A N N/A<br>
<br>
- gluster peer status on the server<br>
gluster peer status<br>
Number of Peers: 2<br>
<br>
Hostname: gluster3<br>
Uuid: c7b4a448-ca6a-4051-877f-788f9ee9bc4a<br>
State: Peer Rejected (Connected)<br>
<br>
Hostname: gluster2<br>
Uuid: 162fea82-406a-4f51-81a3-e90235d8da27<br>
State: Peer Rejected (Connected)<br>
<br>
- gluster peer status on the other 2 servers:<br>
gluster peer status<br>
Number of Peers: 2<br>
<br>
Hostname: gluster1<br>
Uuid: 9a360776-7b58-49ae-831e-a0ce4e4afbef<br>
State: Peer Rejected (Connected)<br>
<br>
Hostname: gluster3<br>
Uuid: c7b4a448-ca6a-4051-877f-788f9ee9bc4a<br>
State: Peer in Cluster (Connected)<br>
<br>
I noticed that, in the brick logs, i see that the public IP is used<br>
instead of the LAN IP. brick logs from one of the volumes:<br>
<br>
rejected node: <a href="https://pastebin.com/qkpj10Sd" rel="noreferrer" target="_blank">https://pastebin.com/qkpj10Sd</a><br>
connected nodes: <a href="https://pastebin.com/8SxVVYFV" rel="noreferrer" target="_blank">https://pastebin.com/8SxVVYFV</a><br>
<br>
Why is the public IP suddenly used instead of the LAN IP? Killing all<br>
gluster processes and rebooting (again) didn't help.<br>
<br>
<br>
Thx,<br>
Hubert<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Milind<br><br></div></div></div></div>