Error messages
Error messages provide information about problems that occur while running the probe. You can use the information that they contain to resolve such problems.
The following table describes the error messages specific to this probe. For information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC14-7530).
Error |
Description |
Action |
|---|---|---|
Failed to read alarm |
The probe could not read the incoming event stream. The data may have become corrupt. |
Check that the device is running correctly. |
Flushtime exceeded |
The probe waited for the period specified by the FlushTime property but failed to receive an alarm terminator. The data may have become corrupt. |
Check that the device is running correctly. |
Invalid alarm - no alarm terminator - discarding |
The incoming event stream did not contain the alarm terminator that the probe was expecting. The data may have become corrupt. |
Check that the device is running correctly. |
Unable to compile regexp for string |
A regular expression is incorrectly formed in the rules file. |
Correct the regular expression entry in the rules file. |
Connection closed during login |
The probe was unable to connect to the device. |
Check that the chat in and chat out scripts are set correctly. |
ConvertEscapes: Error allocating memory for octal code Expect: Error allocating memory for buffer Failed to allocate memory |
The probe was unable to allocate memory for the buffer that contains the event being read. This caused the probe to shut down. |
Make more memory available. |
Expect timed out after read_timeout seconds |
When the probe tried to log in to or log out of the host, the expect part of the chat timed out. |
Check that the login name and password are valid for the target host. |
Failed to compile regular expression Unable to compile regexp for reg_expression |
A regular expression is incorrectly formed in the rules file. |
Check the rules file for the regular expression and correct the entry. |
Failed to disconnect from host: host port |
The probe failed to disconnect properly from the device. |
Check that the device and the ObjectServer are running correctly. |
Failed to send alert Failed to send command command Failed to send ProbeWatch message: message Failed to send 'Running...' ProbeWatch message: message |
The probe was unable to send the given alert, command, or ProbeWatch message to the ObjectServer. |
Check that the ObjectServer is available. |
File error: filename not found Filename: file not found Unable to open file: filename - reason |
The probe could not find the named file. |
Check that the file exists and that the permissions are set correctly. |
Have lost all connections - going down |
The probe has lost its connection to the socket and is shutting down. |
Check that the device is running correctly. |
Invalid port number for host: port |
The port number specified does not exist on the host. |
Check the value specified for the Port property in the properties file. |
Only managed to write number out of number characters |
The probe was unable to write the entire alarm to the log file. |
Check that there is sufficient disk space and that the write permissions are correct. |
Read error during expect |
The probe could not process the response from the host during an expect. This could be caused by a problem with the target which caused the connection to time out, or the response from the target could have been corrupted. |
If the probe is configured to reconnect, it will try again to establish the connection. |
SessionProcess failed process |
The probe was unable to process the alert against the rules file. |
Contact IBM Support. |