TSAMP: Monitor Command Timeout

Cause

1) What is a monitor command timeout:
A monitor command timeout occurs when a set amount of time has passed after TSAMP issues a monitor command and the monitor command has not exited/finished. This set amount of time is set when the resource is created and can be found in the persistent attributes for all IBM.Application resources.

2) What happens when a monitor command times out:
When the monitor command runs in excess of the time (in seconds) set in the MonitorCommandTimeout attribute, then TSAMP will kill the monitor command script and issue the above messages. When this happens the resource who's monitor command was killed is marked with the OpState of "Unknown" and no further automation action will be taken against that resource until such a time as a monitor command returns within the MonitorCommandTimout timeframe with a valid OpState value.

To check the value of the MonitorCommandTimeout attribute issue the following command on either node as root:
lsrsrc -s 'Name like"%" && ResourceType=1' IBM.Application Name MonitorCommandTimeout

3) What causes monitor command timeouts:
A monitor command timeout is typically due to a increased load on the system making what are typically simple commands take longer to complete. TSAMP uses shells scripts to monitor resources and those scripts can vary in complexity depending on what is needed for the solution.
If monitor command timeouts are occurring and there is no extra load on the systems, then likely the value of the MonitorCommandTimeout attribute has been set to aggressive and needs to be relaxed.