The GDS enables you to log relevant information that is passed from the GDS to the scripts that the GDS starts. This information includes the status of the start, probe, validate, and stop methods as well as property variables. You can use this information to diagnose problems or errors in your scripts, or apply it to other purposes.
You use the Log_level property that is described in Log_level Property to specify the level, or type, of messages that the GDS is to log. You can specify NONE, INFO, or ERR.
The following two GDS log files are placed in the directory /var/cluster/logs/DS/resource-group-name/resource-name:
start_stop_log.txt, which contains messages that are generated by resource start and stop methods
probe_log.txt, which contains messages that are generated by the resource monitor
The following example shows the types of information that start_stop_log.txt contains:
06/12/2006 12:38:05 phys-node-1 START-INFO> Start succeeded. [/home/brianx/sc/start_cmd] 06/12/2006 12:42:11 phys-node-1 STOP-INFO> Successfully stopped the application
The following example shows the types of information that probe_log.txt contains:
06/12/2006 12:38:15 phys-node-1 PROBE-INFO> The GDS monitor (gds_probe) has been started 06/12/2006 12:39:15 phys-node-1 PROBE-INFO> The probe result is 0 06/12/2006 12:40:15 phys-node-1 PROBE-INFO> The probe result is 0 06/12/2006 12:41:15 phys-node-1 PROBE-INFO> The probe result is 0