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
`Discarding event - Failed to parse`	The event is considered invalid as it does not have a line delimiter.	The line delimiter (\n) is missing in the event.
`Discarding invalid line between alarms`	A line from the alert audit file is not in the correct format.	Check that the Motorola MUNO is running correctly.
`Discarding on read failure buffer`	The probe discarded a partially read event from its buffer following a read failure.	The probe is unable to complete reading an event due to a problem with the connection to the device; for example, the device has dropped the connection to the probe.
`Disconnected from system due to shutdown signal`	The probe has disconnected from the host.	A shutdown signal was sent to the probe.
`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 connection failure.
`Failed to send Probewatch message ProbeWatch messages`	The ProbeWatch messages are not reaching the ObjectServer.	There this a problem either with the probe or the ObjectServer.
`Flushtime exceeded while buffering event, flushing event`	There was a problem while buffering and sending the events to the object server.	The problem occured because only partial data was receieved.
`Going Down ...`	The probe is shutting down.	The probe is shutting down after performing the shutdown routine.
`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.
`Running ...`	The probe is running normally.	The probe has just been started.
`Time (in seconds) without activity before sending an Inactivity ProbeWatch message`	The idle time for which the probe waits for the events when the conenctivity is lost.	The time exceeded the idle time for which the probe waits to receive the events.