Christine Caulfield wrote:
gordan@xxxxxxxxxx wrote:
Hi,
I have a weird problem that I can't figure out. I have a two node
cluster (<cman two_node="1" expected_votes="1">), which means that a
node should be quorate on it's own, and there should be no problems for
it to join it's own fence domain (presumably).
But when I do:
service cman start
All the components up to fenced start, but:
fence -c -w join
waits until it times out and never starts.
The logs don't seem to reveal anything other than that fenced failed to
start. What are the likely causes of this kind of a problem? I don't
have any real fencing devices defined (yet) in my cluster.conf, only the
following stub entry:
<fence>
<method name="1">
<device name = "foo"/>
</method>
</fence>
That's probably why. It's trying to fence the non-member nodes and its
failing because you don't have any valid fence devices.
I'm not sure that's right, because I've had dozens of clusters work
without fencing devices in various prototyping environments. So how does
one start up an incomplete cluster without any fence devices?
Try starting fenced with '-D', it'll show more debugging information.
I am not starting fenced directly, I'm doing it via
fence_tool -c -w join
That is supposed to start up fenced, according to documentation, but it
doesn't include the -D option.
Gordan
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
