[Bugs] [Bug 1412240] Glusterd does not reliably start at boot

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1412240



--- Comment #6 from Atin Mukherjee <amukherj at redhat.com> ---
[2017-01-17 10:51:58.122805] D [MSGID: 0]
[glusterd-peer-utils.c:167:glusterd_hostname_to_uuid] 0-management: returning
-1
[2017-01-17 10:51:58.122819] D [MSGID: 0]
[glusterd-utils.c:1009:glusterd_resolve_brick] 0-management: Returning -1
[2017-01-17 10:51:58.122833] E [MSGID: 106187]
[glusterd-store.c:4408:glusterd_resolve_all_bricks] 0-glusterd: resolve brick
failed in restore
[2017-01-17 10:51:58.122848] D [MSGID: 0]
[glusterd-store.c:4481:glusterd_restore] 0-management: Returning -1

The above indicates that the n/w interface might not be up before glusterd
tried to resolve the address of the brick. What OS baseline are you using?

This is an issue we've seen before. GlusterD starts before the network is
online. The 'Network is unreachable' error and the 'resolve brick failed' error
point to this. This shows up particularly in systemd based systems, like RHEL7.

https://bugzilla.redhat.com/show_bug.cgi?id=1260007#c3 explains what is
happening in detail.
tl;dr: systemd starts GlusterD, after the network devices are available, not
after the network is online. The network-online.target is reached after
GlusterD is started, to allow self GlusterFS _netdev mounts to work correctly.

This is not an easy problem to solve correctly. A solution is described in the
comment linked, which can help if self mounts are involved. If self-mounts are
not present, you could force glusterd to start after network-online.target, by
modifying it's service unit file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=W4pi1yAJ4d&a=cc_unsubscribe