Description of problem: The Ubuntu Trusty package has an Upstart (/etc/init/glusterfs-server.conf) and an init.d script (/etc/init.d/glusterfs-server): ubuntu@bwerthmann-0a393805:~$ sudo service glusterfs-server status glusterfs-server start/running, process 23844 ubuntu@bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server start * glusterd service is already running with pid 23844 ubuntu@bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server status * glusterd service is running with pid 23844 ubuntu@bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server stop * Stopping glusterd service glusterd [ OK ] ubuntu@bwerthmann-0a393805:~$ sudo service glusterfs-server status glusterfs-server stop/waiting ubuntu@bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server status * glusterd service is not running. ubuntu@bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server start * Starting glusterd service glusterd [ OK ] ubuntu@bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server status * glusterd service is running with pid 24210 ubuntu@bwerthmann-0a393805:~$ sudo service glusterfs-server status glusterfs-server stop/waiting Version-Release number of selected component (if applicable): 3.7.8 How reproducible: always Steps to Reproduce: 1. sudo /etc/init.d/glusterfs-server status 2. sudo /etc/init.d/glusterfs-server stop 3. sudo /etc/init.d/glusterfs-server start 4. sudo service glusterfs-server status glusterfs-server stop/waiting Actual results: glusterfs-server stop/waiting Expected results: There should be no difference in state between Upstart and init.d. Additional info: We resolved this issue by removing the Upstart script via config mgmt.
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.