On Tue, 2008-09-23 at 22:19 -0400, Lars Kellogg-Stedman wrote:
> (2) qdiskd noted the failure of the ping heuristic
>
> --> cluster becomes inquorate
> --> cman reboots cluster1 ("[CMAN ] quorum lost, blocking activity")
What are your qdiskd timings set to?
> I've swapped the startup order of cman and qdiskd, and now things seem
> to work (read, "the system actually boots and starts up cluster
> services"). Is there any reason *not* to do this?
No reason to not do this. This is fixed in the current RHEL5 branch.
> Would it make more
> sense to start qdiskd out of the cman init script (like fenced,
> groupd, et al)?
This is what we do in the current rhel5 branch:
- if qdiskd is chkconfig'd on start qdiskd before fenced during
startup
- qdiskd init script becomes a no-op if qdiskd is already running
-- Lon
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
