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 TSM. For information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).
Error |
Description |
Action |
|---|---|---|
filename: file not found |
The TSM could not find the hosts file specified in the properties file. | Check the HostsFile entry in the properties file, and amend if necessary. |
Bounce search failed for - hostname:port_number Resynch search failed for - hostname:port_number |
The TSM could not find the connection specified by the host and port parameters of the bounce command. | Check that you have specified the correct hostname and port number. |
Error occurred while reading hostfile: filename Error reading host file filename |
The TSM could not open the hosts file for reading. | Check that you have specified the correct filename and that the permissions of the file and directories are set correctly. Amend if necessary. |
Expect timed out after number seconds |
When the TSM 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 valid for the target host. |
Failed to add line to multi-line end-of-day report - ignoring report |
The TSM could not write to the multi-line end of day report and so the report will not be generated. | Check that the permissions on the report allow it to be written to. |
Failed to create multi-line end-of-day report - exiting |
The TSM failed to generate the multi-line end of day report. | Check that the permissions on the report allow it to be written to. |
Failed to create new command port connection |
The TSM could not set up a command port. | Check that you have appropriate permissions to run the TSM. |
Failed to initialize failover Failed to start failover - aborting |
The application failed to start. | Check that both the master and slave are running and that the failover configurations are correctly set on both the master and the slave. |
Failed to initialize TSM API |
The TSM API failed to initialize. This is an internal error. | Try to rerun the TSM. If this recurs, refer to your support contract for details about contacting IBM Software Support. |
Failed to parse message - exiting |
The TSM was unable to parse the message received from the host. | The incoming data may be corrupt. Check that the device is running properly. |
Failed to save PID to file |
The TSM could not save the process ID number to the file specified. | Check the permissions of the PID file and corresponding directories, and amend if necessary. |
Failed to send command command Failed to send message |
The TSM failed to send the command specified to the device. | Check that the connection to the host is still active. |
Failed to set up command port port |
The TSM cannot start due to a problem setting up the port specified. | Check that the port number specified was positive, not a reserved number, and that it is not in use by another application. |
HeartbeatInterval property may not be negative (number) HeartbeatTimeout property may not be negative (number) ReconnectionInterval property may not be negative (number) ResynchInterval property may not be negative (number) |
The property specified has been set to a negative value. | Change the property to a positive value. |
Hostfile entry entry_number: Failed to retrieve host value Hostfile entry entry_number: Failed to retrieve port value |
The hosts file entry specified contains no value for the host property. | Specify a host name for the hosts file entry specified. |
Hostfile entry entry_number: Chatin property set, but no chatout! HostsFile entry entry_number: ResynchCommand property set, but no ResynchInterval! |
The hosts file entry specified contains a value for the ci property but no corresponding value for the co property. | Specify a chatout string for the hosts file entry specified. |
Hostfile entry entry_number: Parse error ':' expected |
The hosts file entry specified contains no colon. | Add a colon to the hosts file entry specified. |
HostsFile entry entry_number: Heartbeat Interval not set! |
The hosts file entry specified contains no value for the hi property. | Specify value for the heartbeat interval for the hosts file entry specified. |
HostsFile entry entry_number: Heartbeat Timeout not set! |
The hosts file entry specified contains no value for the ht property. | Specify a value for the heartbeat timeout for the hosts file entry specified. |
HostsFile entry entry_number: HeartbeatResponse not set! |
The hosts file entry specified contains no value for the hr property. | Specify a value for the heartbeat response for the hosts file entry specified. |
process_chat_string: Error allocating memory for token AllocateNewNode: Error allocating new node ReadHostEntry: Error allocating memory for entry ReadHostEntry: Error allocating memory for line ReadHostFile: Error allocating memory for socket node ReadHostFile: Error allocating memory for token |
The TSM failed to allocate internal storage. | Make more memory available. If this fails, contact the help desk. |
Read error during chat |
The TSM could not process the response from the host. | Check that the device is running currently. |
Unable to compile HeartbeatResponse regexp for: heartbeat_response |
The TSM was unable to compile the heart beat response required by the TSM. | Check that the HeartbeatResponse property contains a valid regular expression. |
Unable to compile regexp for heartbeat_response Unable to compile regexp for string |
The device was unable to compile the heart beat response required by the TSM. | Check that the HeartbeatResponse property contains a valid regular expression. |
Unable to send HeartbeatString |
The TSM could not send a Heartbeat string to the device. | Check that the connection to the host is still active. |
Unable to send ResynchCommand |
The TSM could not send a Resynch command to the device. | Check that the connection to the host is still active. |
Unknown expect connection error |
An unknown error occurred whilst the TSM was receiving the expect part of a chat script. | Refer to your support contract for details about contacting IBM Software Support. |