gluster problems

etc-glusterfs-glusterd.vol.log

[2015-06-30 12:26:32.334650] I [MSGID: 100030] [glusterfsd.c:2301:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.7.2 (args: /usr/sbin/glusterd -p /var/run/glusterd.pid)
[2015-06-30 12:26:32.338855] I [glusterd.c:1372:init] 0-management: Maximum allowed open file descriptors set to 65536
[2015-06-30 12:26:32.338886] I [glusterd.c:1420:init] 0-management: Using /var/lib/glusterd as working directory
[2015-06-30 12:26:32.345185] W [rdma.c:4493:__gf_rdma_ctx_create] 0-rpc-transport/rdma: rdma_cm event channel creation failed (No such device)
[2015-06-30 12:26:32.345209] W [rdma.c:4793:init] 0-rdma.management: Failed to initialize IB Device
[2015-06-30 12:26:32.345218] W [rpc-transport.c:358:rpc_transport_load] 0-rpc-transport: 'rdma' initialization failed
[2015-06-30 12:26:32.345297] W [rpcsvc.c:1595:rpcsvc_transport_create] 0-rpc-service: cannot create listener, initing the transport failed
[2015-06-30 12:26:32.345324] E [MSGID: 106243] [glusterd.c:1646:init] 0-management: creation of 1 listeners failed, continuing with succeeded transport
[2015-06-30 12:26:32.346234] I [MSGID: 106228] [glusterd.c:421:glusterd_check_gsync_present] 0-glusterd: geo-replication module not installed in the system [No such file or directory]
[2015-06-30 12:26:32.346791] I [glusterd-store.c:2035:glusterd_restore_op_version] 0-glusterd: retrieved op-version: 30603
[2015-06-30 12:26:32.346906] I [glusterd.c:156:glusterd_uuid_init] 0-management: retrieved UUID: b190db46-8f3b-4e05-a755-474b8521b18a
[2015-06-30 12:26:32.346969] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-glustershd: setting frame-timeout to 600
[2015-06-30 12:26:32.347127] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-nfs: setting frame-timeout to 600
[2015-06-30 12:26:32.347252] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-quotad: setting frame-timeout to 600
[2015-06-30 12:26:32.347373] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-bitd: setting frame-timeout to 600
[2015-06-30 12:26:32.347474] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-scrub: setting frame-timeout to 600
[2015-06-30 12:26:32.347627] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-snapd: setting frame-timeout to 600
[2015-06-30 12:26:32.518841] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-snapd: setting frame-timeout to 600
[2015-06-30 12:26:32.520808] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-snapd: setting frame-timeout to 600
[2015-06-30 12:26:32.523015] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-snapd: setting frame-timeout to 600
[2015-06-30 12:26:32.524821] I [glusterd-handler.c:3387:glusterd_friend_add_from_peerinfo] 0-management: connect returned 0
[2015-06-30 12:26:32.524884] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600
[2015-06-30 12:26:32.528224] W [socket.c:923:__socket_keepalive] 0-socket: failed to set TCP_USER_TIMEOUT -1000 on socket 13, Invalid argument
[2015-06-30 12:26:32.528245] E [socket.c:3015:socket_connect] 0-management: Failed to set keep-alive: Invalid argument
[2015-06-30 12:26:32.529957] E [MSGID: 106187] [glusterd-store.c:4245:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore
[2015-06-30 12:26:32.530005] E [xlator.c:426:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again
[2015-06-30 12:26:32.530015] E [graph.c:322:glusterfs_graph_init] 0-management: initializing translator failed
[2015-06-30 12:26:32.530021] E [graph.c:661:glusterfs_graph_activate] 0-graph: init failed
[2015-06-30 12:26:32.530415] W [glusterfsd.c:1219:cleanup_and_exit] (--> 0-: received signum (0), shutting down

Just in case this happens to anyone, the problem was that glusterd crashes if it references itself with a dynamic IP and doesn't have such IP. In my case the hostname mynfs was pointing to this glusterfs host till I installed another one, following http://community.redhat.com/blog/2014/11/up-and-running-with-ovirt-3-5-part-two/.

Therefore, to fix it, check that your volume's bricks are indeed referenced by hostname or IP.

Hi, @txomon,

Thanks for the gist. I am actually encountering the same issue.

Can you be a little more specific on this problem? Like how do you seek the question is actually due to dynamic IP issue?

Thanks.