Bug 1002422
| Summary: | Gluster volume info gives error : Connection failed. Please check if gluster daemon is operational. No volumes present | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | senaik |
| Component: | glusterfs | Assignee: | Atin Mukherjee <amukherj> |
| Status: | CLOSED EOL | QA Contact: | storage-qa-internal <storage-qa-internal> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.1 | CC: | lmohanty, maciej, nsathyan, rhs-bugs, vbellur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | glusterd | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-03 17:10:53 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
senaik
2013-08-29 07:41:15 UTC
I have also seen this issue. Below is the scenario where I got the issue. I have a cluster of 4 nodes with 2 bricks each on which I had 5 volumes. I stopped 5 volumes one by one and started yum update (from glusterfs 3.4.0.23 to glusterfs 3.4.0.24 on 3 nodes). On the other node when I checked "gluster v info" I saw the error mentioned in the bug. Steps to reproduce: # gluster volume info vol Volume Name: vol Type: Replicate Volume ID: 16d51333-ef3b-4253-bbcc-59a9f393806b Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: 172.16.0.4:/srv/glusterfs/vol Brick2: 172.16.0.5:/srv/glusterfs/vol # gluster volume stop vol # gluster volume info vol # gluster volume start vol # gluster volume info vol # gluster volume set vol auth.allow 172.16.0.138,172.16.0.6 Connection failed. Please check if gluster daemon is operational. All commands where executed in script (without any sleep). Just before the crash: [2013-09-16 08:48:17.908841] W [socket.c:514:__socket_rwv] 0-roots-staging-client-0: readv failed (No data available) [2013-09-16 08:48:20.909766] W [socket.c:514:__socket_rwv] 0-roots-staging-client-0: readv failed (No data available) [2013-09-16 08:48:23.910556] W [socket.c:514:__socket_rwv] 0-roots-staging-client-0: readv failed (No data available) [2013-09-16 08:48:25.887573] W [glusterfsd.c:1002:cleanup_and_exit] (-->/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fd5cba4893d] (-->/lib/x86_64-linux-gnu/libpthrea d.so.0(+0x7e0e) [0x7fd5cc105e0e] (-->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xd5) [0x7fd5ccbf8545]))) 0-: received signum (15), shutting down Any progress? Glusterfs is for me quite useless right now. Its not reproducible in the latest downstream build with the steps given. Request you to recheck and let me know if the behaviour persists. As I am not able to reproduce the defect, can you please retry it and let me know the exact steps? Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/ If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |