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 Netcool/OMNIbus error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 1. Error messages
Error	Description	Action
`Both FifoName and LogFile properties are set to NULL`	The FifoName property and LogFile property have both been omitted.	Specify a value for either the FifoName property or for the LogFile property.
`Cannot open file/fifo : file_or_fifo_name` `Failed to open fifo_name`	The probe could not open the file specified by the LogFile property or the FIFO specified by the FifoName property.	Check that the location of the file or FIFO has been specified correctly, and that the permissions are set correctly.
`Cannot stat file : file_name`	The probe cannot obtain the status of the specified file.	Check that the file exists and that the permissions are set correctly.
`Date stamp not in recognised format`	The date stamp is not in the format specified by the TimeFormat property.	Adjust the TimeFormat property appropriately.
`CreateAndSet failed for element : value` `Failed to create NSProbe event : event_id` `Failed to get properties` `Failed to set NSProbe event to asynchronous: event_id`	These are internal errors.	Contact IBM Software Support.
`Failed to install signal handlers`	The signal handler failed to initiate when the probe started.	Restart the probe. If the same problem recurs, contact IBM Software Support.
`Failed to destroy event : event_id` `Failed to process event : event_id` `Failed to set event times : event_id`	The probe failed to process the event correctly.	Check that the events in the file specified by the LogFile property or the FIFO specified by the FifoName property are formatted correctly.
`Failed to allocate memory for event` `Failed to allocate memory for syslog line` `Failed to allocate storage for fifo data`	The probe failed to allocate internal storage.	Make more memory available.
`Failed to open syslog pid file : reason`	The syslog PID file specified by the SyslogPIDFile property could not be opened or accessed.	Adjust the SyslogPIDFile property if necessary, and check file permissions.
`Failed to process line`	The probe was unable to process a line of the alarm against the rules file.	Refer to your support contract for information about contacting the help desk.
`Failed to SIGHUP syslog daemon : reason`	The probe failed to send a `SIGHUP` signal to the syslog daemon on startup.	See Sending a SIGHUP signal for details about the steps that you need to perform to use this functionality. If you still receive this message having followed these steps, and if a reread of the syslog configuration file is required, run the probe as a normal user (instead of as the root) and SIGHUP the syslog daemon manually. If the problem persists contact IBM Software Support.
`Failed to translate date stamp into UTC`	An alert was received that did not match the date stamp format expected.	Contact IBM Software Support.
`New event length exceeds 2056 bytes`	The probe generates this warning message when it receives a message that is longer than 2056 bytes. The probe truncates the message to retain the first 2056 bytes and discards the rest.	This message is for information only. No action is required.