[Bugs] [Bug 1540249] Gluster is trying to use a port outside documentation and firewalld' s glusterfs.xml

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1540249

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amukherj at redhat.com



--- Comment #8 from Atin Mukherjee <amukherj at redhat.com> ---
Based on the netstat output shared (mentioned below)
[root at BUNKER ~]# netstat -nap | grep 49151
tcp        0      0 10.250.1.1:24007        10.250.1.2:49151        SYN_RECV   
-
tcp        0      0 10.250.1.1:49151        10.250.1.2:24007        ESTABLISHED
870/glusterd

49151 looks to be the outband port glusterd has used to communicate to other
glusterd instances. In our deployments what we have seen this outbound port
keeps in the range of privileged port but in this particular case it picked up
49151 and since 49151 is kind of blocked all the communication from glusterd at
10.250.1.1 to other glusterd instances aren't happening because of which you
see nodes are stuck in the cli command.

Just a wild guess was it like that port was initially unblocked and post
glusterd came up this port was made blocked?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.