[Bugs] [Bug 1540249] Gluster is trying to use a port outside documentation and firewalld' s glusterfs.xml
bugzilla at redhat.com
bugzilla at redhat.com
Tue Jan 30 16:05:29 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1540249
--- Comment #6 from devianca at gmail.com ---
with no rebooting of any of the node, same commands on node1:
[root at BUNKER ~]# gluster pool list
UUID Hostname State
f7976943-b81a-4bb4-a1fb-06253bf064c4 10.250.1.2 Connected
2f6697f4-2529-4072-910c-8862fdc43562 localhost Connected
[root at BUNKER ~]# gluster peer status
Number of Peers: 1
Hostname: 10.250.1.2
Uuid: f7976943-b81a-4bb4-a1fb-06253bf064c4
State: Peer in Cluster (Connected)
[root at BUNKER ~]# gluster volume status
Status of volume: replica1
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick 10.250.1.2:/array0/brick1 49152 0 Y 1192
Brick 10.250.1.1:/raid0array1/brick2 49152 0 Y 1395
Self-heal Daemon on localhost N/A N/A Y 1147
Self-heal Daemon on 10.250.1.2 N/A N/A Y 1175
Task Status of Volume replica1
------------------------------------------------------------------------------
There are no active volume tasks
[root at BUNKER ~]# gluster volume info
Volume Name: replica1
Type: Replicate
Volume ID: 5331fac2-42b6-4530-bf79-1ec0236efbc4
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.250.1.2:/array0/brick1
Brick2: 10.250.1.1:/raid0array1/brick2
Options Reconfigured:
client.bind-insecure: off
performance.client-io-threads: off
auth.allow: 10.250.1.1,10.250.1.2
transport.address-family: inet
nfs.disable: on
server.event-threads: 8
performance.io-thread-count: 64
performance.cache-size: 32MB
performance.write-behind-window-size: 64MB
server.allow-insecure: off
[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
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list