[Bugs] [Bug 1385175] New: systemd service fails if quorum not established before timeout

[bugzilla at redhat.com]

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

            Bug ID: 1385175
           Summary: systemd service fails if quorum not established before
                    timeout
           Product: GlusterFS
           Version: mainline
         Component: packaging
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: joe at julianfamily.org
                CC: bugs at gluster.org



Description of problem:

Since the glusterd.service is set with "Type=forking", if glusterd fails to
fork within the default 90 seconds, the service fails while leaving glusterd
running.

If glusterd eventually has quorum established, it will start up successfully
and background itself leaving the cluster healthy but systemd status will show
that the service has failed to start.

How reproducible:
always

Steps to Reproduce:
1. Set up server quorum
2. Boot a server on a distro that uses systemd
3. wait 90 seconds

Actual results:
systemd service fails and leaves glusterd running

Expected results:
I think my expectation is that glusterd will daemonize and continue to try in
the background. Either that or we should just run glusterd as a foreground
process  when started by systemd and change Type to simple.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.