[Bugs] [Bug 1700656] Glusterd did not start by default after node reboot

bugzilla at redhat.com bugzilla at redhat.com
Wed Apr 17 06:45:24 UTC 2019


--- Comment #3 from SATHEESARAN <sasundar at redhat.com> ---
Description of problem:
Did reboot on a server node, but glusterd process was not started automatically
after node reboot. When checked the glusterd status it was shown as
inactive(dead), but on doing glusterd start, the process was active again.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Do reboot on a server node.
2. After the node is back up again, check the glusterd status using "systemctl
status glusterd"
3. To start the glusterd process, do "systemctl start glusterd".

Actual results:
* When a server node is rebooted, and the node is back up online again, the
glusterd service on the node does not start automatically.
* Glusterd has to started using "systemctl start glusterd".

Expected results:
On rebooting a node, when the node comes back up online, glusterd should be

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Bugs mailing list