<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>Are you sure that the firewall is open. Usually , there could be a firewall inbetween the nodes.</div><div><br></div><div>Also, you can run a tcpdump on nodeA and issue a peer probe from NodeB and see if there is anything hitting it.</div><div><br></div><div>What about enabling trace logs and checking for any clues. You can find details about the log level at :
<a href="https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3/html/administration_guide/configuring_the_log_level
Best">https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3/html/administration_guide/configuring_the_log_level
Best</a> Regards,</div><div>Strahil Nikolov</div><div><br></div><div>В 10:07 +0800 на 07.12.2020 (пн), sky написа:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div style="margin: 0;">Hi: </div><div style="margin: 0;">1. The ports of both nodes are changed to 24017</div><div style="margin: 0;">2. After installation, change the port and start directly (non-restart)</div><div style="margin: 0;">3. I tried, but the nodes in the pool cannot connect after restarting. The log shows an attempt to connect to the default port</div><div style="margin: 0;"><br></div><div style="margin: 0;">Steps(both node1 and node2)</div><div style="margin: 0;"> # yum install glusterfs glusterfs-server glusterfs-fuse</div><div style="margin: 0;"> # vim <span style="font-family: arial; white-space: pre-wrap;">/etc/glusterfs/glusterd.vol</span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"> ....</span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"> </span><span style="font-family: arial; white-space: pre-wrap;">option transport.socket.listen-port 24017</span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"> ....</span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"> # systemctl start glusterd</span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"><br></span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"> # </span><span style="font-family: arial; white-space: pre-wrap;">gluster peer probe node2</span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"> </span><span style="font-family: arial; white-space: pre-wrap;">Probe returned with Transport endpoint is not connected</span></div><div style="margin: 0;"><span style="font-family: arial; white-space: pre-wrap;"><br></span></div><div style="margin: 0;">After changing the port back to 24007 and restarting, the connection is normal</div><p style="margin: 0;"><br></p><p style="margin: 0;"><br></p><p style="margin: 0;"><br></p><p style="margin: 0;"><br></p><div style="position:relative;zoom:1"></div><div id="divNeteaseMailCard"></div><p style="margin: 0;"><br></p><br><pre>在 2020-12-06 19:27:01，"Strahil Nikolov" <hunter86_bg@yahoo.com> 写道：</pre><pre>>Did you change the port on both nodes ?</pre><pre>>Did you restart glusterd on both nodes (the one you do peer probe and the other one that is being probed) ?</pre><pre>></pre><pre>>Have you tried to first peer probe and then change the port on all nodes in the pool ?</pre><pre>></pre><pre>></pre><pre>>Best Regards,</pre><pre>>Strahil Nikolov</pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>>В петък, 4 декември 2020 г., 12:18:42 Гринуич+2, sky <x_hsky@163.com> написа: </pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>>linux version: cenots 7.5 </pre><pre>>gluster verison: 7.5.1</pre><pre>>/etc/glusterfs/glusterd.vol: </pre><pre>>volume management</pre><pre>> type mgmt/glusterd</pre><pre>> option working-directory /var/lib/glusterd</pre><pre>> option transport-type socket,rdma</pre><pre>> option transport.socket.keepalive-time 10</pre><pre>> option transport.socket.keepalive-interval 2</pre><pre>> option transport.socket.read-fail-log off</pre><pre>> option transport.socket.listen-port 24017</pre><pre>> option transport.rdma.listen-port 24008</pre><pre>> option ping-timeout 0</pre><pre>> option event-threads 1</pre><pre>># option lock-timer 180</pre><pre>># option transport.address-family inet6</pre><pre>> option base-port 49252</pre><pre>> option max-port 60999</pre><pre>>end-volume</pre><pre>></pre><pre>>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,</pre><pre>>It always prompts me: </pre><pre>> Probe returned with Transport endpoint is not connected</pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>></pre><pre>> </pre><pre>></pre><pre>></pre><pre>> </pre><pre>>________</pre><pre>></pre><pre>></pre><pre>></pre><pre>>Community Meeting Calendar:</pre><pre>></pre><pre>>Schedule -</pre><pre>>Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC</pre><pre>>Bridge: https://meet.google.com/cpu-eiue-hvk</pre><pre>>Gluster-users mailing list</pre><pre>>Gluster-users@gluster.org</pre><pre>>https://lists.gluster.org/mailman/listinfo/gluster-users</pre></div><br><br><span title="neteasefooter"><p> </p></span></blockquote></body></html>