Bug 762071 (GLUSTER-339) - glusterfsd fails to start when there are no active interfaces having address in the address family configured.
Summary: glusterfsd fails to start when there are no active interfaces having address ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-339
Product: GlusterFS
Classification: Community
Component: transport
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-27 18:25 UTC by Raghavendra G
Modified: 2009-11-12 17:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra G 2009-10-27 18:25:46 UTC 
With listen-host not specified, the server should continue to listen on 0.0.0.0/::0 even though there are no active interfaces with addresses in the address family configured. This enables clients from different address family to run.

The bug was submitted and fixed by Corentin Chary <corentin.chary>.
Comment 1 Anand Avati 2009-11-03 11:49:00 UTC 
PATCH: http://patches.gluster.com/patch/2025 in master (transport/name.c: refine the address resolution logic when listen-host is not specified.)
Comment 2 Anand Avati 2009-11-03 12:29:41 UTC 
PATCH: http://patches.gluster.com/patch/2024 in release-2.0 (transport/name.c: refine the address resolution logic when listen-host is not specified.)
Note You need to log in before you can comment on or make changes to this bug.