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 |
|---|---|---|
| Buffer size exceeded. Registering read error | Amount of data read is more than the buffer size. |
Check the size of the buffer. |
| ConvertEscapes: Error allocating memory for octal code | The probe was unable to allocate memory for the buffer that contains the event being read. This caused the probe to stop. |
Make more memory available. |
| Error initialising listError initialising internal probe list | This is an internal probe error. |
Rerun the probe. If that does not solve the problem, contact IBM Software Support. |
| Expect timed out after number seconds | The probe was unable to connect to the remote host. |
Check the remote host is available. |
| Expect: Error allocating memory for buffer | There is not enough memory available. |
Make more memory available. |
| Failed to disconnect from host: hostname port | The probe failed to disconnect connect properly from the device. |
Check that the device and the ObjectServer are running correctly. |
| Failed to parse text block | The probe was unable to parse the data specified. |
This is an internal error. Contact IBM Software Support. |
| Failed to read from socket - disconnecting | This is an internal error. |
Contact IBM Software Support. |
| Failed to retrieve value for property: propertyname | The probe failed to retrieve a value for a required property. |
Check that the properties file contains the required property and that it has been specified in the appropriate format. |
| Failed to rollover InvalidAlarmLogFile | The probe was unable to open another alarm log file to write to. |
Check that there is sufficient disk space and that the permissions are correct. |
| Failed to send alert | The probe was unable to send an alert (usually an internal alert) to the ObjectServer. |
Check that the ObjectServer is available. |
| Have lost all connections - going down | The probe has lost its connection to the socket and is stopping. |
Check that the device is running correctly. |
| 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. |
| Too many tokens in hostfile entry | A line in the hosts file was formatted incorrectly. There are too many entries on the line. |
Check the hosts file. |
| Unable to write to file filenameOnly managed to write number out of number characters | The probe was unable to write to the file specified. |
Check that the permissions of the file are set correctly. |