[Bugs] [Bug 1381339] New: starting glusterfs-server via init.d results in upstart reporting stop/ waiting
bugzilla at redhat.com
bugzilla at redhat.com
Mon Oct 3 18:28:55 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1381339
Bug ID: 1381339
Summary: starting glusterfs-server via init.d results in
upstart reporting stop/waiting
Product: GlusterFS
Version: 3.7.8
Component: core
Severity: high
Assignee: bugs at gluster.org
Reporter: ben at apcera.com
CC: bugs at gluster.org
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 at bwerthmann-0a393805:~$ sudo service glusterfs-server status
glusterfs-server start/running, process 23844
ubuntu at bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server start
* glusterd service is already running with pid 23844
ubuntu at bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server status
* glusterd service is running with pid 23844
ubuntu at bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server stop
* Stopping glusterd service glusterd
[ OK ]
ubuntu at bwerthmann-0a393805:~$ sudo service glusterfs-server status
glusterfs-server stop/waiting
ubuntu at bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server status
* glusterd service is not running.
ubuntu at bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server start
* Starting glusterd service glusterd
[ OK ]
ubuntu at bwerthmann-0a393805:~$ sudo /etc/init.d/glusterfs-server status
* glusterd service is running with pid 24210
ubuntu at 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.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list