[Bugs] [Bug 1537362] glustershd/ glusterd is not using right port when connecting to glusterfsd process

bugzilla at redhat.com bugzilla at redhat.com
Mon Apr 16 04:48:53 UTC 2018


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



--- Comment #4 from zhou lin <zz.sh.cynthia at gmail.com> ---
On sn-0 node, mstate and log glusterfsd process started twice the port in use
is the first one, but glustershd keeps connecting using the latter one:
/////////////////log volume///////////////////////////////
[2018-04-15 18:06:00.280807] I [MSGID: 100030] [glusterfsd.c:2521:main]
0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 3.12.3
(args: /usr/sbin/glusterfsd -s sn-0.local --volfile-id
log.sn-0.local.mnt-bricks-log-brick -p
/var/run/gluster/vols/log/sn-0.local-mnt-bricks-log-brick.pid -S
/var/run/gluster/0af76d9541921cccad34e5fd3041a44d.socket --brick-name
/mnt/bricks/log/brick -l /var/log/glusterfs/bricks/mnt-bricks-log-brick.log
--xlator-option *-posix.glusterd-uuid=ac000adb-afb9-4826-8dba-9e4a3b641068
--brick-port 49154 --xlator-option log-server.listen-port=49154 --xlator-option
transport.socket.bind-address=sn-0.local)
[2018-04-15 18:06:00.767856] I [MSGID: 100030] [glusterfsd.c:2521:main]
0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 3.12.3
(args: /usr/sbin/glusterfsd -s sn-0.local --volfile-id
log.sn-0.local.mnt-bricks-log-brick -p
/var/run/gluster/vols/log/sn-0.local-mnt-bricks-log-brick.pid -S
/var/run/gluster/0af76d9541921cccad34e5fd3041a44d.socket --brick-name
/mnt/bricks/log/brick -l /var/log/glusterfs/bricks/mnt-bricks-log-brick.log
--xlator-option *-posix.glusterd-uuid=ac000adb-afb9-4826-8dba-9e4a3b641068
--brick-port 49157 --xlator-option log-server.listen-port=49157 --xlator-option
transport.socket.bind-address=sn-0.local)

The real working port is 49154 but glustershd keeps trying to connect to 49157
so it does not succeed
[2018-04-15 18:21:25.854249] I [rpc-clnt.c:1986:rpc_clnt_reconfig]
0-log-client-0: changing port to 49157 (from 0)
[2018-04-15 18:21:25.854597] E [socket.c:2369:socket_connect_finish]
0-log-client-0: connection to 192.168.1.12:49157 failed (Connection refused);
disconnecting socket

//////////////////////////// msate volume////////////////////////////
[2018-04-15 18:06:00.383103] I [MSGID: 100030] [glusterfsd.c:2521:main]
0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 3.12.3
(args: /usr/sbin/glusterfsd -s sn-0.local --volfile-id
mstate.sn-0.local.mnt-bricks-mstate-brick -p
/var/run/gluster/vols/mstate/sn-0.local-mnt-bricks-mstate-brick.pid -S
/var/run/gluster/79d00394b1085adcf7dc1fd4c57f71bc.socket --brick-name
/mnt/bricks/mstate/brick -l
/var/log/glusterfs/bricks/mnt-bricks-mstate-brick.log --xlator-option
*-posix.glusterd-uuid=ac000adb-afb9-4826-8dba-9e4a3b641068 --brick-port 49155
--xlator-option mstate-server.listen-port=49155 --xlator-option
transport.socket.bind-address=sn-0.local)
[2018-04-15 18:06:00.869951] I [MSGID: 100030] [glusterfsd.c:2521:main]
0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 3.12.3
(args: /usr/sbin/glusterfsd -s sn-0.local --volfile-id
mstate.sn-0.local.mnt-bricks-mstate-brick -p
/var/run/gluster/vols/mstate/sn-0.local-mnt-bricks-mstate-brick.pid -S
/var/run/gluster/79d00394b1085adcf7dc1fd4c57f71bc.socket --brick-name
/mnt/bricks/mstate/brick -l
/var/log/glusterfs/bricks/mnt-bricks-mstate-brick.log --xlator-option
*-posix.glusterd-uuid=ac000adb-afb9-4826-8dba-9e4a3b641068 --brick-port 49158
--xlator-option mstate-server.listen-port=49158 --xlator-option
transport.socket.bind-address=sn-0.local)

The real listening port for glusterfsd is 49155 but glustershd keeps trying to
connect through 49158, so it always fail

[2018-04-15 18:21:33.855829] I [rpc-clnt.c:1986:rpc_clnt_reconfig]
0-mstate-client-0: changing port to 49158 (from 0)
[2018-04-15 18:21:33.856229] E [socket.c:2369:socket_connect_finish]
0-mstate-client-0: connection to 192.168.1.12:49158 failed (Connection
refused); disconnecting socket

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=47OAUfMjvA&a=cc_unsubscribe


More information about the Bugs mailing list