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:
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.