Bug 1450567
| Summary: | brick process cannot be started at the first time | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | likunbyl | ||||
| Component: | core | Assignee: | bugs <bugs> | ||||
| Status: | CLOSED EOL | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.8 | CC: | amukherj, bugs, likunbyl | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-11-07 10:39:47 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: | |||||||
| Attachments: |
|
||||||
|
Description
likunbyl
2017-05-13 09:13:16 UTC
This looks like that the brick process failed to fetch volfile from glusterd. Do you have the glusterd log handy? Created attachment 1285200 [details]
glusterd log
from brick log: [2017-05-11 08:49:28.064464] I [MSGID: 101190] [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2017-05-11 08:51:30.661259] W [socket.c:590:__socket_rwv] 0-glusterfs: readv on 10.3.3.11:24007 failed (Connection reset by peer) [2017-05-11 08:51:30.661699] E [rpc-clnt.c:365:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x192)[0x7f62bdc09002] (--> /lib64/libgfrpc.so.0(saved_frames_unwind+0x1de)[0x7f62bd9d084e] (--> /lib64/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f62bd9d095e] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x84)[0x7f62bd9d20b4] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x120)[0x7f62bd9d2990] ))))) 0-glusterfs: forced unwinding frame type(GlusterFS Handshake) op(GETSPEC(2)) called at 2017-05-11 08:49:43.653446 (xid=0x1) [2017-05-11 08:51:30.661716] E [glusterfsd-mgmt.c:1686:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:gvol0.10.3.3.11.mnt-brick2-vol) from glusterd log: [2017-05-11 08:51:30.665606] W [socket.c:590:__socket_rwv] 0-management: readv on /var/run/gluster/16909a0348d1da701cfe2486bf91a886.socket failed (No data available) [2017-05-11 08:51:30.668913] I [MSGID: 106005] [glusterd-handler.c:5055:__glusterd_brick_rpc_notify] 0-management: Brick 10.3.3.11:/mnt/brick2/vol has disconnected from glusterd. My question is what caused the readv on the socket failed, and a second running of the same command succeed? Can't it just retry automatically? I just pasted the logs for the reference, the analysis is not complete yet. (In reply to Atin Mukherjee from comment #5) > I just pasted the logs for the reference, the analysis is not complete yet. Is there any progress in this matter? This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release. |