Let me say clearly. When I start a new Heartbeat cluster, I must do
following steps:
1) Make all nodes of my cluster have the same /etc/ha.d directory
2) Copy a "bootstrap" cib.xml into every nodes' /var/lib/heartbeat/
crm
directory
not 100% required.
just make sure the first node you power up has it and the rest will
get it automatically.
Ah... I don't know this feature before...
Any way, thanks for telling me, I should test it.
I do above two things by using GNU cfengine. When cluster is
running up, I
never let cfengine to modify the cib.xml (but can read them, save
them)
When cluster is running, I can add/remove resources by using
cibadmin or
hb_gui, and let Heartbeat to synchronize the cib.xml.
But sometimes HA cluster may goes wrong (rarely, with any/unknown
reason),
Then you _really_ should report this... thats the only way its going
to get fixed ;-)
Can I ask what version you're running?
2.1.3-1, Debian packaging.
About two months ago, my 8-node HA cluster goes wrong and I save all
logs and give it a "cold" restart.
It never failed again, and I just didn't find time to analyze this
logs, maybe I should take a look now to find anything valuable.
and I have to do a "cold" retart, using following steps:
1) stop all heartbeat process on all nodes
2) using cfengine, copy one node's cib.xml back to my cfengine main
server,
to save these resources which I modified after HA's first run.
3) using cfengine, clean cib.xml (clean <cib>, <nodes>), and copy
it back to
all nodes again,
4) start "heartbeat" processes on every nodes.
Yes, I do remove the .sig* files, and clean/backup heartbeat log
files. What
I showed is just a small piece of my big cfengine config.
ok - just making sure
I think a good feature of Heartbeat 2.x is that one can modify HA
config
after it runs up. And a bad feature for Unix system administrator
is that I
must do something to save the live config (cib.xml, mainly), when
something
goes wrong and I have to start the cluster again.
Well it's always saved to disk - and if there is at least one
surviving node, then any node joining the cluster will receive a copy
of the current configuration.
So I'm not completely sure what you're talking about here - unless you
mean when you have to populate the configuration when you create a
cluster from scratch.
I just want to keep all my server config into one central cfengine
server and use Subversion to track their changes. And yes, when I
create a HA cluster from scratch, cfengine help me put every file at
their right position.
Regards,
Chun Tian (binghe)
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
