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).

Table 1. Error messages
Error	Description	Action
`<Filename> File not found`	The probe could not find the hosts file.	Check that the host file exists and that the permissions are correct.
`Error initializing list`	This is an internal probe error.	Re-run the probe. If that does not solve the problem, refer to your support contract for more information about contacting the help desk.
`Event from <event source> did not match the expected format`	The event was not in the correct format.	Check that you are connected to the correct port.
`Expect timed out after <seconds> seconds`	When the probe tried to log in or out of the host, the expect part of the chat timed out.	Check that the host you are connecting to is running correctly. Check that the login name and password are appropriate for the target host. It may be that the login name was not found and the connection timed out while the target host was trying to validate it.
`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 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 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 <sendchat>`	When the probe tried to log in or out of the host, the send part of the chat failed. The `<SENDCHAT>` indicates the part of the chat message the probe was trying to send when it failed.	Check that the host you are connecting to is running correctly.
`Invalid <message>`	The event was not in the correct format.	Check that you are connected to the correct port.
`Invalid <string>` `Invalid hostfile entry <lineprint>` `Not valid <string>`	A line in the hosts file was formatted incorrectly.	Check the hosts file.
`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 that 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 open file`	The probe was unable to open the hosts file.	Check the hosts file.
`Unable to write to file <filename>` `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.
`Using DEFAULT_READ_TIMEOUT`	The ReadTimeout property has not been set so the probe is using the default value 100ms.	If you want to override the default setting, specify an alternative value using the ReadTimeout property.