Bug 1001577
| Summary: | quota build 3: volume start failed | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> |
| Component: | glusterd | Assignee: | Kaushal <kaushal> |
| Status: | CLOSED DUPLICATE | QA Contact: | Saurabh <saujain> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | CC: | kaushal, kparthas, mzywusko, psriniva, rhs-bugs, vagarwal, vbellur |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 2.1.2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.4.0.49rhs | Doc Type: | Bug Fix |
| Doc Text: |
Previously the glusterd would listen on port 24007 for CLI requests, there was a possibility for glusterd to reject CLI requests from unprivileged ports (>1024) leading to CLI command execution failures.
With this fix, glusterd listens to CLI requests through a socket file (in /var/run/glusterd.sock) preventing CLI command execution failures.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-03 07:31:32 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
Saurabh
2013-08-27 10:35:26 UTC
The problem here is not with quota. rhsauto032 ran out of privileged ports (which may or may not have been due to quota, most likely because of running gluster commands). The brick process on rhsauto032 connected to glusterd to fetch the brick volfile using an insecure port (>1024). Currently glusterd (and gluster as a whole) rejects incoming requests from insecure ports. Since the brick process couldn't get its volfile, if failed to start and this lead to the inconsistent state observed in the bug report. The current workaround for this issue is to set the option, 'management.rpc-auth-allow-insecure on' in /etc/glusterfs/glusterd.vol and restart glusterd. Setting this option allows request from insecure ports. There have been patches posted upstream for the following downstream bugs which track the unprivileged ports issue. 1. https://bugzilla.redhat.com/show_bug.cgi?id=979926 -> upstream bug https://bugzilla.redhat.com/show_bug.cgi?id=980746 2. https://bugzilla.redhat.com/show_bug.cgi?id=979861 -> upstream bug https://bugzilla.redhat.com/show_bug.cgi?id=980754 The upstream patches haven't been accepted yet because of some regression failures. Once those patches are accepted, they can be backported downstream to the u1 branch. Want to let the patches soak in for U2. removing from u1 list The fix for 979861 also addresses this. Moving to ON_QA. didn't the same problem again, tried out several times on glusterfs-3.4.0.49rhs Can you please verify this doc text for technical accuracy? Closing this bug as dup of 979861, as this bug is just a specific incarnation of it. *** This bug has been marked as a duplicate of bug 979861 *** |