Antwort: AW: switching packages because of system maintenance
dk at webcluster.at
Wed Oct 23 06:22:14 MDT 2002
> thanks for your fast answer. But a restart of heartbeat would affect all
> packages not only one, so this is not an option. What I mean by package is
> an IP / package name, filesystems and a service. And I have a lot of
> packages with more than one resource.
> I am looking for a possibility to do the same what Heartbeat does, in case
> of nice_failback off, but for every package itself.
I am not the big heartbeat crack but I can tell you what I do:
Have a look at a typical takeover/release procedure on one node (ha-log).
There you will see the commands heartbeat sends.
heartbeat: 2002/09/28_00:36:15 info: Running /etc/ha.d/resource.d/IPaddr
Now if I want to takeover an IP on the other node because of maintenance I
/etc/ha.d/resource.d/IPaddr 10.1.0.213 stop
/etc/ha.d/resource.d/IPaddr 10.1.0.213 start
As heartbeat simply runs the resource scripts with start|stop depending on
a node leaves|takes over you can easily simulate heartbeats behavior with a
small shellscript which
runs the resource script like heartbeat does.
I think you look for a command that soes something like:
* Acquiring resource group: vie1.webdns.at 10.1.0.214 mirror_VIE1
* Releasing resource group: vie1.webdns.at 10.1.0.214 mirror_VIE1
but this seems to be a core feature of heartbeat itself that can't be
triggered by a simple command.
But as I said - a shell script should do this work for you.
Do a 'cat /var/log/ha-log | grep Running'
Then you see what heartbeat calls at which time.
You may have to look inside the scripts to see which environment variables
The heartbeat cracks may correct me, maybe I am far too complicated :)
More information about the Linux-HA