内に含ま
その他のドキュメント
サポート リソース
| PDF 文書ファイルをダウンロードする
Error Messages
A
- Error messages can be generated from many different pieces of the SunNet Manager package. Error messages can be sent to a number of places: to stdout, stderr, the system console, the system's messages file, and in the case of the Console, they may go to the Console's Error Reports window or the Console's window footer.
-
Note - For descriptions of errors specific to agents, see the man page for each agent.
A.1 Categories for Error Messages
- Error messages fall into the following categories:
A.1.1 Information Only:
- For user information only. No action is required.
A.1.2 Warning:
- If possible, the application will recover as described.
A.1.3 Error:
- Remedial action from the operator is required to correct the problem.
A.1.4 API Error:
- The Manager/Agent Services library detected an error caused by the application program. These are often due to programming errors in the application.
A.1.5 Internal Error:
- An unexpected error occurred. It's possible the Console's runtime database may have become corrupted. If you suspect that is the cause of the error, try saving the runtime database to the MDB--use the File button's Save >> Management Database option-- and correct the invalid entry. After the correction is made, reinitialize the runtime database specifying the -i flag in the snm command.
- It's also possible this internal error does not indicate an error in the Console's runtime database. It could be an internal error generated by another application or by the Manager/Services library. If an internal error persists, contact the appropriate Sun service entity and provide the error message, circumstances that caused the error, and any relevant files.
A.2 Alphabetical Listing of Error Messages
- The actual error message text may be prefixed with "Error:" or the name of the application that is returning the error (e.g. "snm:"). The error messages in this section are generally listed in alphabetical order according to the text of the error message.
-
-
Abnormal termination
- Internal Error: The SNMP trap daemon has encountered a fatal error and has terminated.
-
-
Agent error:<why>
- Warning/Error: An agent returned an agent-specific error. Refer to the agent documentation for more information. (You can determine the agent from the request name, which is also returned. The default request name is in the format <agent>.<group>.<number>.)
-
-
Agent has over <number> groups
Warning: An agent has too many groups or tables. Not all groups and tables
will be displayed in the menus.
(alloc_buffer):error, no more space
- Error: The Console could not write a message to the data or event log because it ran out of virtual memory. Either increase the amount of swap space on the system or decrease the number of applications running concurrently.
-
-
(API):request failed, <why>
Error: A request failed for the reason given. The request will not be retried.
(API):request failed, <why>, retrying
- Error: A request failed for the reason given. The request will be retried.
-
-
Argument name is too big
- API Error: The specified name string is too long for the name buffer.
-
-
Attempt(s) in which an element was no longer in the MDB
- Internal Error: A race condition in the database has occurred.
-
-
Attempt(s) to Drop or Paste a request unknown to an element
- Error: The target element is not associated with an agent of the type specified in the request being dropped or pasted.
-
-
Attempt(s) to Drop or Paste into a request
- Error: An attempt was made to put elements into the subview of a request. Requests have no subviews.
-
-
Attempt(s) to Drop or Paste to an element accepting no
requests
- Error: The target element has no associated agents and therefore accepts no requests.
-
-
Attempt(s) to inappropriately Drop or Paste into Home
Error: An attempt was made to put a request into the Home view.
Attribute not supported, not using SNMP for auto-
management.
- Warning: An SNMP autorequest resulted in an "attribute not supported" error.
-
-
Attribute type does not match: group '(<group>)' attribute
'(<attr>)': schema type '(<type1>)', returned type '(<type2>)'
Error: The agent and schema disagree on the attribute's data type.
Attribute unavailable for set operation: variable #n
Error: The set request was not performed because the nth attribute to be set
was not available for set operations. This variable cannot be set.
Attribute <agent>/<group>/<attribute> is not writable
- Error: The attribute does not have write permission, it is not set-able.
-
-
Bad index <index>
- Internal Error: An invalid runtime database index was passed to a database routine.
-
-
Bad rasterfile:<file>
Error: The raster file <file> could not be loaded because its format is not that
of a raster file.
Bad security credentials
- Error: The requester's security credentials are bad. Ask your system administrator to add you to the appropriate security netgroup. Refer to "Network Administration Security" for more information about security.
-
-
Cannot acquire database lock, try again later
Error: Check to make sure that the database directory is writable.
Cannot add agent to system:<name>
- Warning: Failure adding an agent to the element called <name>.
-
-
Cannot add index to event database files <name>.:<why>
Error: The Console could not add an event report to its runtime database.
Check to see if the directory exists and is writable. If it is, remove the
runtime database files in the directory and restart the Console specifying -i.
Cannot allocate memory
Error: An error occurred allocating dynamic memory. The malloc(3)
library function failed. Try increasing the swap space on your system or
running fewer applications.
Cannot allocate memory for request
Error: There is not enough memory for the Console to proceed. Increase
swap space on the system.
Cannot allocate memory to view request.
Error: A new request has been started, but the Console cannot allocate the
memory required to display the request information in the View Requests
window. Increase the swap space.
Cannot allocate request
Error: The system does not have enough memory to allocate resources for
another request.
Cannot allocate resources to update request list.
- Warning: Due to a memory allocation failure, the state of a request could not be updated in the request list. The system will recover by itself, but the user must make sure the system has enough memory.
-
-
Cannot backup existing file - no saving done.
- Error: snm_set is unable to make a backup copy of the existing file before saving the newer version. This might be because there is no more space or no write permission on the file system.
-
-
Cannot bind socket
- Error: An error occurred binding the socket name. The bind(2) system call failed.
-
-
Cannot cache request
Internal Error: An error occurred when the activity daemon tried to cache
the request.
Cannot contact na.activity to determine id.
- Error: The Console or Browser or Grapher tools attempted to contact the daemon to obtain an ID using SNM_NAME or USER. Make sure that na.activity is installed correctly and is in /etc/inetd.conf.
-
-
Cannot create agent request log file
Error: The agent request log file does not exist and cannot be created. Ensure
the directory exists and is writable.
Cannot create base frame! Try removing some windows
Error: The operator has too many windows and the Console windows
cannot be created. Try deleting some existing windows.
Cannot create colormap, (mono display?)
Error: The Console attempted to create a colormap for a color background,
but the system appears to have a monochrome display. You must run the
Console on a color display to load color background images.
Cannot create database directory:
- The directory specified by the database keyword in the /etc/snm.conf file does not appear to be writable. Set the protection on the directory to 777 or change the database keyword to point to a directory that is writable by the user running SNM.
-
-
Cannot create event database files <name>.:<why>
- Error: The Console could not create its runtime database. Check to see if the directory exists and is writable. If it is, remove the runtime database files in the directory and restart the Console specifying -i.
-
-
Cannot create key menu, not enough memory!
Internal Error: There is not enough memory to create the key menu. Check if
the table has too many entries.
Cannot create resources for selecting requests; please
remove some windows and try again.
Error: The pop-up window to allow you to select requests cannot be
displayed because there are too many windows already open.
Cannot create resources for viewing requests; please remove
some windows and try again.
Error: The Console is unable to display the View Requests window because
there are too many windows already open.
Cannot create runtime database files <name>.<why>
Error: The Console could not create its runtime database. Check to see if the
directory exists and is writable. If it is, remove the runtime database files in
the directory and restart the Console specifying -i.
Cannot create RPC client:program = <RPC program number>;
version = <RPC version number>; RPC:Program not registered
- Error: An error occurred creating an RPC client handle for the agent with the specified <RPC program number> and <RPC version number>. The agent (an RPC program) is not registered with the portmapper on the agent system. The error is generally caused by one of the following:
- The agent is not installed on the host where you are sending the request. Install the agents on the remote system. See the Installation Guide for more information.
- The agent was started from the shell command line and subsequently killed. Follow the procedures listed under the error message "Remote procedure call failed: Can't send request: RPC: Timed out".
-
-
Cannot create TCP transport
Internal Error: An error occurred creating a TCP/IP RPC transport handle.
Cannot create UDP transport
- Internal Error: An error occurred creating a UDP/IP RPC transport handle.
-
-
Cannot create window!
- This is a window system problem. Check to make sure that the DISPLAY environment variable is set correctly, the user has permission to create a window on the requested DISPLAY, or the user does not have too many windows.
-
-
Cannot decode argument list
Internal Error: An error occurred during XDR decoding and de-serializing a
message argument list.
Cannot decode message header
- Internal Error: An error occurred during XDR decoding and de-serializing a message header.
-
-
Cannot delete activity in cache
- Internal Error: The activity daemon failed to delete the activity in its activity cache.
-
-
Cannot delete request
- Internal Error: An error occurred deleting a request from the agent request queue.
-
-
Cannot determine id. Check for existence of directory <id-
directory>.
For the Solaris 2.x version of SNM, <id-directory> is
/etc/opt/SUNWconn/snm/snm.id.
For the Solaris 1.1 version, <id-directory> is /etc/snm.id.
- Error: Check that <id-directory> exists and contains the user ID that you are using. If the directory exists, kill the activity daemon.
-
-
Cannot determine name. Neither SNM_NAME or USER set.
- Error: One of these environment variables must be set for the Grapher and Browser or Console and Grapher to communicate; it must be the same for both tools.
-
-
Cannot display more than 1024 graphic objects.
Error: The Console cannot display more than 1024 different graphic objects
(icons and raster files). You need to reduce the number of graphic objects in
the runtime database.
Cannot encode argument list
Internal Error: An error occurred during XDR encoding and serializing a
message argument list.
Cannot encode message header
Internal Error: An error occurred during XDR encoding and serializing a
message header.
Cannot execute command:<cmd>
- Error: The Console could not send an event to the program <cmd> because the command failed. Verify that the program exists and is executable.
-
-
Cannot execute mail command:<cmd>
- Error: The Console could not mail an event to a user because the mail command <cmd> failed. Verify that the mail program exists and is executable.
-
-
Cannot fetch stats on database directory:
- Error: The database db.<username> could not be found. Make sure that the directory specified by the SNMDBDIR environment variable is a valid directory that is writable. If you did not set SNMDBDIR, make sure that you are starting the Console from the same directory where the Console was last started.
-
-
Cannot find activity in cache
Internal Error: The activity daemon could not find the specified activity in
its activity cache.
Cannot find 'activity-log' entry in configuration file,
using '<file>'
- Warning: The snm.conf file does not contain an entry for 'activity-log'.
-
-
Cannot find agent <name>
Internal Error: While launching a request, the agent name could not be
found in the runtime database.
Cannot find agent name, <name>
Internal error: While making a request, the agent name specified could not
be found in the runtime database.
Cannot find agent name, serial# = <number>, rid = <number>
Internal Error: Could not find the runtime database record describing the
agent for the incoming data or event report.
Cannot find agent <defaultagent> to set
Error: The default agent you specified does not run on the target system or
does not have any set-able attributes. The default will be ignored.
Cannot find attribute record for <agentname>/<groupname>.
Internal Error: snm_set is unable to retrieve attributes under group
<groupname> for the agent <agentname> in the database. This might be an
internal database error or the database is corrupted.
Cannot find cluster record, deferred request not sent.
Error: While trying to send a request to dump the deferred statistics, the
request could not be found in the runtime database.
Cannot find cluster record, request not killed.
Error: While trying to send a request, the request could not be found in the
runtime database.
Cannot find element <name> in database -- no automatic
request started.
- Error: Element was deleted before the request could be started. Create the element and try again.
-
-
Cannot find enum text for <attribute>, number displayed.
Error: There is no database record to describe the text of the attribute which
is an enumeration data type. Check the schema file for the attribute to see if
the enumeration record is defined properly and all possible values for the
attribute are specified.
Cannot find enumeration text for <agent>/<group>/<attribute>.
Internal Error: snm_set cannot find the enumeration record in the database
for the attribute specified.
Cannot find enumeration value for <attribute>.
Internal Error: snm_set is unable to get the enumeration record for
<attribute> due to a database error.
Cannot find font <font>
Error: The font specified in the Icon Font setting in the Console Properties
Window category is not available on your OpenWindows server. Use the
xlsfonts command to see available fonts.
Cannot find glue file <filename>.
Error: The snm.glue file cannot be found. Make sure that the SNMHOME
environment variable is set correctly, and its contents are valid.
Cannot find group <name>
Internal Error: While launching a request, the group name could not be
found in the runtime database.
Cannot find group <defaultgroup> to set.
- Error: The default group you specified does not have any set-able attributes. The default will be ignored.
-
-
Cannot find group record, serial# = <number>, rid = <number>
- Internal Error: Could not find the record describing the group/table for the incoming data or event report.
-
-
Cannot find home directory for <userid>
Error: The user name specified (with "~" or "~user") is unknown or is
known but has no associated home directory. Make sure that the user name
is known (in the /etc/passwd file or in the NIS/NIS+ passwd map/table)
and has an associated home directory.
Cannot find icon/rasterfile <file>
Error: Could not load a raster or icon file. Verify the file exists and is
readable. Verify the viewBackground record in the instance file or
elementIcon record in the elements schema is correct.
Cannot find key field:<field>.
Internal Error: The field called <field> used as the runtime database key for
the record was not found in the record as expected. If the record is a
component, view, connection or bus definition, be sure the record contains a
field called Name.
Cannot find product; please set SNMHOME environment
variable
Error: The SNMHOME environment variable needs to be set to the correct path
for the SNM directory. The default of /usr/snm does not apply in this case.
Cannot find record for group <group>.
Internal Error: snm_set cannot locate the group record for <group> due to a
database error.
Cannot find record of attribute <attribute>, request not sent.
Internal Error: The Console could not find the threshold for <attribute> in its
runtime database.
Cannot find request in database
- Internal Error: The Console couldn't find a request in its runtime database.
-
-
Cannot find request to terminate
- API Error: The agent could not find the requested activity to terminate.
-
-
Cannot find request to update
Internal Error: An attempt to update the runtime database with a requests
updated status failed. Ensure the file system containing the runtime
database is not full.
Cannot find rpc id for <agent>, request not sent.
Error: While trying to send a request, the RPC program number for the
<agent> could not be found. Be sure the RPC program number for this
<agent> has been added to the RPC database.
Cannot find rpc id for redirection, request not sent
Error: This error may occur only when SNMP Redirect is in effect. The
request could not be sent as the RPC id for the target agent was not
specified correctly.
Cannot find system/schema name in <hostfile> on line <lineno>,
ignored
Error: An invalid schema name is found in the SNMP host file on line
<lineno>. Make sure the file has the right path and permission, and the line
has the proper syntax.
Cannot find target object record <system>
Error: While processing an incoming report, the Console could not find the
element representing the <system>. The report has been discarded.
Cannot find your home directory
Error: The user name specified (with "~" or "~user") is unknown or is
known but has no associated home directory. Make sure that the user name
is known (in the /etc/passwd file or in the NIS/NIS+ passwd map/table)
and has an associated home directory.
Cannot fork subprocess
- Internal Error: An error occurred creating a subprocess. The fork(2) system call failed.
-
-
Cannot get agent ID: <why>
- Error: A call to the agent to get its ID failed for the reason shown.
-
-
Cannot get current working directory.
Error: snm_set is unable to get the current working directory for 'File' pop-
up window. This might be because read or search permission is denied for a
component of the path name.
Cannot get database record for <element> - unable to retrieve
the element in the database due to database error.
Internal Error
Cannot get DES authentication handle
- Internal Error: An error occurred getting a DES authentication handle.
-
-
Cannot get local host name
Internal Error: A error occurred getting the local hostname. The
sysinfo(2) system call failed.
Cannot get report message information:<reason>
Error: While processing an incoming report, the Console could not obtain
the information about the report. The report has been discarded.
Cannot get request info, deferred request not sent.
Error: While trying to send a request to dump deferred reports, the
information about the request could not be extracted from the runtime
database record.
Cannot get request info, request not killed.
- Error: While trying to kill a request, the request could not be found in the runtime database. The request was not killed.
-
-
Cannot get RPC# for agent <agentname>.
- Error: snm_set is unable to get the rpc number for <agentname>. This might be a mismatch of the agent's RPC number or the agent is not registered.
-
-
Cannot get RPC program number from rpc database for agent
<agentname>.
- Error: The RPC database does not have an entry for the specified agent. Make sure that are specifying a valid agent name. If you are running NIS/NIS+, you must manually add the agent entries to /etc/rpc and /etc/services on the NIS/NIS+ master.
-
-
Cannot get socket
Internal Error: An error occurred creating a socket. The socket(2) system
call failed.
Cannot get socket name
Internal Error: An error occurred getting the socket name. The
getsockname(2) system call failed.
Cannot get time of day
Error: The system did not return the time of day. (The gettimeofday(2)
system call failed.)
Cannot get user netname
Internal Error: An error occurred converting from a domain-specific
hostname to an operating-system independent netname.
Cannot initialize database manager traps -- exiting.
- Internal Error: Contact Sun support.
-
-
Cannot initialize field value <value>
- Error: The field value <value> could not be placed in the record. Either there are not enough fields in the record or the value is not the correct type for the field.
-
-
Cannot insert activity in cache
- Internal Error: The activity daemon failed to insert the activity in its activity cache.
-
-
Cannot load color rasterfile on B&W monitor:<file>
- Error: The raster file <file> is a color raster file and the Console is running on a B&W system. Color raster file can only be loaded on color systems.
-
-
Cannot load file <file>
Error: The named <file> does not exist or is not readable. Verify that the
<file> exists and is readable.
Cannot load more than 1024 icons/rasterfiles.
Error: No more than 1024 icons/raster files can be loaded into the Console.
Reduce the number of icons/raster files in the runtime database.
Cannot open <file> - load failed
Error: The named <file> does not exist or is not readable. Verify that the
<file> exists and is readable.
Cannot open activity log:<file>
Warning: The Console could not open the activity log. No checking will be
done for requests that have terminated. Verify that the activity daemon has
started, and that the user has access to the activity log file.
Cannot open event database files <name>.:<why>
Error: The Console could not open its runtime database. Check to see if the
directory exists and is readable. If it is, first delete the file
/usr/tmp/NETISAM.LOCKTABLE, then remove the runtime database files
in the directory. Restart the Console with the -i option.
Cannot open file <file>
Error: The requested <file> could not be opened. Make sure the directory
exists, and has the appropriate permissions for access.
Cannot open <file> for reading.
- Error: The <file> to load does not have read permission.
-
-
Cannot open <file> for writing.
- Error: The <file> to save does not have write permission.
-
-
Cannot open <file> - save failed.
- Error: The named path to the <file> might not exist or is not writable. Verify that the path to the <file> exists and is writable.
-
-
Cannot open icon directory <directory>
Error: The Console could not open the icon directory <directory> as specified
in the Locations category of the Console's Property window. Check to verify
that the <directory> exists and that you have read and execute (list) access.
Cannot open lock file: <file>: <why>
Error: The lock file <file> could not be opened for the stated reason. Set the
protection on the lock file so that the <file> is readable.
Cannot open runtime database files <name>.:<why>
- Error: The Console could not open its runtime database. Check to see if the directory exists and is readable. If it is, first delete the file /usr/tmp/NETISAM.LOCKTABLE, then remove the runtime database files in the directory. Restart the Console with the -i option.
-
-
Cannot open schema directory <directory>
- Error: The agent/element schema directory could not be found. Verify that the <directory> is readable and that path name specified in the Locations category of the Console's Properties window points to the correct <directory>.
-
-
Cannot open temporary print file <file>
- Error: The temporary print file could not be created. Verify that /tmp is writable.
-
-
Cannot read kernel memory
Error: An error occurred reading from kernel memory. This could happen if
the application doesn't have permission to read kernel statistics.
Cannot register callback (<why>)
- Internal Error: The Console could not register itself with the port mapper.
-
-
Cannot register rendezvous with event dispatcher (<why>)
- Internal Error: An error occurred registering a rendezvous with the event dispatcher.
-
-
Cannot register RPC service
- Internal Error: An error occurred registering the RPC service with the portmapper.
-
-
Cannot register with event dispatcher (<why>)
Error: The Console could not register itself with the event dispatcher,
na.event. Verify na.event has been correctly installed and is either
started manually or from inetd.
Cannot request data report for group '(<groupname>)'
(<reason>)
Error: The request to the agent failed for the reason shown.
Cannot save enumeration <name>
- Error: The enumeration could not be saved in the runtime database.
-
-
Cannot set argument (<error>)
Error: While trying to send a request, the netmgt_set_argument(3n) call
failed and returned <error>.
Cannot set first threshold (<error>).
Internal Error: While trying to set a threshold, the
netmgt_set_threshold(3n) call failed and returned <error>.
Cannot set instance (<error>)
Error: While trying to send a request, the call to
netmgt_set_instance(3n) failed and returned <error>.
Cannot set second threshold (<error>)
- Error: While trying to set a threshold, the call to netmgt_set_threshold(3n) failed and returned <error>.
-
-
Cannot set socket SO_REUSEADDR
- Internal Error: An error occurred setting the socket option. The setsockopt() system call failed.
-
-
Cannot start more requests
Error: The agent could not start the request because it would exceed the
maximum number of requests the agent is configured to perform. You must
either terminate some of the requests the agent is performing or reconfigure
the agent to perform more requests. See the snm.conf(5) manual page.
Cannot start request '<reason>'
- Error: The agent could not start the request because of the specified '<reason>'.
-
-
Cannot terminate request
API Error: An error occurred terminating the requested operation. The
kill(2) system call failed.
Cannot unregister rendezvous with event dispatcher
- Internal Error: An error occurred unregistering a rendezvous with the event dispatcher.
-
-
Cannot unregister RPC service
Internal Error: An error occurred unregistering the RPC service with the
port mapper.
Child process ended unexpectedly
- Internal Error: The child process has encountered a fatal error and exited.
-
-
Cluster record overflow.
- Error: Too much data in an element record.
-
-
Console must be restarted to get correct color images
Error: The Console was unable to obtain the colors required for the icons or
backgrounds specified in the schema file being loaded. To obtain the correct
colors, stop and restart the Console.
Could not change type for <system> due to memory allocation
failure
- Error: There was not enough memory or swap space available to make the change. Free up space by killing unnecessary processes etc., and retry.
-
-
Could not open schema file : (<filename>)
Error: The listed file could not be opened for reading.
Creating a database in <directory>.
- Information Only: Tells the user where database was created.
-
-
Database directory is not a directory: <name>
Error: db.username was found, but is not a directory (it could be a regular
file, named pipe, etc.). Verify that the value associated with the SNMDBDIR
environment variable is a valid directory.
Delete from view <view> failed.
Warning: In attempting to delete an element from the view called <view> the
operation failed.
Detected n errors between schema file and
agent'(<agentname>)' on '(<hostname>)'
Error: This is a summary of errors found. Correct the agent schema file
and/or agent code.
Duplicate agent name <name>
Error: The agent/proxy name matched an agent/proxy already in the
runtime database. Change the conflicting agent name.
Duplicate agent/proxy:<name>
Error: An element was defined that contained two or more agent or proxy
records with the same name. Fix the schema file and reload it.
Duplicate attribute name:<name>
- Error: The agent has a group with two attributes with the same name. Change the name of one of the attributes and then reload the schema file.
-
-
Duplicate definition of group (<groupname>)
- Error: The named group/table has been previously defined in this agent schema. Correct the agent schema file
-
-
Duplicate enum name <name>
- Error: The enumeration name is a duplicate of an existing enumeration name.
-
-
Duplicate error code <number>
Error: The agent error code <number> appears for multiple messages.
Correct the agent schema file.
Duplicate field name <name>
Error: The field name matched a field already in the runtime database.
Change the conflicting group/table name.
Duplicate group/table name <name>
Error: The group/table name matched a group/table already in the runtime
database. Change the conflicting group/table name.
Duplicate id:<id>
Error: When adding a request record to the runtime database, the serial
number <id> of the request matched an existing request. Make sure all
requests have unique serial numbers.
Duplicate name:<name>
Error: When adding a component, view, connection or bus record to the
runtime database, the name for the record matched an existing record. All
elements must have unique names. Change the name of the element.
Duplicate record name <name>
Error: A record name matched that of an existing record. Change the name
of one of the record definitions.
Duplicate request id #<number> ignored
- Warning: While reading in a MDB file, two requests with the same request identification were found. The duplicate request is ignored.
-
-
Empty queue
- Internal Error: The queue specified is empty.
-
-
Error creating new stream, file load aborted.
- Internal Error: Contact the appropriate Sun service entity and submit the log file.
-
-
Error report message too long
API Error: The error report message string is too long.
Error while asking for portmapper list
- Warning: The remote portmapper was not reachable.
-
-
Error while connecting to portmapper
- Warning: The remote portmapper was not reachable.
-
-
Error while creating client to portmapper
- Warning: The remote portmapper was not reachable.
-
-
Error while creating ICMP socket
- Internal Error
-
-
Error while creating pipe
- Internal Error: An error occurred when creating the pipe to a subprocess.
-
-
Error while creating portmapper socket
Error while creating raw socket
Internal Error
Error while getting interface flags
- Internal Error
-
-
Error while receiving response
- Warning: Discover noticed that an unexpected error occurred while waiting for a ping response and will retry the ping request.
-
-
Event occurred, however could not get event data
- Internal Error
-
-
Event report data too big
API Error: The event report is larger than 6KB.
Failed to fetch netmgt error
- Internal Error: An incoming error message was received, but the Set tool could not fetch the error information.
-
-
Failed to fetch Set reply: <reason>
- Internal Error: snm_set cannot get the confirmation message of the set request.
-
-
Fatal error
- The requested operation experienced a fatal agent specific error. The global variable netmgt_error.agent_error (if nonzero) is an index to an error string in the agent schema file. This string describes the cause of the error. The global variable netmgt_error.message (if non-null) is a pointer to a string containing additional error information.
-
-
File name load aborted after <number> reports read.
Error: Loading of the file was aborted, as too many errors were detected in
the log file. Make sure that the log file is in the correct log file format; see the
snm.logfile(5) manual page.
File not found: <file>.
Error: The <file> to load does not exist. Make sure that the <file> exists in the
specified directory.
File <file> is not a regular file.
Error: The Browser can only read regular UNIX files and not directories or
special (device) files. Supply the name of a regular file.
Grapher not running
- Error: A request was launched from the Console or the Browser that specified sending results to the Grapher but the Grapher is not running. Start the Grapher and then restart the request.
-
-
HOME environment variable is not set
- Error: Set the HOME environment variable to point to the home directory.
-
-
Invalid agent security level
API Error: An invalid agent security level was specified.
Invalid message type
- API Error: The requested operation is invalid for this message type.
-
-
Invalid group name
- API Error: An invalid group name was specified. This error occurs when: (1) there is no entry for the target device in the SNMP host file so the default SNMP schema (na.snmp.default-schema) was used, but the default schema does not contain the specified group, or (2) the schema defined in the SNMP host file does not contain the specified group.
-
-
Invalid input (date type is <type>).
Error: There is an error in the input data. Check if the input is of the proper
data type.
Invalid key name
- API Error: An invalid key was specified.
-
-
Invalid object id <id> found in <filename>
Error: Invalid input was found in the SNMP schema file while the SNMP
trap daemon was loading data. This might be a syntax error in or an invalid
object identifier in the file.
Invalid relational operator
- API Error: An invalid threshold relational operator was specified.
-
-
Invalid reporting count
- API Error: An invalid data or event reporting count was specified.
-
-
Invalid reporting interval
- API Error: An invalid data or event reporting interval was specified.
-
-
Invalid request timestamp
- API Error: An invalid request timestamp was specified.
-
-
Invalid RPC timeout
API Error: An invalid RPC timeout was specified.
Invalid system name
- API Error: An invalid system name was specified.
-
-
Invalid trap-signal type <type>
- Error: The trap-signal type specified is invalid.
-
-
Invalid type <type>
- Error: The type is unknown.
-
-
Limits exceeded
- Error: The database limit has been exceeded for Site Manager.
-
-
Load failed, invalid input data/format
Error: The file to load does not have a valid input format. Refer to "Set
Tool" for more information about using Set Tool.
Load failed, no writeable attribute for target system in
file.
Warning: There is no applicable data for the current target system to load
from the file. Nothing will be loaded.
Load failed, not enough memory!
- Internal Error: Not enough internal memory is available to load the data.
-
-
Load of icon file failed
- Error: Could not load a raster or icon file. Verify the file exists and is readable. Verify the viewBackground record in the instance file or elementIcon record in the elements schema is correct.
-
-
Memory allocation failure -- no automatic request started
for <name>
- Error: System ran out of memory. Maybe there is not enough swap space. Try again.
-
-
nc_rebuildIcons:add failed.
Internal Error: when rebuilding the glyph list, the Console could not insert a
glyph record.
NIS not running
Error: The Network Information Services (NIS) are not running. NIS/NIS+
is required if you are using secure RPC.
No agent host name
- API Error: No agent host name was specified when sending the request.
-
-
No agent name
- API Error: No agent name was specified.
-
No agent to set. Error: There is no agent that has any set-able (that is, writable) attributes running on the current target system.
-
-
No agents apply
- The element does not have any agent run on the system, or applied to the system.
-
-
No alias exists
Error: The object does not have any alias.
No alias found
Error: The object does not have the specified alias.
No argument buffer
- API Error: No argument buffer was specified.
-
-
No argument length
- API Error: No argument length was specified.
-
-
No argument name
- API Error: No argument name was specified.
-
-
No argument type
- API Error: No argument name was specified.
-
-
No argument value
API Error: No argument value was specified.
No attribute information saved to Unset.
- Error: snm_set is unable to undo the previous set request. This might be because the previous set request failed.
-
-
No attribute information supplied to Set.
- Error: No attribute set information has been supplied to do the set request.
-
-
No callback dispatch function
API Error: No callback dispatch function was specified.
No Console
Information Only: The Console was not running when the database
record was added by Discover.
No data buffer
- API Error: No data buffer was specified.
-
-
No error report buffer
- API Error: No error report buffer was specified.
-
-
No event report buffer
- API Error: No event report buffer was specified.
-
-
No event threshold buffer
- API Error: No event threshold buffer specified.
-
-
No group name
- API Error: No group name was specified.
-
-
No group to set.
Error: There is no group that has any set-able (that is, writable)
attributes under the current agent.
No groups in this agent?
- Error: There were no groups or tables listed in the schema file. Check the agent schema file.
-
-
No license found
- Error: There is no license installed in the system.
-
-
No manager host name
- API Error: No manager host name was specified when sending the request.
-
-
No message information buffer
API Error: No message information buffer was specified.
No more space to do Unset (malloc failed when building
backup list).
Internal Error: Not enough memory is available.
No optional argument buffer
- API Error: No optional argument buffer specified.
-
-
No relational operator
- API Error: No threshold relational operator was specified.
-
-
No rendezvous host name
Error: No rendezvous host name was specified when sending the
request. You need to specify a rendezvous name in your request.
No report to print
- Warning: There was no report to print.
-
-
No request information buffer
- API Error: No request information buffer specified.
-
-
No Streams Selected
Warning: Attempted to send data from the Browser to the Grapher
without having stream(s) selected first.
No such file: <file>
- Error: The image file specified in the database does not exist. Check the database for the correct file name and directory path.
-
-
No such rasterfile: <file>
- Error: The raster file <file> could not be opened. Check that the file exists and that the permissions allow reading.
-
-
No suitable network interfaces are available
- Error: None of the interfaces found on the system were available for Discover watch mode. Discover does not use the loopback interface, a point-to-point interface, or an interface that is marked "down" when using watch mode. If no other interfaces are available, watch mode cannot be used. Use Discover with "ping" mode instead.
-
-
No system name
Error: No system name was specified. You need to specify a system
name in your request.
No table key
Error: The set request for a tabular attribute did not specify a table key.
Specify a table key and re-send the request.
No threshold buffer
- API Error: No threshold buffer was specified.
-
-
No threshold is set for attribute <name>.
Internal Error: While trying to request event reports, an attribute was
found that did not have any thresholds set.
No threshold is set, request is not sent.
Error: A request to start event reporting has no thresholds. The request
is ignored.
No threshold value
- API Error: No threshold value was specified.
-
-
No value buffer
- API Error: No value buffer specified.
-
-
No value saved to unset attribute <attribute>
- Error: snm_set is unable to undo the previous, successful set for <attribute>. This might be because the previous set request failed, or the attribute is not in the list of items set in the previous request.
-
-
Non-fatal error
- Warning: An agent-defined warning message is being returned. The global variable netmgt_error.agent_error (if nonzero) is the number of the error string in the agent schema file. This string describes the cause of the error. The global variable netmgt_error.message (if non-null) is a pointer to a string containing additional error information.
-
-
Not a cluster record
Internal Error: A request was found in the runtime database that was
not a cluster record.
Not enough memory for additional records
Error: The Console has run out of virtual memory for additional record
definitions. Either allocate more swap space for the system or run
fewer applications concurrently.
Not enough memory for clone window!
- Error: The Browser could not allocate enough memory to clone the requested window. Try increasing the size of the system's swap space.
-
-
Not Interesting
- Information Only: The -v and -e options were specified for Discover, and a system was found that did not meet the "interesting system" criteria.
-
-
<file name>: Not Readable by SunNet Manager...
An attempt was made to load <file name> as a runtime database or
data/events request file but <file name> is not in ASCII format.
Not regular file: <file name>
Error: The file <file name> is not a regular file. Check to make sure the
file is of a valid type.
Note - attribute is 'writeonly': group '(<group>)',
attribute '(<attr>)'
Error: Since the named attribute is write-only, the agent doesn't return
it; it cannot be checked with snm_cmd -v.
NULL callback socket pointer
Error: A NULL callback socket pointer was specified. Specify the
address of a socket descriptor in your request.
Null cluster record
- Error: An empty cluster record was found in the MDB.
-
-
NULL queue node data pointer
- Internal Error: A null queue node data pointer was specified.
-
-
NULL queue node pointer
- Internal Error: A null queue node pointer was specified.
-
-
NULL queue pointer
Internal Error: A null queue pointer was specified.
Number of bits in host part must be >0 and <=24
Error: A negative, zero-length or large (more than three bytes) host
part is not legal under TCP/IP. Specify a legal number of host bits
between 1 and 24 inclusive.
Only agent child can call this function
- API Error: Only an agent child process can call this function.
-
-
Only agent parent can call this function
- API Error: Only an agent parent process can call this function.
-
-
Only manager can call this function
- API Error: Only a manager application can call this function.
-
-
Only rendezvous can call this function
- API Error: Only a rendezvous application can call this function.
-
-
Opening event log
- Error: The Console couldn't allocate enough memory for the event log.
-
-
Opening event log state
- Error: The Console couldn't allocate enough memory for the event log state.
-
-
Out of memory (<program>)
- Error: The program <program> was not able to allocate enough memory for its operation. Try to reduce memory utilization by killing unused processes or by increasing swap space. If this error persists, contact the appropriate Sun service entity and specify the name of the program.
-
-
Out of memory...cannot mail to <user>
Error: The Console ran out of virtual memory while trying to mail an
event to <user>. Increase the amount of swap space for the system or
run fewer applications concurrently.
Out of memory...cannot send to <cmd>
- Error: The Console ran out of virtual memory while trying to send an event to the program <cmd>. Increase the amount of swap space for the system or run fewer applications concurrently.
-
-
Over <number> agents defined
Warning: Too many agents defined in the system. Reduce the number
of agents.
Over <number> agents on system: <name>
- Warning: Too many agents were added to the element called <name>. Not all agents will be displayed in the menus.
-
-
Over <number> elements in view.
- Warning: A view contains too many elements. Not all the elements in the view will be displayed. Break the view up into two or more subviews.
-
-
Over <number> record types defined.
Warning: Too many record types defined.
Over <number> types defined.
Warning: Too many components, views, connections or buses defined.
Not all will be listed in the menus.
Parsing error, file not saved
Error: An error occurred when the SNMP trap daemon was parsing the
SNMP schema file. Make sure that the file has the proper syntax, as
specified by the agent schema syntax definitions.
Reading MDB: <error>
- Error: An error occurred when reading from the MDB.
-
-
Read only mode
- Information only: The database is read-only.
-
-
Record <#id> is not an attribute record, request not sent.
- Internal Error: A record in the runtime database that was expected to be an attribute record was not. The request has not been started.
-
-
Record does not contain 'Name' field
- Error: A element was defined whose record did not contain a 'Name' field. All elements definitions must contain a 'Name' field. Fix the element schema file and then restart the Console and load in the new files.
-
-
Remote procedure call failed: <message>
- Error: A remote procedure call error was detected. The error <message> indicates the reason.
-
-
Remote procedure call failed: Can't send request:RPC:
Timed out
- Error: The request failed because the remote procedure call timed out before a request confirmation was received by requesting processes. This error is generally caused by one of the following:
- The network connection between the manager and agent cannot be established because of network congestion. The Console continues to re-send the request until the request succeeds or the user kills the request.
- The host where the Console and/or the agent is installed is slow because of high CPU utilization, disk I/O, etc. The Console continues to re-send the request until the request succeeds or the user kills the request.
- A new copy of the agent was installed on the system and inetd(8c) was not initialized. You should:
-
- Kill any requests for the agent from the Console. You only need to kill requests for the agent on the system where the new version of the agent is installed.
- Log into the system where the new version of the agent is installed.
- Reinitialize inetd(8c) by sending kill -HUP to the inetd(8c) process.
- Re-send the request.
-
-
Report is too big: 52438 byte maximum for event reports.
Error: The maximum event report size that can be returned is 52438
bytes. You cannot request event reports where the returned report size
would exceed this limit (for example, where every row in a very large
table is returned).
Request <req>: Agent error: <error>: <error_info>
- Warning: Recoverable operational error encountered; the request will be retried.
- Error: Unrecoverable operational error encountered; the request will not be retried.
-
-
Request <req>: API error: <error>
- Error: Unrecoverable operational error encountered; the request will not be retried.
-
-
Request <req>: API error: <error>: Retrying
Error: A recoverable operational error was encountered. The request
will be retried.
Request <req>, cannot get confirm message
Internal Error: An incoming error message was received but the
Console could not fetch the error specific information.
Request must be performed by a new subprocess
API Error: Request cannot be performed by an existing subprocess. You
must create a new subprocess to handle this request.
Request too large
- Internal Error: a request was found that was too large.
-
-
Request without request state encountered
- Internal Error: A runtime database entry for a request was found that did not contain a request state entry.
-
-
Requesting deferred data reports (<error>)
- Error: While requesting deferred data reports, the API error specified occurred.
-
-
Request(s) failed
Error: The request could not be started.
Request has ended unexpectedly
- Warning: A request ended without notifying the Console that it was ending. Some possible reasons are the agent has crashed, the remote machine has crashed, etc. If the request has "Restart" set to true, the Console will attempt to restart the request and will indicate this by appending the text "-- restarting" to the error message.
-
-
Request(s) invalid
Error: The request's data fields were not valid for submission to the
helper process.
Request(s) submitted
- Information Only: Requests were successfully submitted to the helper process.
-
-
Row/instance does not exist with key <key>
- Error: snm_set is unable to retrieve the row identified by <key>.
-
-
Runtime database does not contain <name> record definition
Error: Restart the Console with the -i option.
Save failed, calloc(): not enough memory!
- Internal Error: Not enough memory is available.
-
-
Save failed, fwrite error!
- Internal Error: The file is not able to be saved due to an I/O error.
-
-
Save failed, unable to process line <linenumber>
Internal Error: snm_set is unable to save the line numbered
<linenumber> in the Set Information window.
Saw bad file entry '<entry>...' at line <line>
Saw bad logfile entry at offset <number>
Saw bad microseconds value '<seconds>' at line <line>
Saw bad received time '<time>' at line <line>
Saw bad RPC number '<number>' at line <line>
Saw bad seconds value '<seconds>' at line <line>
Error: The log file has an incorrect entry at the indicated <line>. Correct
the entry according to the format specified in snm.logfile(5). If the
log file entry was programmatically generated, the application that
wrote the entry should be fixed.
Schema serial number mismatch: agent wants <n>, schema is
<m>.
No attribute validation done.
- Error: The agent was initialized with a particular serial number coded in the agent software. The agent schema serial number given by the 'serial' keyword should match, otherwise the agent and schema are out of sync. If no 'serial' keyword is given, serial 1 is assumed. This is a fatal error; snm_cmd will not continue.
-
-
scroll.c: Cannot acquire selection!
Internal Error.
Security credentials too weak
- Internal Error: The requester's security credentials are too weak.
-
-
SizeField: Need to give size for type <type>
- Internal Error: the type for a field did not match a type known to the Console.
-
-
snm already running: started <date> on <host> (pid <pid>) by
<user> on display <displayname>
- Error: The Console is already being run under the user name specified in the message. Change SNM_NAME and rerun the Console. (Existing Browser and Grapher instances would need to be restarted with the same name.)
-
-
Specified database directory is not a directory: <path>
Error: The database directory path must be a directory.
Success
- The requested operation completed successfully.
-
-
Symbol 'rthost' is not in the kernel's namelist
Symbol 'rtnet' is not in the kernel's namelist
Symbol 'rthashsize' is not in the kernel's namelist
Internal Error: A required symbol (related to the routing table) was not
found in the kernel's name list.
Syntax error in <trapfile> on line <lineno>
- Error: Invalid input found in the trap file on the line indicated.
-
-
The receiving application cannot handle
- Error: The Browser cannot send data to the specified receiver because the receiver cannot accept the indicated data type. For example, the Results Grapher can only accept integer, float, gauge, and counter data types.
-
-
These attribute(s) not returned by agent '(agentname)' group
'(group)'
attribute '(attr1)' (type (type1))
attribute '(attr2)' (type (type2))
Error: The given list of attributes was named in the agent schema but
the agent didn't return any of them. Check the agent schema.
This folder cannot be renamed
- Warning: An attempt was made to rename the Browser Main folder. To create a new folder, use the New Folder option of the Edit menu.
-
-
Time must be > 0
- Error: The pause or wait times for Discover must be positive numbers.
-
-
Too many fields
Error: An attempt was made to store into a field that did not exist in
the record.
Too many panel items -- <n> items drawn
- Internal Error: Contact Sun support.
-
-
Too many requests
- Warning: No more requests can be added. Out of virtual memory.
-
-
Two agent definitions in schema file
- Error: Only one agent definition is allowed per schema file. Correct the agent schema file.
-
-
Type field. Need to give size for type <type>
- Internal Error: The type for a field did not match a type known to the Console.
-
-
Unable to connect to Graph Tool: <reason>
Error: The Console or Browser could not contact the Grapher for the
reason shown. If the Grapher is not running, start the Grapher and
restart the request. If the Grapher is running, restart the Grapher and
then restart the request.
Unable to delete alias
- Error: Unable to delete the specified alias.
-
-
Unable to extract RPC id number from <file>
Error: The Console or Browser could not determine the RPC program
number of the Grapher from the file <file>. Restart the Grapher and
then restart the request.
Unable to load requested color, try increasing colormap-
size.
Error: The raster file file has too many colors to be loaded. Either
reduce the number of colors in the raster file or increase the number
allocated to the Console by modifying the Maximum Colors setting in
the Console Properties Windows category.
Unable to obtain Grapher port number
- Error: The Console or Browser could not locate the port number for the Grapher. You may have attempted to send data to the Grapher, but the Grapher is not running. Start/Restart the Grapher and then either restart the request or re-send the data to be graphed.
-
-
Undefined attribute '(<attr>)' (type (<type>)) returned by
agent
Error: An attribute with the given name and type was returned by the
agent but is not listed in the agent schema. Correct the agent schema.
Undefined enumeration name <name>
- Error: The enumeration <name> is undefined.
-
-
Unexpected NIT read error
- Internal Error
-
-
Unknown agent name <name>
- Error: The agent name <name> is unknown.
-
-
Unknown argument name
- API Error: An unknown argument name was specified.
-
-
Unknown argument type
- API Error: An unknown argument type was specified.
-
-
Unknown data type (<type>) returned for request.
Error: Agent error: The incoming monitor or event report contained the
unknown data type <type>.
Unknown data type: attribute <attribute>, type <type>
- Error: The data type of the attribute to be set is not valid.
-
-
Unknown field <name>
- Error: The field <name> cannot be found in the record.
-
-
Unknown field (<name>) returned for request.
- Error: Probable agent/schema file mismatch: an incoming monitor or event report contained a field that was not defined in the agent schema.
-
-
Unknown host address
- API Error: The specified host address could not be translated to a host name.
-
-
Unknown host <name>
- API Error: The specified host name could not be translated to a host address.
-
-
Unknown name <name>
- Error: The element <name> is unknown.
-
-
Unknown net/host <name>
Error: Either the host named was not found in the /etc/hosts file or
the NIS/NIS+ host map/table, or the network named was not found in
the file /etc/networks or the NIS/NIS+ host map/table.
Unknown protocol requested
Error: The Console or Browser attempted to contact the Grapher using
an unknown protocol id. Restart the Console and try the request again.
Unknown record <name>
- Error: Record <name> is undefined.
-
-
Unknown record name <name>
- Error: The record name <name> is unknown.
-
-
Unknown request type
- API Error: An unknown request type was specified.
-
-
Unknown system name <name>
- Error: The element called <name> could not be found.
-
-
Unknown transport protocol
- API Error: An invalid transport protocol was specified.
-
-
Unrecoverable error while opening ICMP socket
- Internal Error.
-
-
Username too long: <name>
Error: The supplied user name is illegal; it has too many characters.
Supply a legal user name.
Using monochrome mode.
Information Only: Static visuals are treated as monochrome--all
glyphs are black and white.
Value is too big
- Internal Error: The agent cannot return a value because it would overflow an internal buffer.
-
-
Warning: field <field> not present in component.<type>
- Warning: When the element type of an element is changed, not all properties of the original element type can be converted to the new element type.
-
-
Would exceed queue length limit
Internal Error: A node cannot be appended to a queue because the
queue length limit would be exceeded.
Writing MDB: <error>
- Error: An error occurred when writing to the MDB.
|
|