Atin Mukherjee [2016-05-25 15:50 +0530] :
> Could you check the brick log?
Sorry, I was not aware of the fact that there is an additional log. Here
it is:
[2016-05-25 08:26:11.830795] I [MSGID: 100030] [glusterfsd.c:2318:main] 0-/usr/local/sbin/glusterfsd: Started running /usr/local/sbin/glusterfsd version 3.7.6 (args: /usr/local/sbin/glusterfsd -s box-fra-01.klaas --volfile-id volume1.box-fra-01.klaas.usr-local-glusterfs-volume1 -p /var/db/glusterd/vols/volume1/run/box-fra-01.klaas-usr-local-glusterfs-volume1.pid -S /var/run/gluster/f816ca60d4f69f995e570ed408036266.socket --brick-name /usr/local/glusterfs/volume1 -l /var/log/glusterfs/bricks/usr-local-glusterfs-volume1.log --xlator-option *-posix.glusterd-uuid=2a95ee7c-bfb7-4acd-b029-42da963d5862 --brick-port 49153 --xlator-option volume1-server.listen-port=49153)
[2016-05-25 08:27:26.838921] E [socket.c:2278:socket_connect_finish] 0-glusterfs: connection to 10.1.0.1:24007 failed (Operation timed out)
[2016-05-25 08:27:26.839707] E [glusterfsd-mgmt.c:1818:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: box-fra-01.klaas (Connection reset by peer)
[2016-05-25 08:27:26.839756] I [glusterfsd-mgmt.c:1824:mgmt_rpc_notify] 0-glusterfsd-mgmt: Exhausted all volfile servers
[2016-05-25 08:27:26.840712] W [glusterfsd.c:1236:cleanup_and_exit] (-->0x40d0a0 <???> at /usr/local/sbin/glusterfsd -->0x4079ed <???> at /usr/local/sbin/glusterfsd ) 0-: received signum (1), shutting down
[2016-05-25 08:27:26.848019] W [rpc-clnt.c:1586:rpc_clnt_submit] 0-glusterfs: failed to submit rpc-request (XID: 0x1 Program: Gluster Portmap, ProgVers: 1, Proc: 5) to rpc-transport (glusterfs)
To me it looks like a firewall issue since there's a problem
establishing a connection (see line 2 and three). Yet, IP 10.1.0.1 is on
an internal interface that is not protected by firewall:
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>
ether 00:bd:17:0f:00:00
inet6 fd16:dcc0:f4cc::1:0:1 prefixlen 80
inet6 fe80::2bd:17ff:fe0f:0%tap0 prefixlen 64 scopeid 0x4
inet 10.1.0.1 netmask 0xff000000 broadcast 10.255.255.255
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
Opened by PID 10208
Further, I noticed that the daemon listens on every IP address:
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root glusterfsd 27595 11 tcp4 *:24007 *:*
Maybe that's causing some issues. How can I force the daemon to only
listen to IP 10.1.0.1?
Niklaas
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
