[Bugs] [Bug 1364495] New: systemd could not restart glusterd after /var/run/ glusterd.pid disappeared

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 5 13:41:27 UTC 2016


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

            Bug ID: 1364495
           Summary: systemd could not restart glusterd after
                    /var/run/glusterd.pid disappeared
           Product: GlusterFS
           Version: mainline
         Component: scripts
          Assignee: ndevos at redhat.com
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org
        Depends On: 1364492



+++ 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:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1364492
[Bug 1364492] systemd could not restart glusterd after
/var/run/glusterd.pid disappeared
-- 
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=bRdfsphu8m&a=cc_unsubscribe


More information about the Bugs mailing list