Bug 1065632
Summary: | glusterd: glusterd peer status failed with the connection failed error evenif glusterd is running | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | ssamanta |
Component: | glusterd | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | pre-release | CC: | bugs, gdubreui, gluster-bugs, mjc, mzywusko, redhat.bugs, zezar98 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-22 15:40:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
ssamanta
2014-02-15 09:34:58 UTC
I've had this happen also. I've gone back to glusterfs-3.5.0-0.4.beta2 as the peer probe function works in that release. Had same issue. Using glusterfs-server-3.5.1-1.el7.x86_64. After disabling SELinux (setenforce 0) it works fine. I hope it helps. I found that the use of Quotas was the cause of my problems. Are you able to check with quotas enabled? i.e. gluster volume quota my_volume enable See this bug report for my build process: https://bugzilla.redhat.com/show_bug.cgi?id=1113460 Thanks, Rich Still broken in glusterfs-351beta2-epel.repo Thanks, Rich Same problem; deleting /var/run/glusterd.socket and restarting fixed it. [root@karsh brick1]# gluster peer probe xena Connection failed. Please check if gluster daemon is operational. [root@karsh brick1]# systemctl stop glusterd [root@karsh brick1]# rm /var/run/glusterd.socket rm: remove socket ‘/var/run/glusterd.socket’? y [root@karsh brick1]# systemctl start glusterd [root@karsh brick1]# gluster peer probe xena peer probe: success. [root@karsh brick1]# rpm -qa | grep gluster glusterfs-api-3.5.3-1.fc20.x86_64 glusterfs-server-3.5.3-1.fc20.x86_64 glusterfs-libs-3.5.3-1.fc20.x86_64 glusterfs-fuse-3.5.3-1.fc20.x86_64 glusterfs-cli-3.5.3-1.fc20.x86_64 glusterfs-3.5.3-1.fc20.x86_64 pre-release version is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it. (In reply to Michael J. Chudobiak from comment #7) > Same problem; deleting /var/run/glusterd.socket and restarting fixed it. > > > [root@karsh brick1]# gluster peer probe xena > Connection failed. Please check if gluster daemon is operational. > > [root@karsh brick1]# systemctl stop glusterd > > [root@karsh brick1]# rm /var/run/glusterd.socket > rm: remove socket ‘/var/run/glusterd.socket’? y > > [root@karsh brick1]# systemctl start glusterd > > [root@karsh brick1]# gluster peer probe xena > peer probe: success. > > [root@karsh brick1]# rpm -qa | grep gluster > glusterfs-api-3.5.3-1.fc20.x86_64 > glusterfs-server-3.5.3-1.fc20.x86_64 > glusterfs-libs-3.5.3-1.fc20.x86_64 > glusterfs-fuse-3.5.3-1.fc20.x86_64 > glusterfs-cli-3.5.3-1.fc20.x86_64 > glusterfs-3.5.3-1.fc20.x86_64 Worked for me! Thanks a lot |