ProbeWatch messages
During normal operations, the probe generates ProbeWatch messages and sends them to the ObjectServer. These messages tell the ObjectServer how the probe is running.
The following table describes the raw ProbeWatch error messages that the probe generates. For information about generic ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.
ProbeWatch message |
Description |
Triggers/causes |
|---|---|---|
| failed to Send probewatch %s\n | The probe failed to send a ProbeWatch message for the reason given. |
Check that HP Operations Manager is running correctly and is available. |
Failed to connect - aborting Retried up to maximum delay, probe will shutdown |
The probe failed to connect to HP Operations Manager after retrying to connect using the backoff strategy. |
Check that HP Operations Manager is running correctly and is available. Check the connection details specified in the hpom.props file. |
| Must be root to run this probe!!! | The user running the probe does not have root permissions. |
Run the probe as root. For details of how to do this, see the following page in the CORE Netcool/OMNIbus Knowledge Center: |
| not connecting to HPOM as no username and password provided | The probe failed to connect to HP Operations Manager. |
Check the username and password specified. |
| Sending probewatch Unable to get events | The probe cannot get messages from the target system. |
Check that HP Operations Manager is running correctly and is available. |
Failure in acknowledging HPOM alert. Failure in unacknowledging HPOM alert. Check probe log for details. |
When an Note: The failure must be an outcome from the command executed
in probe rules.
Other failures due to a mismatched URL or an inactive probe cannot generate this ProbeWatch; the probe is simply unaware of the action. |
Check probe log for details. |