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 |
|---|---|---|
Connection closed during login |
The probe was unable to connect to the GIF/FM process. |
Check that the chat in and chat out scripts are set correctly. |
ConvertEscapes: Error allocating memory for octal code |
The probe was unable to allocate memory for buffer that contains the event being read. This caused the probe to terminate. |
Make more memory available. |
CreateAndSet failed for element |
The probe is unable to create the specified element. |
Contact IBM Support. |
Encountered GIF/FM error - disconnecting |
The probe is about to disconnect due to GIF/FM error. |
Check that the device is running correctly. |
Error initialising list |
This is an internal probe error. |
Rerun the probe. If that does not solve the problem, contact IBM Support. |
Error reading host file filename |
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 |
When the probe tried to log in to 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. |
Expect: Error allocating memory for buffer |
The probe failed to allocate sufficient memory. |
Make more memory available. |
Failed to allocate memory |
The probe failed to allocate sufficient memory. |
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: element |
The probe is unable to create an element. |
Contact IBM Support. |
Failed to disconnect from host: string integer |
The probe failed to disconnect properly from the device. |
Check that the device and the ObjectServer are running correctly. |
Failed to install signal handler |
The probe was unable to install a signal handler for the signal type specified. The probe will try to continue; however, any further signal handling will result in an error on exit. |
Contact 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: property |
The probe failed to retrieve a value for the specified 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 roll over to the next InvalidAlarmLogFile. |
Check that there is sufficient disk space and that the permissions are correct. |
Failed to send command command |
When the probe tried to log in to or out of the host, one command in the chat failed. |
Check that the host you are connecting to is running correctly. |
Failed to send ProbeWatch message: message |
The probe was unable to send the alert, command, or ProbeWatch message specified to the ObjectServer. |
Check that the ObjectServer is available. |
Failed to Set value for LastOccurrence |
The probe could not set value for the LastOccurence field. |
Contact IBM Support. |
File error: filename not found |
The probe could not find the file specified. |
Check that the file exists and that the permissions are set 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. |
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. |
Message Received from GIF/FM |
The probe has received a fatal message from the GIF/FM process. |
Action should be taken as per the description included in the error message. |
No backup host specified |
There is no backup host specified in the host file. |
If appropriate, add backup host in the host file. |
No recovery timestamp available. |
The recovery timestamp is not available from the recovery file. |
No action required. |
OplPropGetValue() failed for: property |
The probe was unable to connect to the Siemens SMN-OS system, because the property specified contains an incorrect value. |
Check that the properties file contains the required property and that it has been specified in the appropriate format. |
Process Failure Threshold reached |
The number of process failures has reached the specified maximum limit. |
Check that the device is running correctly. |
PropGetValue failed: RecoveryFile |
The probe failed to retrieve a value for the specified property. |
Check that the properties file contains the required property and that it has been specified in the appropriate format. |
Message Received from GIF/FM PROTOCOL VIOLATION Received from GIF/FM, Previous request discarded TEMPORARY FAILURE Received from GIF/FM - Resending request |
The probe has received a non-fatal message from the GIF/FM process. |
No action is required. |
PsockTimeout |
A socket timeout error occured while trying to read event. |
Check that the host you are connecting to is running correctly. |
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. |
Read failure |
A socket error occured while trying to read events. |
Check that the connection to the device is still up. |
REGEXP: sub number does not exist |
A regular expression has not been specified. |
Check the rules file and correct the problem. |
SendCommand: Error allocating memory for command |
There is not enough memory available. |
Make more memory available and restart the probe. |
SessionProcess failed session |
The probe was unable to process the alert against the rules file. |
Contact IBM Support. |
Hostfile entry is not valid linenumber |
Too many tokens in hostfile entry |
A line in the hosts file was formatted incorrectly. Check the hosts file. |
Unable to compile regexp for expect_str |
A regular expression is incorrectly formed in the rules file. |
Check the rules file for the regular expression and correct the entry. |
Unable to get events |
The probe was unable to get any events from the device. |
Check that the device is running correctly. |
Unable to open file: filename - errorstring |
The specified file could not be created. |
Check that there is enough disk space to save the file. Exact reason is indicated in the error string message. |
Unable to open stream capture file file |
The probe could not open the file specified. |
Check that the permissions are set correctly on the file specified. |
Unable to write record file: Recovery_file |
The probe was unable to write to the recovery file. |
Check that the permissions of the recovery file are set correctly. Unable to write to file filename |
Only managed to write number out of number characters |
The probe could not write to the file specified. |
Check that there is sufficient disk space and that the write permissions are correct. |