Looks like you have a stale process running. Can you force kill all gluster daemons, rm -rf /etc/glusterd and start fresh? Please ensure name resolution works fine between the hosts. Avati On Tue, Jan 18, 2011 at 6:32 AM, Gerry Reno <greno at verizon.net> wrote: > Restarted daemons on both servers and checked logs: > > > +------------------------------------------------------------------------------+ > [2011-01-18 00:50:58.452742] I > [glusterd-handler.c:673:glusterd_handle_cli_list_friends] glusterd: > Received cli list req > [2011-01-18 00:51:04.994903] I [glusterfsd.c:672:cleanup_and_exit] > glusterfsd: shutting down > [2011-01-18 00:51:07.35087] I [glusterd.c:275:init] management: > Using /etc/glusterd as working directory > [2011-01-18 00:51:07.36126] E > [rpc-transport.c:905:rpc_transport_load] rpc-transport: > /usr/local/lib/glusterfs/3.1.2/rpc-transport/rdma.so: cannot open > shared object file: No such file or directory > [2011-01-18 00:51:07.36141] E > [rpc-transport.c:909:rpc_transport_load] rpc-transport: volume > 'rdma.management': transport-type 'rdma' is not valid or not found > on this machine > [2011-01-18 00:51:07.36233] I [glusterd.c:87:glusterd_uuid_init] > glusterd: retrieved UUID: 301d715d-649f-42a3-ac2f-208ada7447c2 > [2011-01-18 00:51:07.36313] E > [glusterd-store.c:1446:glusterd_store_retrieve_peers] management: > key: 0x7f8580, and value: (nil) > Given volfile: > > +------------------------------------------------------------------------------+ > 1: volume management > 2: type mgmt/glusterd > 3: option working-directory /etc/glusterd > 4: option transport-type socket,rdma > 5: option transport.socket.keepalive-time 10 > 6: option transport.socket.keepalive-interval 2 > 7: end-volume > 8: > > > +------------------------------------------------------------------------------+ > > I see it complaining about transport-type so I added 'tcp' and restarted > daemons again: > > [2011-01-18 01:00:06.436154] I [glusterd.c:275:init] management: > Using /etc/glusterd as working directory > [2011-01-18 01:00:06.436993] E [socket.c:322:__socket_server_bind] > tcp.management: binding to failed: Address already in use > [2011-01-18 01:00:06.437008] E [socket.c:325:__socket_server_bind] > tcp.management: Port is already in use > [2011-01-18 01:00:06.437108] I [glusterd.c:87:glusterd_uuid_init] > glusterd: retrieved UUID: 301d715d-649f-42a3-ac2f-208ada7447c2 > Given volfile: > > +------------------------------------------------------------------------------+ > 1: volume management > 2: type mgmt/glusterd > 3: option working-directory /etc/glusterd > 4: option transport-type socket,tcp,rdma > 5: option transport.socket.keepalive-time 10 > 6: option transport.socket.keepalive-interval 2 > 7: end-volume > 8: > > > +------------------------------------------------------------------------------+ > > It looks like it's trying to complain about a port, but what port? > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >
