On Jul 11, 2008, at 4:34 AM, Steve Wray wrote:
Hi there,
A while ago someone send a link to a really great document:
http://clusterlabs.org/mw/Image:Configuration_Explained.pdf
which I've been referring to while tuning and diagnosing some
heartbeat configs here.
One of the commands it refers to is crm_standby. It reads:
<quote>
To check the standby status of the current machine, simply run:
crm_standby --get-value
</quote>
which gives me the output:
Please specify a node with -U or -u
you might have an old version. newer versions use the current node if
none is supplied.
It also gives the example:
<quote>
You can also check the status of other nodes in the cluster by
specifying the --node-uname option. Eg.
crm_standby --get-value --node-uname sles-2
</quote>
which gives me the output:
value=(null)
Error performing operation: The object/attribute does not exist
and, yes, the value I give it for the uname *is* correct.
right, but there is no value for standby which is what its referring
to :)
this also has been "tweaked" in later versions
I've tried this on a few nodes all of which actually do work
properly with respect to heartbeat failover. So it would seem that
my heartbeat config on these servers is more or less correct...
So, has heartbeat already diverged from this document or am I
missing something?
Thanks!
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
