Description of problem: The systemd service fails due to timeout because the pid file is not created. This seems to happen when there are dns lookup problems. Version-Release number of selected component (if applicable): 3.7.8 How reproducible: always Steps to Reproduce: 1. Start "glusterd -p /var/run/glusterd.pid" (with volumes defined) without a way to look up hostnames of other hosts (myhostname is in nsswitch so it must be due to resolving the *other* hostnames) 2. ls /var/run/glusterd.pid Actual results: ls: cannot access '/var/run/glusterd.pid': No such file or directory Expected results: /var/run/glusterd.pid Additional info:
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.