|
|
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.
Error Message No matching field found for <field name>
Error Message Field `<field name>' not found in status table
Error Message Connection to InfoServer marked DEAD - aborting...
Error Message Failed to set interfaces file location
Error Message Failed to access OMNIHOME directory: <directory name>
Error Message Unknown data type returned from InfoServer
Error Message Failed to initialize
Error Message Failed to create property
Error Message Failed to set property
Error Message Failed to define argument
Error Message Failed to process arguments
Error Message Session create failed - aborting
Error Message Failed to connect - aborting
Error Message Failed to read rules - aborting
The Info Mediator is likely to terminate when these messages are issued.
Error Message Option -propsfile used without argument
Error Message Unknown option: <option name>
Error Message Option <option name> used without argument
Error Message Property <property name> for option <option name> does not exist
Error Message Can't set generic property <property name> via command line
Error Message No extraction data for '<regexp>' - missing ()'s?
Error Message Regexp doesn't match for '<string>'
Error Message Failed to open Properties file: <properties file name>
Error Message Properties file: <error description> at line <line no>
Error Message Unknown property '<property name>' - ignored
Error Message Regular Expression Error: <regexp>
Error Message Failed to open Rules file: <rules file name>
Error Message Rules file: `<error description>' at line <line no>
Error Message Failed to open file: <file name>
Error Message Unexpected value during results processing
Error Message Results processing failed
Error Message Unexpected return from results processing
Error Message OS Error: <error message>
Error Message Server '<server name>': <error message>
Error Message Procedure '<procedure name>': <error message>
Error Message Unknown message level `<message level string>' - using WARNING level
Error Message Could not set <fieldname> field
Error Message Could not send alert
Error Message Error Setting SIGQUIT Handler
Error Message Error Setting SIGINT Handler
Error Message Error Setting SIGTERM Handler
Error Message PropGetValue failed
Error Message CreateAndSet failed
Error Message CreateAndSet failed for attr: <element name>
Error Message SessionProcess failed
Error Message Failed to open message log: <file name>
Error Message SendAlert failed
These messages are issued as warnings and should not cause the Info Mediator to terminate.
Error Message New value for field <field name> truncated to <number>
charactersError Message Failed to set SYBASE in environment
Error Message Type mismatch for property '<property name>' - new value ignored
Error Message Results processing failed
Error Message Failed to retrieve connection status - attempting to continue
Error Message Failed to install Client Message Callback
Error Message Failed to install Server Message Callback
These messages are for information purposes.
Error Message Using stderr for logging
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.
Error Message New value for field <field name> is <value>
Error Message OplInitialise() called more than once
which can only be called once.
Error Message A value for `<string>' doesn't exist in lookup table `<table name>'
Error Message Failed to allocate memory (Requested size was <number> bytes)
Error Message Attempted to free NULL pointer
Error Message Attempted to realloc NULL pointer
Error Message Failed to reallocate memory block at address <hex address> (Requested size was <number> bytes)
Error Message Attempted to duplicate NULL string
Error Message Failed to duplicate string
Error Message Failed to allocate command structure
Error Message Failed to set command query
Error Message Failed to send command
Error Message Failed to allocate context structure
Error Message Failed to initialize Sybase internals: <number>
Error Message Failed to set username
Error Message Failed to set password
Error Message Failed to set appname
Error Message Failed to set hostname
Error Message Failed to connect
Error Message Failed to fetch number of columns
Error Message No columns in result set
Error Message Failed to describe column
Error Message Failed to bind column
Error Message Got a row fail - continuing
Error Message A problem or error has occurred at the Sybase connection or InfoServer connection level.
Error Message Failed to flush alerts before EXIT
Error Message Problem during disconnect before EXIT
Error Message Problem during session destruction before EXIT
Error Message Problem during shutdown before EXIT
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. Table E-1 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:
Error Message Running
Error Message Unable to get events
Error Message Going Down
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Wed Sep 29 18:54:35 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.