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, (SC14-7530).

Table 1. ProbeWatch messages
ProbeWatch message	Description	Triggers/causes
`Connection attempted ... (host, port no.)`	The probe is trying to establish a connection to the host.	The probe tried to establish a connection to the host.
`Connection failed ... (host, port no.)`	The probe has failed to establish a connection to the host.	General connection failure due either to an incorrect setting of the Host or Port property, or the host refusing a connection request from the probe.
`Connection lost ... (host, port no.)`	The probe has lost the connection to the host.	The device dropped the connection to the probe.
`Connection succeeded ... (host, port no.)`	The probe has successfully established a connection to the host.	The probe successfully established a connection to the host.
`Disconnected from system due to shutdown signal`	The probe has disconnected from the host.	A shutdown signal was sent to the probe.
`Disconnecting from system due to Inactivity alarm ...(host, port no.)`	The probe has disconnected from the device.	The device was silent for the period specified by the Inactivity property. If you want the probe to time out less frequently, increase this value.
`Disconnection attempted ... (host, port no.)`	The probe is attempting to disconnect from the host.	The probe is shutting down or has lost the connection.
`Disconnection failed ... (host, port no.)`	The probe has failed to disconnect cleanly from the host.	There has been a corruption of the memory location storing the connection details.
`Disconnection succeeded ... (host, port no.)`	The probe has disconnected from the host.	The probe shut down or lost the connection.
`Failed to get events`	A problem occurred while receiving events.	Either there was a problem initializing the connection due to insufficient memory or (if this message was sent after some events had been parsed) there was a license or a connection failure.
`Failed to get license ... (host, port no.)`	The probe is unable to obtain a license for the connection to the host.	Either the license server is down or there are insufficient licenses in the server.
`Have lost all connections - going down`	The probe is shutting down because all of its connections have been deactivated.	The number of times that the probe has attempted reconnection for each of its connections has exceeded that specified by the ReconnectionAttempts property.
`Heartbeat response received ... (host, port no.)`	A heartbeat response has been received within the period specified by the ResponseTime property.	A response matching the ResponseTime property in the props or hosts file has been received.
`Heartbeat response timed out ... (host, port no.)`	A response to the heartbeat string has not been received for the period specified by the ResponseTime property.	The probe has not received the expected response or an event and so is disconnecting from and reconnecting to the host.
`Heartbeat sent ... (host, port no.)`	A heartbeat string has been sent from the probe to the host.	The probe has not received an event from the device for the period specified by TimeoutSendingRequest property.
`License failure - going down`	The license server could not be reached.	Either the license has expired, the license server has gone down, or the connection to the license server has been lost.
`Login attempted ... (host, port no.)`	The probe is trying to log in to the host.	The probe is trying to log in to the host.
`Login failed ... (host, port no.)`	The probe has failed to log in to the host.	The probe has encountered a problem while logging in using ChatinString property.
`Login succeeded ... (host, port no.)`	The probe has logged in to the host.	The probe has logged in to the host.
`Logout attempted ... (host, port no.)`	The probe is trying to log out from the host.	The probe has received a command to shut down or has received the bounce command from the command port.
`Logout failed ... (host, port no.)`	The probe has failed to log out from the host.	The probe has encountered a problem while logging out using ChatoutString property.
`Logout succeeded ... (host, port no.)`	The probe has logged out from the host.	The probe has logged out from the host.
`Message Received from GIF/FM`	The probe has received a fatal message from the GIF/FM process.	Details of the problem that caused the fatal message are included in the message.
`Synchronisation complete`	The probe has completed synchronisation.	The probe received a complete event, but not the `END OF BLOCK` string.
`Unable to write recovery time to file`	The probe was unable to write to the recovery file.	Permissions for the recovery flag may not be set correctly.