Joel, >From the logs, we see bind(3) is failing with "Address already in use". Could you check using netstat, what other process is listening on the port, around the time of failure? # netstat -ntlp | grep <brick_port> where brick_port can be found in the logs, see "--xlator-option home-server.listen-port=49157". thanks, krish ----- Original Message ----- > On fedora 19, the glusterfs-3.4.0 package just went out replacing 3.4 beta4. > On the systemctl restart glusterd.service, one of the glusterfsd won't > restart. > > in /var/log/glusterfs/bricks/lhome-gluster_home.log I see: > > [2013-07-29 23:34:41.949089] I [glusterfsd.c:1910:main] > 0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 3.4.0 > (/usr/sbin/glusterfsd -s ir2 --volfile-id home.ir2.lhome-gluster_home -p > /var/lib/glusterd/vols/home/run/ir2-lhome-gluster_home.pid -S > /var/run/5a538b707ce5dbf525ba6d01835863bb.socket --brick-name > /lhome/gluster_home -l /var/log/glusterfs/bricks/lhome-gluster_home.log > --xlator-option *-posix.glusterd-uuid=9d2d74bf-9055-47a6-b3df-8c2057ea1dd9 > --brick-port 49157 --xlator-option home-server.listen-port=49157) > [2013-07-29 23:34:41.952053] I [socket.c:3480:socket_init] > 0-socket.glusterfsd: SSL support is NOT enabled > [2013-07-29 23:34:41.952087] I [socket.c:3495:socket_init] > 0-socket.glusterfsd: using system polling thread > [2013-07-29 23:34:41.952172] E [socket.c:695:__socket_server_bind] > 0-socket.glusterfsd: binding to failed: Address already in use > [2013-07-29 23:34:41.952186] E [socket.c:698:__socket_server_bind] > 0-socket.glusterfsd: Port is already in use > [2013-07-29 23:34:41.952195] W [rpcsvc.c:1394:rpcsvc_transport_create] > 0-rpc-service: listening on transport failed > > Any suggestions? > > I tried hand running the fsd command with other ports but get the same > result. > > Joel > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users
