|
|
This appendix lists all of the non-Info Mediator specific error messages. See the Info Mediator sections in this manual for more information about Info Mediator specific error messages.
Five classes of error messages exist: Fatal, Error, Warning, Info, and Debug. Each message is usually followed by two bullet points. The first provides further details on the error. The second provides a problem resolution or some indication of where to look for further details on the error.
The Info Mediator automatically terminates when these messages are issued.
No matching field found for <field name>
Field `<field name>' not found in status table
Explanation The rules file being used refers to a field in the format @fieldname which does not exist in the status table.
Action Check the rules file and correct the problem.
Connection to InfoServer marked DEAD - aborting...
Explanation The connection to the Cisco Info Server ceased (and store and forward is not enabled in the Info Mediator).
Action Check whether the Cisco Info Server is available.
Failed to set interfaces file location
Failed to access OMNIHOME directory: <directory name>
Explanation The Info Mediator was unable to locate the interfaces file.
Action Check whether the OMNIHOME environment variable setting is pointing to the correct destination.
Unknown data type returned from InfoServer
Explanation The Cisco Info Server has returned unknown data.
Action Check the Cisco Info Server.
Failed to initialize
Failed to create property
Failed to set property
Failed to define argument
Failed to process arguments
Session create failed - aborting
Explanation Internal errors.
Action Note the message and contact the Help desk. Refer to your support contract for more information about contacting the Help desk.
Failed to connect - aborting
Explanation The Cisco Info Server appears to be unavailable.
Action Check that the Cisco Info Server is running, that the interfaces file on the system where the Info Mediator is installed has an entry for it, and that a networking problem doesn't exist between the two systems.
Failed to read rules - aborting
Explanation The properties or command line options are pointing to a non-existent rules file.
Action Check the command line options and properties and set them to refer to the correct rules file.
The Info Mediator is likely to terminate when these messages are issued.
Option -propsfile used without argument
Explanation The -propsfile command line option must be followed by a parameter specifying where to find the properties file.
Action Check the command line you are using to start the Info Mediator and supply a correct parameter.
Unknown option: <option name>
Explanation An option has been used on the command line to start the Info Mediator which is not supported by the Info Mediator.
Action Check the Info Mediator documentation and the contents of the command line.
Option <option name> used without argument
Explanation The option expects a parameter which was not supplied.
Action Check the Info Mediator documentation and the contents of the command line.
Property <property name> for option <option name> does not exist
Can't set generic property <property name> via command line
Explanation An option in the Info Mediator is not mapped correctly to a property.
Action Refer to your support contract for more information about contacting the Help desk.
No extraction data for '<regexp>' - missing ()'s?
Regexp doesn't match for '<string>'
Explanation A regular expression in the rules file, being used in the extract() function, is missing parentheses, or the string data that is used to extract does not match the regular expression. Extract() is unable to extract data.
Action Check the rules file and correct the problem.
Failed to open Properties file: <properties file name>
Explanation The Info Mediator is unable to open the properties file.
Action Check the properties file or the command line and ensure the parameter is pointing to the correct destination.
Properties file: <error description> at line <line no>
Explanation An error exists in the format of the properties file.
Action Check the properties file at the specified line number and correct the problem.
Unknown property '<property name>' - ignored
Explanation A property specified in the properties file does not exist within the Info Mediator.
Action Check the properties file for the named property and see the Info Mediator documentation for supported properties.
Regular Expression Error: <regexp>
Explanation A regular expression is incorrectly formed in the rules file.
Action Check the rules file for the regular expression and correct the entry.
Failed to open Rules file: <rules file name>
Explanation The rules file for the Info Mediator is not available or incorrectly specified.
Action Check the properties file and/or command line and ensure the rules file is where the properties/command line specifies.
Rules file: `<error description>' at line <line no>
Explanation An error exists in the rules file format/syntax.
Action Check the rules file at the specified line number and correct the problem.
Failed to open file: <file name>
Explanation A file referred to in the rules file (for example, with the table function) does not exist.
Action Check the rules file and ensure the file is available.
Unexpected value during results processing
Results processing failed
Unexpected return from results processing
Explanation A problem exists at the Cisco Info Server.
Action Check the Cisco Info Server.
OS Error: <error message>
Server '<server name>': <error message>
Procedure '<procedure name>': <error message>
Explanation An error exists in the Sybase connection. A subsequent message from the Info Mediator that details the effect of this error should exist.
Unknown message level `<message level string>' - using WARNING level
Explanation The properties or command line specified a message level which is not supported.
Action Check the properties and/or command line and use a supported message level (debug, info, warning, error, fatal).
Could not set <fieldname> field
Explanation The Info Mediator was unable to set a field value. This may be because the Cisco Info Server tables were modified so the default fields are no longer present.
Action Check the Cisco Info Server.
Could not send alert
Explanation The Info Mediator was unable to send an alert (usually an internal alert) to the Cisco Info Server.
Action Check whether the Cisco Info Server is available.
Error Setting SIGQUIT Handler
Error Setting SIGINT Handler
Error Setting SIGTERM Handler
Explanation The Info Mediator was unable to set up a signal handler for either a QUIT, INT, or TERM.
PropGetValue failed
Explanation A required property has not been set.
Action Check the properties file.
CreateAndSet failed
CreateAndSet failed for attr: <element name>
Explanation The Info Mediator is unable to create an element.
Action Refer to your support contract for more information about contacting the Help desk.
SessionProcess failed
Explanation The Info Mediator was unable to process the alert against the rules file.
Action Refer to your support contract for more information about contacting the Help desk.
Failed to open message log: <file name>
Explanation The Info Mediator is unable to open the specified logging file.
Action Check the command line and/or properties file and correct the problem.
SendAlert failed
Explanation The Info Mediator was unable to send an alert to the Cisco Info Server.
Action Check whether the Cisco Info Server is available.
These messages are issued as warnings and should not cause the Info Mediator to terminate.
New value for field <field name> truncated to <number> characters
Explanation A string being copied into an alert field was truncated to fit the field.
Action Check the rules file.
Failed to set SYBASE in environment
Explanation The Info Mediator was unable to override the SYBASE environment variable.
Type mismatch for property '<property name>' - new value ignored
Explanation A property has been set with the wrong data type.
Action Check the properties file and/or command line options to ensure that the property is correctly set.
Results processing failed
Failed to retrieve connection status - attempting to continue
Failed to install Client Message Callback
Failed to install Server Message Callback
Explanation A problem exists with the Cisco Info Server. The Info Mediator will try to continue.
These messages are for information purposes.
Using stderr for logging
Explanation The Info Mediator was unable to open a log file. It is now using stderr.
The debug error messages provide detailed errors and information messages on the internal functioning of the Info Mediator. These messages are aimed at Info Mediator developers, however, they are listed here for completeness.
New value for field <field name> is <value>
Explanation A field value has been set.
OplInitialise() called more than once
Explanation Multiple calls were made to the C Info Mediator API function OplInitialise() which can only be called once.
A value for `<string>' doesn't exist in lookup table `<table name>'
Explanation A value requested from a lookup table is not available. The function in the rules file will return an empty string.
Failed to allocate memory (Requested size was <number> bytes)
Attempted to free NULL pointer
Attempted to realloc NULL pointer
Failed to reallocate memory block at address <hex address> (Requested size was <number> bytes)
Attempted to duplicate NULL string
Failed to duplicate string
Explanation An error or problem has occurred in the memory allocation or string handling components of the Info Mediator library. The library will cope with the problem.
Failed to allocate command structure
Failed to set command query
Failed to send command
Failed to allocate context structure
Failed to initialize Sybase internals: <number>
Failed to set username
Failed to set password
Failed to set appname
Failed to set hostname
Failed to connect
Failed to fetch number of columns
No columns in result set
Failed to describe column
Failed to bind column
Got a row fail - continuing
A problem or error has occurred at the Sybase connection or InfoServer connection level.
Failed to flush alerts before EXIT
Problem during disconnect before EXIT
Problem during session destruction before EXIT
Problem during shutdown before EXIT
Explanation A problem or error has occurred during the shutdown of the Info Mediator.
In certain situations, an Info Mediator generates events of its own. These events can be used to detect problems with the Info Mediator.
ProbeWatch messages are passed through the rules file and are then converted into Cisco Info Center alerts. When possible, all rules should allow for this possibility. shows the ProbeWatch alert elements:
| Element Name | Description |
Identifier | Name of Info Mediator @host name:<summary>. |
Summary | Summary string. |
Node | Node name where the Info Mediator is running. |
Agent | Name of Info Mediator. |
Manager | ProbeWatch. |
Severity | Variable by the severity of the problem. |
FirstOccurrence | Time problem first occurred. |
LastOccurrence | Time problem last occurred. |
The <summary> strings are listed below:
Running
Explanation The Info Mediator has started.
Unable to get events
Explanation The Info Mediator was unable to start.
Action Refer to your support contract for more information about contacting the Help desk.
Going Down
Explanation The Info Mediator is shutting down.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Jun 13 16:57:53 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.