Debug Size:

8 - Testing RSF-1

The following tests show how RSF-1 can be used to manually move services around the cluster and perform automatic failovers in the event of failures. The user may find it useful to open two terminal sessions per node whilst undertaking these tests; one for monitoring the RSF-1 log files, and the other to issue the various commands.
NOTE - When connecting to cluster nodes, use the fixed IP addresses, not the service VIPs as these sessions will hang or exit during failover tests
The recommended way to monitor log files is as follows (on each cluster node):
romulus# tail -f /opt/HAC/RSF-1/log/rsfmon.log
[9555 Oct 3 09:15:02] Process mlocked in memory
[9556 Oct 3 09:15:02] Process mlocked in memory
[9552 Oct 3 09:15:03] INFO: event-notify: LOG_INFO RSF_DAEMON machine=romulus state=start
[9552 Oct 3 09:15:03] INFO: event-notify: LOG_INFO RSF_SERVICE service=POOLA state=stopped mode=manual block=unblocked
[9552 Oct 3 09:15:03] INFO: event-notify: LOG_INFO RSF_SERVICE service=POOLB state=stopped mode=manual block=unblocked
[9552 Oct 3 09:15:03] NOTICE: net heartbeat (7, seq 3) from remus OK
[9552 Oct 3 09:15:03] CRIT: Established contact with remus
[9552 Oct 3 09:15:03] romulus.POOLA unknown/manual/unblocked -> stopped/manual/unblocked
[9552 Oct 3 09:15:03] romulus.POOLB unknown/manual/unblocked -> stopped/manual/unblocked
[9552 Oct 3 09:15:03] NOTICE: Service POOLA not running, is manual/unblocked, not starting it.
[9552 Oct 3 09:15:03] NOTICE: Service POOLB not running, is manual/unblocked, not starting it.
Prev Page
Next Page