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
`All agent connections are dead - aborting`	The connections to agents have ceased (and store and forward is not enabled in the probe).	Check that the BMC Patrol system is available.
`Failed to create/set: token name`	The probe is unable to create an element.	Contact IBM Software Support.
`Failed to install SIGUSR1 handler`	The probe was unable to install a signal handler for either a `QUIT`, `INT` or `TERM`. The probe will try to continue, however any further signal handling will result in an error on exit.	Contact IBM Software Support.
`Failed to parse host name on line host name` `Failed to parse password on line password` `Failed to parse port on line line number` `Failed to parse username on line username`	The probe was unable to parse the data specified.	Contact IBM Software Support.
`Failed to perform initial stat of PatrolDefFile!`	The probe was unable to perform the initial `stat` on the `patrol.def` file.	Check that the file exists and that the permissions are correct.
`Failed to process arguments`	Internal error.	Contact IBM Software Support.
`FAILED TO RECOVER`	The recovery file could not be found or could not be accessed and so the tailing begins from the current line value.	Check that the RecoveryFileName property is set correctly and that the user running the probe has read and write permissions over the file.
`Failed to send alert`	The probe was unable to send an alert (usually an internal alert) to the ObjectServer.	Check that the ObjectServer is available.
`Failed to set FirstOccurrence` `Failed to set LastOccurrence`	Some application has affected the operation of the probe.	Rerun the probe.
`Failed to stat PatrolDefFile` `Failed to perform initial stat of PatrolDefFile`	The probe cannot obtain the status of the file specified.	Check that the file exists and that the permissions are set correctly.
`Failed to stat PatrolDefFile!`	The probe was unable to perform a `stat` on the `patrol.def` file.	Check that the file exists and that the permissions are correct.
`gethostbyaddr(): failed to find host host name` `gethostbyname(): failed to find agent host host name` `Hostname resolution problems`	The probe was unable to log on to the host.	Check that the properties are set correctly.
`gethostbyaddr(): failed to find host hostname`	The probe was unable to find the host specified in the `patrol.def` file.	Check that the specified host is running and reachable.
`gethostbyname(): failed to find host HostName`	The probe was unable to find the host specified in the `patrol.def` file.	Check that the specified host is running and reachable.
`Incomplete final line in line number`	A line from the alert file is not in the correct format.	Check that the BMC Patrol is running correctly.
`Invalid port on line` `Patrol Agent host is unreachable`	There is a problem with your machine, the network, or the probe configuration.	Check that there are no problems with your network and that you configured the correct port number in the probe properties file.
`Memory problems` `Out of memory`	A memory allocation problem occurred.	Make more memory available.
`No agents configured in Patrol Def file` `No patrol agents configured - aborting` `Patrol Def file errors`	The BMC Patrol definition file does not contain the agent details.	Add the agent details in the BMC Patrol definition file.
`No patrol agents configured - aborting`	The agents have not been configured or have been incorrectly configured.	Check that the definition file exists and that the agents to which the probe connects have been correctly configured.
`No patrol agents configured - aborting`	There are no BMC Patrol Agents defined in the `patrol.def` file.	Add some BMC Patrol Agents to your `patrol.def` file.
`Patrol API problems`	Internal errors.	Contact IBM Software Support.
`Probe has been given Unknown RecoveryMode Recovery Mode Value. Defaulting to NORMAL MODE` `Unknown RecoveryMode Recovery Mode Value. Defaulting to NORMAL MODE`	As the given value for the RecoveryMode property is incorrect, the probe reverts back to the `NORMAL` mode.	Correct the RecoveryMode value in the properties file.
`PropertyName is greater than the maximum` `PropertyValue of Number Milliseconds - using maximum`	The property specified in the properties file or at the command line is greater than the maximum permitted. The maximum permitted value is used.	Correct the entry in the properties file.
`PropertyName is less than the minimum PropertyValue of Number Milliseconds - using minimum`	The property specified in the properties file or at the command line is lower than the minimum permitted. The minimum permitted value is used.	Correct the entry in the properties file.
`Rules processing failed: errordescription`	There is an error in the rules file format or syntax.	Check the rules file and correct the problem.
`Session create failed – aborting`	Internal errors.	Contact IBM Software Support.
`The number of agents is greater than the recommended absolute maximum of maximum limit` `Too many agents configured in Patrol Def file`	The number of agents specified in the BMC Patrol definition file is more than the default limit.	Reduce the number of agents in the BMC Patrol definition file to the limit shown in the error message.
`Unable to ping Host: HostName Port: PortValue Responded With: errordescription`	The probe lost its connection to the server.	Check that the BMC Patrol is running correctly on the socket shown in the error message.
`Unable to read recovery file: filename` `Unable to write recovery file: filename`	The probe cannot open, read, or reset the recovery file.	Check that the file exists and that the permissions are set correctly.