Hu Bert
2019-Mar-05 06:43 UTC
[Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP
Good morning, i have a replicate 3 setup with 2 volumes, running on version 5.3 on debian stretch. This morning i upgraded one server to version 5.4 and rebooted the machine; after the restart i noticed that: - no brick process is running - gluster volume status only shows the server itself: gluster volume status workdata Status of volume: workdata Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gluster1:/gluster/md4/workdata N/A N/A N N/A NFS Server on localhost N/A N/A N N/A - gluster peer status on the server gluster peer status Number of Peers: 2 Hostname: gluster3 Uuid: c7b4a448-ca6a-4051-877f-788f9ee9bc4a State: Peer Rejected (Connected) Hostname: gluster2 Uuid: 162fea82-406a-4f51-81a3-e90235d8da27 State: Peer Rejected (Connected) - gluster peer status on the other 2 servers: gluster peer status Number of Peers: 2 Hostname: gluster1 Uuid: 9a360776-7b58-49ae-831e-a0ce4e4afbef State: Peer Rejected (Connected) Hostname: gluster3 Uuid: c7b4a448-ca6a-4051-877f-788f9ee9bc4a State: Peer in Cluster (Connected) I noticed that, in the brick logs, i see that the public IP is used instead of the LAN IP. brick logs from one of the volumes: rejected node: https://pastebin.com/qkpj10Sd connected nodes: https://pastebin.com/8SxVVYFV Why is the public IP suddenly used instead of the LAN IP? Killing all gluster processes and rebooting (again) didn't help. Thx, Hubert
Milind Changire
2019-Mar-05 06:58 UTC
[Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP
There are probably DNS entries or /etc/hosts entries with the public IP Addresses that the host names (gluster1, gluster2, gluster3) are getting resolved to. /etc/resolv.conf would tell which is the default domain searched for the node names and the DNS servers which respond to the queries. On Tue, Mar 5, 2019 at 12:14 PM Hu Bert <revirii at googlemail.com> wrote:> Good morning, > > i have a replicate 3 setup with 2 volumes, running on version 5.3 on > debian stretch. This morning i upgraded one server to version 5.4 and > rebooted the machine; after the restart i noticed that: > > - no brick process is running > - gluster volume status only shows the server itself: > gluster volume status workdata > Status of volume: workdata > Gluster process TCP Port RDMA Port Online > Pid > > ------------------------------------------------------------------------------ > Brick gluster1:/gluster/md4/workdata N/A N/A N > N/A > NFS Server on localhost N/A N/A N > N/A > > - gluster peer status on the server > gluster peer status > Number of Peers: 2 > > Hostname: gluster3 > Uuid: c7b4a448-ca6a-4051-877f-788f9ee9bc4a > State: Peer Rejected (Connected) > > Hostname: gluster2 > Uuid: 162fea82-406a-4f51-81a3-e90235d8da27 > State: Peer Rejected (Connected) > > - gluster peer status on the other 2 servers: > gluster peer status > Number of Peers: 2 > > Hostname: gluster1 > Uuid: 9a360776-7b58-49ae-831e-a0ce4e4afbef > State: Peer Rejected (Connected) > > Hostname: gluster3 > Uuid: c7b4a448-ca6a-4051-877f-788f9ee9bc4a > State: Peer in Cluster (Connected) > > I noticed that, in the brick logs, i see that the public IP is used > instead of the LAN IP. brick logs from one of the volumes: > > rejected node: https://pastebin.com/qkpj10Sd > connected nodes: https://pastebin.com/8SxVVYFV > > Why is the public IP suddenly used instead of the LAN IP? Killing all > gluster processes and rebooting (again) didn't help. > > > Thx, > Hubert > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users >-- Milind -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190305/5638f95c/attachment.html>