Displaying 2 results from an estimated 2 matches for "__socket_server_bind".
2011 Jan 12
1
Setting up 3.1
[Repost - last time this didn't seem to work]
I've been running gluster for a couple of years, so I'm quite used to 3.0.x and earlier. I'm looking to upgrade to 3.1.1 for more stability (I'm getting frequent 'file has vanished' errors when rsyncing from 3.0.6) on a bog-standard 2-node dist/rep config. So far it's not going well. I'm running on Ubuntu Lucid x64
2017 Aug 06
1
[3.11.2] Bricks disconnect from gluster with 0-transport: EPOLLERR
...06 03:16:12.484758] I [MSGID: 106478] [glusterd.c:1422:init] 0-management: Maximum allowed open file descriptors set to 65536
[2017-08-06 03:16:12.484797] I [MSGID: 106479] [glusterd.c:1469:init] 0-management: Using /var/lib/glusterd as working directory
[2017-08-06 03:16:12.489459] E [socket.c:796:__socket_server_bind] 0-socket.management: binding to failed: Address already in use
[2017-08-06 03:16:12.489485] E [socket.c:799:__socket_server_bind] 0-socket.management: Port is already in use
[2017-08-06 03:16:12.489503] W [rpcsvc.c:1667:rpcsvc_create_listener] 0-rpc-service: listening on transport failed
[2017-08...