+++ This bug was initially created as a clone of Bug #1364492 +++ Description of problem: I'm not sure what caused /var/run/glusterd.pid to be missing, but after an update systemd was unable to start glusterd again. glusterd was running, but a 2nd instance was unable to bind the 24007 port (address already in use). I was not able to reproduce this when configuring the glusterd.service file as Type=simple and adding the --no-daemon parameter to the commandline. Version-Release number of selected component (if applicable): 3.8.1 (on Fedora 23/24) How reproducible: Have updates installed by ansible, with a restart of the glusterd service after the packages got updated. Steps to Reproduce: 1. install and configure Gluster, make sure that the glusterd service is running 2. update the packages 3. restart the glusterd service with "systemctl restart glusterd" Actual results: glusterd fails to restart Expected results: glusterd should have been restarted with the new (updated) binaries Additional info:
REVIEW: http://review.gluster.org/15101 (glusterd: do not fork into the background when systemd is used) posted (#1) for review on master by Niels de Vos (ndevos)
REVIEW: http://review.gluster.org/15101 (glusterd: do not fork into the background when systemd is used) posted (#2) for review on master by Niels de Vos (ndevos)
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.