Re: Cannot connect to the cluster after customizing the port

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi: 
1. The ports of both nodes are changed to 24017
2. After installation, change the port and start directly (non-restart)
3. I tried, but the nodes in the pool cannot connect after restarting. The log shows an attempt to connect to the default port

Steps(both node1 and node2)
   # yum install glusterfs glusterfs-server glusterfs-fuse
   # vim /etc/glusterfs/glusterd.vol
....
option transport.socket.listen-port 24017
....
# systemctl start glusterd

# gluster peer probe node2
Probe returned with Transport endpoint is not connected

After changing the port back to 24007 and restarting, the connection is normal







在 2020-12-06 19:27:01,"Strahil Nikolov" <hunter86_bg@xxxxxxxxx> 写道: >Did you change the port on both nodes ? >Did you restart glusterd on both nodes (the one you do peer probe and the other one that is being probed) ? > >Have you tried to first peer probe and then change the port on all nodes in the pool ? > > >Best Regards, >Strahil Nikolov > > > > > >В петък, 4 декември 2020 г., 12:18:42 Гринуич+2, sky <x_hsky@xxxxxxx> написа: > > > > > >linux version: cenots 7.5  >gluster verison: 7.5.1 >/etc/glusterfs/glusterd.vol:  >volume management >    type mgmt/glusterd >    option working-directory /var/lib/glusterd >    option transport-type socket,rdma >    option transport.socket.keepalive-time 10 >    option transport.socket.keepalive-interval 2 >    option transport.socket.read-fail-log off >    option transport.socket.listen-port 24017 >    option transport.rdma.listen-port 24008 >    option ping-timeout 0 >    option event-threads 1 >#   option lock-timer 180 >#   option transport.address-family inet6 >    option base-port 49252 >    option max-port  60999 >end-volume > >I started normally after changing the ports on both nodes(port from 24007 to 24017), but I cannot add nodes through the ‘gluster peer probe node2‘ command, >It always prompts me:  >   Probe returned with Transport endpoint is not connected > > > > > > > > > > > >  > > >  >________ > > > >Community Meeting Calendar: > >Schedule - >Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC >Bridge: https://meet.google.com/cpu-eiue-hvk >Gluster-users mailing list >Gluster-users@xxxxxxxxxxx >https://lists.gluster.org/mailman/listinfo/gluster-users


 

________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux