After adding a new resource type, you should test it as follows:
Define a resource group that contains resources of the new type. Ensure that the group contains all of the resources on which the new resource type depends.
Bring the resource group online in the cluster using cluster_mgr or the GUI.
For example, using cluster_mgr:
cmgr> admin online resource_group new_rg in cluster test_cluster |
Check the status of the resource group using cluster_mgr or GUI after a few minutes.
For example:
cmgr> show status of resource_group new_rg in cluster test_cluster |
If the resource group has been made online successfully, you will see output similar to the following:
State: Online Error: No error Owner: node1 |
If there are resource group errors, do the following:
Check the srmd logs ( /var/log/failsafe/srmd_nodename) on the node on which the resource group is online
Search for the string ERROR in the log file. There should be an error message about a resource in the resource group. The message also provides information about the action script that failed. For example:
Wed Nov 3 04:20:10.135 <E ha_srmd srm 12127:1 sa_process_tasks.c:627> CI_FAILURE, ERROR: Action (exclusive) for resource (10.0.2.45) of type (IP_address) failed with status (failed) exclusive script failed for the resource 10.0.2.45 of resource type IP_address. The status "failed" indicates that the script returned an error. |
Check the script logs (/var/log/failsafe/script_nodename on the same node) for IP_address exclusive script errors.
After the fixing the problems in the action script, perform an offline_force operation to clear the error. For example:
cmgr> admin offline_force resource_group new_rg in cluster test_cluster