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, (SC23-6373).

Table 1. Error messages
Error	Description	Action
`Error initialising alarm list` `Error initialising node list`	This is an internal probe error.	Rerun the probe. If that does not solve the problem, contact IBM Software Support.
`Error reading host file`	There was a problem reading the host file.	Check that the host file exists and is formatted correctly. Check that the permissions are correct.
`Error reading syntax file`	There was a problem reading the syntax file.	Check that the syntax file exists and the permissions are correct.
`Expect timed out after <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 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 hostfile entry, too many tokens`	A line in the hosts file was formatted incorrectly. There are too many entries on the line.	Check the hosts file.
`Invalid syntax file entry <lineprint>`	A line in the syntax file was formatted incorrectly. The <LINEPRINT> part of the error message indicates the line.	Check the syntax 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 tries again to establish the connection.