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 ProbeWatch messages that the probe generates. For information about generic Netcool/OMNIbus ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 1. ProbeWatch messages
ProbeWatch message	Description	Triggers or causes
`Cannot open recovery file filename for reading: No such file or directory`	The probe is unable to open the recovery file specified by the RecoveryFile property at startup.	Either the recovery file does not exist, has been locked, or the probe does not have permission to access it. The probe starts in clean start mode instead of recovery mode.
`Cannot open recovery file filename for writing: No such file or directory` `Cannot read recovery file. Continuing with invalid values`	The probe is unable to read or update the recovery file specified by the RecoveryFile property.	Either the recovery file has been locked or the probe does not have permission to write to it. The probe continues functioning as normal, but without updating the recovery file.
`Cannot stat file: No such file or directory`	The probe is unable to obtain the status of the file specified by the LogFile property.	Possible reasons include the log file does not exist or has been locked, or the probe does not have permission to access the file. The probe then pauses for a period specified by the PollTime property before attempting to open the log file again.
`Failed to send SIGHUP to syslogd daemon`	The probe has failed to send a HUP signal to the `syslogd` process during probe startup.	Either the probe is unable to open the `syslogd` PID file or an error has occurred while sending the HUP signal to the `syslogd` process. Check that the PID file is in the location set by the SyslogPIDFile property.
`File inode changed! Re-opening file`	The probe detected a change in the inode number of the syslog log file and is reopening the log file.	A syslog log file rollover occurred. The probe reads the rolled-over log file from the beginning.
`File truncated! Reopening file`	The probe detected a truncation of the syslog log file.	A syslog log file rollover occurred. The probe reads the rolled-over log file from the beginning.
`Going Down`	The probe is shutting down.	The probe is shutting down after performing the shutdown routine.
`No syslog messages received for n seconds`	No new syslog messages have been received for the specified number of seconds.	The probe has received no messages for the time specified by the InactivityAlarmTime property.
`Running ...`	The probe is running normally.	The probe has just been started.
`Unable to get events`	A problem occurred while trying to obtain the syslog log entries.	Either there was a problem with one of the components in the path prefix of the log file or named pipe (FIFO) (such as search permission is denied for the component) or there was a connection failure.