| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
SNMP SubAgent User's Guide (UNIX) |
![[-]](/dwicons/i_colpse.gif)
| Appendix A: Messages |
This appendix contains error messages generated by the Subagent. There are four categories of messages:
The following sections describe the message format and the Subagent messages.
Every message has format:
sybagt: date_and_time
.... message_number: message_text
where date_and_time identifies when the Subagent created the message, message_number uniquely identifies the error, and message_text is the text of the message. For example:
sybagt: June 6, 1995
.... C1001: $SYBASE environment variable is not defined
Is a configuration error describing the SYBASE environmental variable.
C1001: $SYBASE environment variable is not defined
When you started the Subagent, the SYBASE environmental variable was not set. This error causes the Subagent to terminate.
Set SYBASE and restart the Subagent.
C1002: $SYBSNMP environment variable is not defined
When you started the Subagent, the SYBSNMP environmental variable was not set. This error causes the Subagent to terminate.
Set SYBSNMP and restart the Subagent.
C1003: cs_ctx_alloc() failed - Could be mixed versions of CT-Library
The Subagent could not allocate required resources. The most common reason for this error is that you are using mixed versions of Open ClientTM Client-LibraryTM. This error causes the Subagent to terminate.
When you install the Subagent, you install Open Client Client-Library under the $SYBSNMP directory. If you encounter this error, you should reinstall the Subagent. When the installation procedure prompts you to overwrite files, respond no. If you respond yes, the installation procedure may overwrite existing configuration files.
C1004: ct_init() failed
The Subagent could not initialize required resources. The most common reason for this error is that you are using mixed versions of Open Client Client-Library. This error causes the Subagent to terminate.
When you install the Subagent, you install Open Client Client-Library under the $SYBSNMP directory. If you encounter this error, you should reinstall the Subagent. When the installation procedure prompts you to overwrite files, respond no. If you respond yes, the installation procedure may overwrite existing configuration files.
C1005: Cannot open interfaces file: interfaces_file
This is a fatal error because the Subagent could not open the interfaces file.
If you used the -I flag, make sure that the path is correct and that the directory contains a valid interfaces file. If you did not use the -I flag, make sure that the $SYBASE directory contains a valid interfaces file. Also, check the file permissions. You typically start the Subagent as "root", therefore "root" must have read permission. Although "root" generally has read permission on files, some NFS mounted file systems do not recognize "root".
C1006: Operating system error: <message>
This message appears after message I3003. This problem often occurs when there are networking errors or a failure to locate some needed resource.
None.
C1007: rdbmsSrvEntry duplicate attempted
Attempt to add two servers with the same applIndex. Because of this, the Subagent cannot make an entry in the rdbmsSrvTable.
Check snmp.ini and make sure that every applIndex is unique.
C1008: DbIndex # is a duplicate
DbIndexes must be unique for a given host machine. The Subagent attempts to keep all DbIndexes unique and this error should not occur.
None.
C1009: DbIndex # is a duplicate
DbIndexes must be unique for a given host machine. The Subagent attempts to keep all DbIndexes unique and this error should not occur.
None.
C1010: ini_file: num error encountered
num identifies the total number of errors encountered while parsing the initialization file identified by ini_file (typically snmp.ini).
Identify and correct each initialization file error.
C1011: ini_file, num applIndex value must be between 1 & 99999
ini_file identifies the initialization file and num is the offending number. ApplIndex values must be in the range of 1 to 99999.
Shut down the Subagent and change the applIndex to a value within this range. See "Format of snmp.ini" for more information on server entries in the initialization file.
C1012: Cannot open file tmp_ini_file
The Subagent cannot open the temporary initialization file specified by tmp_ini_file. The Subagent uses this file for the temporary storage of information. This is not a fatal error, but the Subagent cannot update the initialization file until you correct the error.
$SYBASE/snmp.ini.tmp is the default temporary initialization file. Check this file or use the -c flag to specify a different temporary file.
C1013: InitSubagent:SNMP initialization error. Is Master agent installed?
The Subagent can not register itself with the master agent.
You must start the master agent before starting the Subagent. Make sure that the master agent is running. If it is not, stop the Subagent, start the master agent, and restart the Subagent.
C1014: server_name is not in interfaces file.
The server server_name is in the initialization file but it is not in the interfaces file. The Subagent does not monitor servers if it cannot find an entry for it in the interfaces file.
Check the name of the server in the initialization file and in the interfaces file. Make sure that they match.
C1015: SNMP Subagent cannot login to: server_name -login name: login_name or password is bad
The Subagent is not able to login to the server using the login_name login and password.
Check that the login_name login and password are correct and that the server has a valid account with that name and password.
C1016: ct_cmd_alloc failed
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation for more information.
C1017: server_name applIndex = num is a duplicate. Row in applTable not created
The Subagent cannot monitor the server server_name in the initialization file because its applIndex number is not unique.
Shut down the Subagent and modify the server entry in the initialization file so that it has a unique applIndex.
Note: A special case exists if you are running a sub-agent from another vendor which also supports the application table. Make sure that the applIndex numbers are unique for all entries. If there are duplicates among different sub-agents, the error will go undetected and the Subagent cannot monitor some servers.
C1018: ini_file, num DbIndex value must be between 1 & 255
There is an invalid DbIndex number in the initialization file ini_file.
Normally, the Subagent makes sure that each DbIndex value is unique. If this problem persists, shut down the Subagent, edit the initialization file, and remove all database entries. Then, restart the Subagent.
C1019: LongSleep: num is out of limits
The LongSleep time specified by num is outside allowable limits. The Subagent uses the default value.
None.
C1020: ShortSleep: num is out of limits
The ShortSleep time specified by num is outside allowable limits. The Subagent uses the default value.
E2001: applIndex_value, rdbmsSrvParamName_value was not created in rdbmsSrvParamTable
The Subagent cannot create a row in the rdbmsSrvParamTable because of insufficient memory or because a duplicate entry was attempted.
None.
E2002: applIndex_value, rdbmsSrvLimitedResouceName_value was not created in rdbmsSrvLimitedResouceTable
The Subagent did not create a row in the dbmsSrvLimitedResouceTable because of insufficient memory or because it is a duplicate.
None.
E2003: rdbmsDbIndex_value,rdbmsParamName_value was not created in rdbmsDbParamTable
A row in the dbmsDbParamTable was not created either because of insufficient memory or because it is a duplicate.
None.
E2004: rdbmsDbIndex_value, segment_name_value was not created in rdbmsDbLimitedResourceTable
A row in the dbmsDbLimitedResouceTable was not created either because of insufficient memory or because it is a duplicate.
None.
E2005: applIndex_value was not created in RdbmsSrvTable
A row in the dbmsSrvTable was not created either because of insufficient memory or because it is a duplicate.
None.
E2006: applIndex_value row was not created in RdbmsSrvInfoTable
A row in the dbmsSrvInfoTable was not created either because of insufficient memory or because it is a duplicate.
None.
E2007: DbIndex_value,applIndex_value was not created in rdbmsDbTable; in dbPinger
A row in the rdbmsDbTable was not created either because of insufficient memory or because it is a duplicate.
None.
E2008: CT- Library failed to install client callback handler
Open Client Client-Library failed to install callback handler. This is a fatal error.
See your Open Client Client-Library documentation for more information.
E2009: CT- Library failed to install server callback handler
Open Client Client-Library failed to install callback handler. This is a fatal error.
See your Open Client Client-Library documentation.
E2010: ct_config error failed when setting timeouts
This is an Open Client Client-Library error. This error causes the Subagent to terminate.
See your Open Client Client-Library documentation for more information.
E2011: Recursion detected in message handler
If you can reproduce this message, it is a bug. This is a fatal error.
None. Save the log file messages and call Sybase Technical Support.
E2012: ct_res_info failed.
Open Client Client-Library error while retrieving results. Could be a failed connection.
See your Open Client Client-Library documentation for more information.
E2013: bind_data: too few columns returned
The Subagent was expecting more columns in the managed server. Perhaps this is not a supported SQL Server.
None.
E2014: ct_bind failed
Encountered Open Client Client-Library error while retrieving results. Could be a failed connection.
See your Open Client Client-Library documentation for more information.
E2015: ct_cancel failed.
The Subagent received an unexpected result from the server and attempted to cancel the query. The cancel failed.
None.
E2016: ct_results failed
This is an Open Client Client-Library error. A command to the server or a result set from the server failed. This could be due to a server going down or an unstable connection.
See your Open Client Client-Library documentation for more information.
E2017: rdbmsSrvEntry allocation error.
An allocation operation failed. Probably an insufficient memory problem.
None.
E2018: Unable to create new ApplEntry
An allocation operation failed. Probably an insufficient memory problem.
None.
E2019: ct_con_alloc failed
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation.
E2020: ct_con_props CS_USERNAME failed
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation.
E2021: ct_con_props CS_PASSWORD failed
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation for more information.
E2022: ct_con_props CS_APPNAME failed
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation for more information.
E2023: ct_con_props CS_HOSTNAME failed
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation for more information.
E2024: ct_con_props CS_PACKETSIZE failed
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation for more information.
E2027: Invalid OperStatus
Internal logic error.
None.
E2028: A connection has terminated unexpectedly rdbmsSrvInfoEntry
A connection has unexpectedly terminated.
None.
E2029: ct_command failed in rdbmsSrvInfoEntry
This is an Open Client Client-Library error that could be due to an unstable connection or temporary inconsistency.
See your Open Client Client-Library documentation for more information.
E2030: A connection has unexpectedly terminated in rdbmsSrvInfoEntry.seldom
A connection has unexpectedly terminated.
None.
E2031: ct_command failed in rdbmsDbEntry_seldom
This is an Open Client Client-Library error that could be due to an unstable connection or temporary inconsistency.
See your Open Client Client-Library documentation for more information.
E2032: cs_loc_alloc failed during initialization
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation for more information.
E2033: cs_locale failed during initialization.
This is an Open Client Client-Library error.
See your Open Client Client-Library documentation for more information.
I3001: Shutting down.
Subagent has terminated.
None.
I3002: server_name server timed out after number seconds
The named server server_name did not respond within number seconds.
The Subagent will retry the command.
I3003: Client msg: LAYER = (num) ORIGIN = (num) SEVERITY = (num) NUMBER = (num)
error_message
This is a general trace routine which reports all Open Client Client-Library client-side error messages, where error_message is the actual string.
See your Open Client Client-Library documentation for more information.
I3004: Terminating a connection
Terminating a connection to a server, because the server is giving improper responses. For example, the server has shut down or the connection has been broken.
The agent will attempt a new connection at a later time.
I3005: Server message number=num ,Severity=num, Line=num"
A message/error from the server.
See your server documentation for more information.
I3006: From server server_name: server_message
This is a follow on message from I3005 and contains the server_ message.
Consult the SQL Server (or open server application) for the meaning of these messages.
I3008: DbIndex DbIndex_value Database was dropped
A database was dropped from the server.
None.
S4001:snmp.ini_path: num Syntax error -- Missing']'
section_name
A closing brace was missing at the end of a section_name where section_name is the name of the section. The error occurred on line num in the file.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4002: snmp.ini_path: num Syntax error -- Section name is empty
section_name
The section section_name was found, but there was not a valid section name within the brackets. The error occurred on line num in snmp.ini.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4003: snmp.ini_path: num Syntax error --Section name contains white space
section_name
You cannot have white space between the brackets of a section. The error occurred on line num in snmp.ini in the section_name section.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4004: snmp.ini_path: num Syntax error -- keyword not in a section|
ini_entry
The keyword ini_entry was found outside of the appropriate section. The error occurred on line num in snmp.ini.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4005: snmp.ini_path: num Syntax error -- keyword not found
invalid_keyword
There is an invalid keyword in a section. The error occurred on line num in snmp.ini.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4006: snmp.ini_path: num Syntax error -- no keyword found
ini_entry
The Subagent found and entry that did not begin with a keyword. The error occurred on line num in snmp.ini.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4007: snmp.ini_path: num Syntax error -- no '=' found following keyword
ini_entry
The Subagent found a keyword but the it was missing the "=". The error occurred on line num in snmp.ini.
Stop the Subagent, edit snmp.ini, and then restart the Subagent.
S4008: snmp.ini_path: num Syntax error -- no 'value' found following '='
ini_entry
The entry ini_entry did not have a value after the "=". The error occurred on line num in snmp.ini.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4009: snmp.ini_path: num Syntax error -- Unrecognized keyword:
keyword
The Subagent found the keyword keyword in the file but it is not a valid keyword. The error occurred on line num in snmp.ini.
Stop the Subagent and edit snmp.ini. Then, restart the Subagent.
S4010: Unable to open configuration file snmp.ini_ file_name
The Subagent cannot open snmp.ini. The default file is in the $SYBASE directory. This error causes the Subagent to terminate.
You can override the file name with the -c option when starting the Subagent.
T5001: ct_send error in update_SrvParam
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5002: ct_send error in update_SrvLimitedResource
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5003: ct_send error from update_DbParam
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5004: Database_name was empty in update_DbLimitedResource
An rdbmsDbEntry had no database name.
None.
T5005: Database name in rdbmsDbTable was in wrong format in update_DbLimitedResource
A database name was improperly formatted.
None.
T5006: ct_send error in update_DbLimitedResource
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5007: ct_send error in function dbPinger
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5008: dbIndex_value, applIndex_value was not created in dbmsDbInfoTable; in dbPinger
A row in the rdbmsDbInfoTable was not created either because of insufficient memory or because it is a duplicate.
None.
T5009: DbIndex_value, applIndex_value was not created in rdbmsRelTable; in dbPinger
A row in the rdbmsRelTable was not created either because of insufficient memory or because it is a duplicate.
None.
T5010: ct_command error in routine do_sp_who
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5011: ct_send error in routine do_sp_who
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5012: ct_results failed
This is an Open Client Client-Library error that occurred while retrieving data from server. Could be a server going down, or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5013: ct_send failed in ApplEntry::connect
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5014: ct_command failed in ApplEntry::connect
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5016: ct_command failed in ApplEntry::used
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5017: ct_send failed in ApplEntry::usedb
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5018: ApplEntry::usedb: Cannnot change to database_name database
The server could be transitioning after a database was dropped. database_name could be restricted, not fully recovered, or suspect.
None.
T5019: ct_command failed in ApplEntry::often_refresh
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5020: ct_send failed in ApplEntry::often_refresh
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5021: ct_command failed in rdbmsSrvEntry::seldom
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5022: ct_send failed in ApplEntry::often_refresh
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5023: ct_send failed in ApplEntry::often_refresh
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5024: ct_command failed in rdbmsSrvEntry::seldom
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5025: ct_send failed in ApplEntry::often_refresh
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5026: rdbmsDbEntry.seldom: Can't find matching applEntry
The rdbmsDbTable is temporarily out of synchronization.
None.
T5027: ct_send failed in rdbmsDbEntry::seldom_refresh
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5028: rdbmsDbInfoEntry.seldom: Can't find matching applEntry
An inconsistency exists between rdbmsDbInfoTable and the ApplTable.
None.
T5029: rdbmDbInfoEntry.seldom: Can't find DbEntry
An inconsistency exists between rdbmsDbInfoTable and rdbmsDbTable
None.
T5030: ct_command failed in rdbmsDbEntry::seldom
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5031: ct_send failed in rdbmsDbEntry::seldom
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5032: ct_command failed in ApplEntry::connect
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
T5033: ct_send failed in ApplEntry::connect
This is an Open Client Client-Library error that could be due to a temporary error or an unstable connection.
See your Open Client Client-Library documentation for more information.
|
|