Bug 951177
| Summary: | glusterd silently fails if a peer file is empty | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> |
| Component: | glusterd | Assignee: | bugs <bugs> |
| Status: | CLOSED DEFERRED | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.1 | CC: | bugs, gluster-bugs |
| 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: | 2014-12-14 19:40:30 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: | |||
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug. If there has been no update before 9 December 2014, this bug will get automatocally closed. |
Description of problem: Two people were individually complaining that glusterd would silently end. Looking at the logs, there was no indication why. {all normal start up lines above, including the rest of the confusion causing "Unknown key" list} [2013-04-11 13:49:24.184786] E [glusterd-store.c:2080:glusterd_store_retrieve_volume] 0-: Unknown key: brick-25 [2013-04-11 13:49:25.152621] E [xlator.c:385:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2013-04-11 13:49:25.152738] E [graph.c:294:glusterfs_graph_init] 0-management: initializing translator failed [2013-04-11 13:49:25.152783] E [graph.c:483:glusterfs_graph_activate] 0-graph: init failed [2013-04-11 13:49:25.153205] W [glusterfsd.c:831:cleanup_and_exit] (-->/usr/sbin/glusterd(main+0x574) [0x407404] (-->/usr/sbin/glusterd(glusterfs_volumes_init+0x145) [0x405bb5] (-->/usr/sbin/glusterd(glusterfs_process_volfp+0x198) [0x405a68]))) 0-: received signum (0), shutting down Version-Release number of selected component (if applicable): 3.3.1 How reproducible: Always Steps to Reproduce: 1. Truncate a file in /var/lib/glusterd/peers 2. start glusterd Actual results: glusterd silently fails with no indication what's wrong. Expected results: glusterd should throw an error explaining why it's dying. Additional info: I don't know how the peer files can get into an empty state. I believe this has something to do with adding new peers.