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 Netcool/OMNIbus error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.
Error |
Description |
Action |
|---|---|---|
| Buffer size exceeded. Registering read error. Discarding line: linenumber | The event read by the probe is larger than the value of the MaxEvents property. This caused the probe to discard the specified line. |
Make more memory available. |
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. |
| CreateAndSet failed for host | The probe is unable to create an element. |
Refer to your support contract for details about contacting IBM Support. |
Discarding invalid data between alarms Discarding line: linenumber |
A line from the alert audit file is not in the correct format. |
Check that the probe is running correctly. |
| Disconnect from ObjectServer failed: hostname | The probe failed to disconnect properly from the ObjectServer. |
Check that the ObjectServer is running correctly. |
Error initialising internal probe list Error initialising list |
This is an internal probe error. |
Rerun the probe. If that does not solve the problem, refer to your support contract for details about contacting IBM Support. |
| Error reading host file hostfilename | The probe could not open the hosts file for reading. |
Check the permissions for the hosts file and directories, and amend if necessary. |
| 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 | Unable to allocate memory for the buffer that contains the event being read. This caused the probe to terminate. |
Make more memory available. |
Failed to allocate memory |
The probe failed to allocate internal storage. |
Make more memory available. |
| Failed to compile regular 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 create and set: $Host-> element | The probe is unable to create an element for the host. |
Refer to your support contract for details about contacting IBM Support. |
| Failed to create and set: $Port-> element | The probe is unable to create an element for the port. |
Refer to your support contract for details about contacting IBM Support. |
| Failed to disconnect from host: hostname port | The probe failed to disconnect properly from the device. |
Check that the device and the ObjectServer are running correctly. |
| Failed to parse first line of event | The probe failed to parse the incoming data. The incoming data may be corrupt. |
Check that the device is running properly. |
| Failed to parse text block | The probe was unable to parse the data specified. |
This is an internal error. Refer to your support contract for details of contacting IBM Support. |
| Failed to read from socket - disconnecting | The probe had successfully logged into the target host, but something interrupted the connection. |
Check that the target host is working correctly. |
| 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 Failed to send command string |
The probe was unable to send an alert to the ObjectServer. |
Check that the ObjectServer is available. |
Failed to send message ProbeWatch message Failed to send ProbeWatch message: message |
The probe was unable to send the specified ProbeWatch message to the ObjectServer. |
Check that the ObjectServer is available. |
| Failed to send string | The probe failed to send the message specified to the device. |
Check that the connection to the host is still active. |
| Feature has expired: featurename | The license for the feature specified has expired. |
Update the license for the feature using the Netcool License Server. |
File error: filename not found File error: ReadHostFile File error: ReReadHostFile filename: file not found |
The probe could not find the file specified. |
Check that the host file exists and that the permissions are correct. |
| First line is invalid (not enough tokens): invalid_line | First line from the alert audit file is not in the correct format. |
Check that the probe is running correctly. |
| 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. |
| Hostfile entry is not valid: linenumber | A line in the hosts file was formatted incorrectly. |
Check the hosts file. |
| Invalid port number for host: port | The port number specified does not exist on the host. |
Check the value specified for Port in the properties file. |
| License heartbeat failed | 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. |
| Only managed to write number out of number characters | The probe was unable to write to the alarm log file. |
Check that there is sufficient disk space and that the permissions are correct. |
| OplPropGetValue() failed: 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. |
| Read error during expect | The probe could not process the response from the host. |
Check that the device is running currently. |
| SendCommand: Error allocating memory for command | Unable to allocate memory for buffer that contains the event being read. This caused the probe to terminate. |
Make more memory available. |
| SessionProcess failed internal error code | The probe was unable to process the alert against the rules file. |
Refer to your support contract for details about contacting IBM Support. |
| 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 compile regexp for string | A regular expression is incorrectly formed in the rules file. |
Check the rules file for the regular expression and correct the entry. |
| Unable to extract $MSN from event | Extract() is unable to extract $MSN element from the alarm data. |
Check the rules file and correct the problem. |
| Unable to get events | The probe was unable to get any events from the system. |
Check that the system is running correctly. |
| Unable to open file: filename - filename | The probe could not open the file specified. |
Check that the permissions are set correctly on the file specified. |
| Unable to send HeartbeatString | The probe could not send a heartbeat string to the device. |
Check that the connection to the host is still active. |
| Unable to write to file filename | The probe could not write to the file specified. |
Check the permissions on the file specified. |
| Unknown system error! | An unknown error occurred while the probe was receiving the data. |
Refer to your support contract for details about contacting IBM Support. |