Chapter 6 Error Messages
This chapter describes the critical farm and system error messages with an error ID. The error messages described in this chapter consist of the following categories:
-
Core system errors: error ID 1001 through 1022
-
Control plane database (CPDB) errors: error ID 2001 through 2043
-
Hardware abstraction layer (HAL) errors: error ID 3000 through 3950
-
Monitoring errors: error ID 4015 through 4042
-
Domain Name Service (DNS) and Dynamic Host Configuration Protocol (DHCP) errors: error ID 5000 through 5021
-
Farm management errors: error ID 6100 through 6823 and 9300 through 9316
Note –The error message listing in this chapter is not all inclusive. It lists only the most important messages that you might encounter.
Error Message Overview
During the course of administering an Infrastructure Fabric (I-Fabric), you will encounter error messages. This chapter provides messages, descriptions, and actions required to solve a problem or to gather additional information before reporting a problem. You can locate messages in the log files.
The severity of error messages ranges from merely a minor debug message to a critical alert. All messages from N1 Provisioning Server software are logged in the /var/adm/tspr.debug log file. All messages from third-party components (for example, drivers) are logged in the /var/adm/messages log file.
As the message is written to the log file, the message is categorized as okay, debug, warning, or critical. The following example shows how it appears in the log:
Oct 30 00:16:47 sp4 java[ 506]: [ID 289794 user.info] TSPR [sev=okay] [apps=770034] TCPEventHandler:dispatch. |
Note –
[sev=okay] denotes the message's severity.
N1 Provisioning Server software logs messages in two separate log files:
-
okay, warning, and critical messages with an error ID are logged in the /var/adm/messages log file.
-
Along with the okay, warning, and critical messages, the /var/adm/tspr.debug log file also includes the debug messages, which are used for debugging system failures.
Error Message Descriptions
The following table lists messages by their error number. Each message is described in detail and corrective actions are provided. Words enclosed in curly brackets, for example {application_ID}, denote variables that are substituted for meaningful values when an error occurs.
Core System Errors (ID 1001 through 1022)
1001 property property-name is invalid, using default |
The property entered in the tspr.properties file for a device is invalid. The system is using the default value.
Solution:Enter a valid value for this property in the tspr.properties file or remove the line entirely.
1002 cannot get database access |
The device cannot access the CPDB.
Solution:Ensure that the database settings in /etc/opt/terraspring /tspr.properties are correctly pointing to the database. Check that the database is running. See the N1 Provisioning Server 3.1, Blades Edition, Installation Guide for details.
1003 method name with null arguments |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1004 not registered |
The process is not yet registered.
Solution:Restart all the processes on the control plane server, most important, segment manager. Also ensure that the database is not corrupted by, for instance, manual manipulation of data.
1005 application-ID already registered |
The process has already been registered
Solution:Stop and restart the segment manager.
1006 invalid entry in application table with application-ID |
The application table in the CPDB contains an invalid entry for the application.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
1007 cannot dequeue or update request (request ID) |
The server is unable to process or update the specified request ID.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
1008 Object name not serializable |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1009 invalid destination aid |
The database contains an invalid entry of a destination application ID (AID) associated with a particular process.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
1011 cannot send event to destination-aid (exception-details) |
A process is unable to send an event to another process with destination_aid.
Solution:Ensure that the destination application is running properly.
1012 invalid request id |
An invalid request ID has been provided.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
1013 timeout expires |
An execution of a request has timed out.
Solution:A request performs a task. When this task is being executed, a timeout value is usually associated with the request. When the time since execution exceeds this value, this message is printed. Ensure that the destination application is running. Also ensure that no blocked requests for the destination application exist. Try to reissue the command.
1014 application-ID: max number of digit exceeded |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1015 application-ID: not a digit |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1016 Invalid IP address: IP-address |
An invalid IP address has been provided.
Solution:Check that all IP addresses in the CPDB have been correctly entered.
1017 method name:value invalid argument |
An invalid argument has been entered.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
1022 Could NOT create the LogHandler, classname. |
An invalid LogHandler has been entered for the com.terraspring. core.log.exthandler.
Solution:Ensure that the exthandler property is set to a valid class name that implements the LogHandler interface.
CPDB Errors (ID 2001 through 2043)
2002 Not enough resource-name resources available to complete allocation. |
The farm requires resources that are currently unavailable.
Solution:Place more devices into the resource pool or wait for more resources to become available.
2005 object-name value is not in correct state for this operation. |
The farm is currently not in the correct state for executing the specified operation.
Solution:Ensure that the farm is allowed to make the transition intended (refer to Chapter 7, Troubleshooting).
2008 Request request-ID could not be materialized from the database. |
This could be caused by incompatible objects on the client and server side.
Solution:Ensure that the packages are up to date. Delete the request and restart the Segment Manager (refer to Chapter 7, Troubleshooting). Retry the operation or reissue the command that previously failed.
2009 Invalid database connection parameters. Check the tspr.properties file. |
The /etc/opt/ terraspring/ tspr.properties file has an invalid entry.
Solution:In the tspr.properties file, check the lines that begin with com.terraspring.db. CpdbConnection and enter the correct connection parameter.
2010 More than one Segment Manager is running on the host. |
You may only have one segment manager running.
Solution:Stop all the segment managers by issuing /opt/terraspring/sbin/sm -stop. Restart the segment manager using /opt/terraspring/sbin/sm -start.
2011 Invalid application state for this operation. |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
2016 Image size is greater than the requested disk size. |
Internal error.
Solution:Ensure that the specified image is of a smaller or equal size than the specified disk. Choose a smaller image or increase the disk size.
2017 Invalid special device type: type |
The type must be BACKHAUL.
Solution:This message is associated with the farm's Farm Markup Language (FML) and Wiring Markup Language (WML). Contact http://sun.com/service/contacting/index.html for assistance.
2031 IP does not belong to subnet |
The specified IP address does not belong to the specified subnet.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
2033 Invalid deQueue request status: request-ID |
The queue is in QUEUED, QUEUED_BLOCKED, or INPROGRESS state.
Solution:Refer to Chapter 7, Troubleshooting for details on dealing with requests.
2035 Duplicate MAC address mac-address cannot be added |
The media access control (MAC) address is already in use.
Solution:Assign a MAC address that is not yet in use.
2036 Subnet cannot be added because it overlaps with an existing one |
This subnet is already defined.
Solution:Assign a subnet that is not yet defined.
2037 CPDB server is probably dead or not allowing connections |
The CPDB connection is failing.
Solution:Check whether the server is running. If not, start it.
Check the listener for the network connection. If the connection has failed, reestablish the network connection.
2038 Farm name: farm-name does not follow the DNS domain label format |
An invalid DNS name has been specified.
Solution:DNS names accept only alphanumeric characters and the minus (-) sign. Specify a proper DNS name.
2039 Customer name: customer-name does not follow the DNS domain label format |
An invalid DNS name has been specified.
Solution:DNS names accept only alphanumeric characters and the minus (-) sign. Specify a proper DNS name.
2040 CP name cannot be null |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
2041 Monitor Node with monitoring_node not found |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
2042 IP Address IP_address is not a valid IP |
An invalid IP address has been assigned.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
Hardware Abstraction Layer (HAL) Errors (ID 3000 through 3950)
3000 Missing attributes attribute-name |
An attribute, such as an IP address for the server or a password, is missing in the CPDB.
Solution:Use the device command to add the missing attribute to the CPDB. For details on how to use this command see the device man page.
3100 Network interface can only be configured by root. |
The Network Virtual Interfaces (NVIs) cannot be created because the farm manager is not run as root.
Solution:Ensure that the user has root access and retry the operation, or reissue the command that previously failed. Refer to the Solaris 8 documentation for details on root access.
3101 Solaris network interface is already in use. |
The NVI intended to be created has already been created. This error can be caused by resources not being cleared up completely after a failed farm operation.
Solution:Refer to Chapter 7, Troubleshooting for details on how to clear up NVIs and such resources.
3102 ifconfig failed on Solaris |
ifconfig is a standard Solaris command. Failure to issue this command implies some misbehavior in the operating environment.
Solution:Ensure that the Solaris software has been set up properly.
3103 unknown exit code from ifconfig |
ifconfig is a standard Solaris command. Failure to issue this command implies some misbehavior in the operating environment.
Solution:Ensure that the Solaris software has been set up properly.
3202 Login/passwd incorrect |
Cannot log into a device, such as a server.
Solution:Ensure that the user names and passwords on the database are current.
3204 Operation not supported on Solaris |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
3300 methodname The MAC address for key not found on device |
The MAC address for the device is missing.
Solution:This message is associated with the farm's WML. Contact http://sun.com/service/contacting/index.html for assistance.
3500 Warning: Cannot initialize interfaces on ifname (error) |
The system is unable to bring up an interface, such as a card or driver.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
3600 SQLException: exception |
Database error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
3700 This feature is not supported. |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
3800 Physical Device is either null or not valid |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
3900 Invalid Power Controller Port |
Inconsistency with the ports and the power controller specified in the database.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
3950 Could not power down the specified port. |
Power controller could not power down the device on a port.
Solution:Check the physical device and ensure accessibility and its connection to the power controller.
Monitoring Errors (ID 4015 through 4042)
4015 Monitoring [start] Error: No database connection. |
The database connection is unavailable now.
Solution:Check the CPDB connection and redo the operation.
4016 Monitoring [start] Error: No farm id. |
The farm ID is not valid. The CPDB has incorrect values for this farm.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
4017 Monitoring [start] Error: No node id. |
The node ID is not valid. The CPDB has incorrect values for this node.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
4019 Monitoring [start] Warning: Empty MML. |
The Monitoring Markup Language (MML) file is empty.
Solution:This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.
4022 Monitoring [start] Error: Database error occurred (exception details). |
A database error occurred while accessing MML from the CPDB.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
4024 Monitoring [start] Error: Error occurred (exception-details). |
A monitoring exception occurred.
Solution:View details of the message, then contact http://sun.com/service/contacting/index.html for assistance.
4028 MML Parsing Error: Parsing error occurred (exception details). |
The MML is invalid.
Solution:This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.
4029 MML Parsing Error: I/O error occurred (exception-details). |
An I/O error occurred during parsing of the MML.
Solution:View details of the message, then contact http://sun.com/service/contacting/index.html for assistance.
4030 MML Parsing Error: MML content is empty. |
The MML is empty.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
4033 MML Parsing Warning: Invalid threshold value threshold-volume |
The MML is wrong.
Solution:This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.
4034 MML Parsing Warning: Illegal node-name child node node-ID found. |
The MML is wrong.
Solution:This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.
4035 MML Parsing Warning: Invalid monitor monitor-name encountered. |
The MML is wrong.
Solution:This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.
4036 MML Parsing Warning: No value for integer. |
The MML is wrong.
Solution:This message is associated with the farm's MML. Contact http://sun.com/service/contacting/index.html for assistance.
4037 Remote Command for shutdown invoked successfully, but shutdown has a problem, check the console for device device-ID |
The system in unable to shut down the resource pool server.
Solution:Ensure that the server can be pinged and the N1 Provisioning Server agent is active.
4038 Shutdown of device device-ID failed. Interrupted exception while pinging the device. |
The Java Virtual Machine (JVM) is unable to execute sleep mode while waiting for the device to be stopped.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
4039 MML Parser Error: Cannot create parser with requested configuration (parser-configuration_ exception) |
An error exists in the MML.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
4040 MML Parser Warning: The object warning has an invalid value (threshold) |
An error exists in the MML.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
4042 Monitoring [start] Error: Illegal access error occurred (illegal_access_exception) |
Unable to open the connection to the CPDB.
Solution:Ensure that the CPDB is running and accessible.
Domain Name Service (DNS) and Dynamic Host Configuration Protocol (DHCP) Errors (ID 5000 through 5021)
5000 unable to look up localhost info |
The local server's IP address cannot be determined or obtained.
Solution:Ensure that the local server has an IP address.
5001 IOException exception details |
Error writing to disk.
Solution:Ensure that both /etc/named.conf and /etc/dhcpd.conf are not write-protected.
5002 IOException cannot restart DHCP server |
Internal error
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
5003 unable to instantiate subnet in dhcp sync |
Error when allocating internal objects.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
5004 problem reading the "leasetime" property |
The leasetime property in /etc/opt /terraspring/ tspr.properties is not properly formatted or unreadable.
Solution:Ensure that the line com.terraspring.dns.leasetime exists in the property file, and that it is followed by an equal sign (=) and then an integer.
5005 Interrupted Exception: exception details |
The restart of the dhcpd daemon has been interrupted.
Solution:Issue dhcpdmod sync manually. If this fails, check /etc/dhcpd.conf and try running dhcpd manually in debug mode to see details of the failure.
5007 encountered a null host object while writing dhcp config |
Internal error.
Solution:Restart the segment manager and retry the operation, or reissue the command that encountered this error.
5008 cannot restart DNS server |
The restart of the BIND daemon has failed.
Solution:Issue the dnsmod sync command manually. If this fails, check /etc/named.conf. Try running named manually in debug mode to see details of the failure. Read /var/adm/messages.
5011 SQLException: exception details |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
5012 SQLException: encountered a null attribute object while writing dns config |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
5013 SQLException: encountered a bad attribute object while writing dns config |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
5016 DNS Error: Cannot create zone file directory directory-name. |
For DNS to function properly, a directory must be created for DNS database files. The default directory is /var/opt/ terraspring/named.
Solution:Ensure that the disk is not write-protected.
5017 DNS Error: Zone file directory directory name is not a directory. |
For DNS to function properly, a directory must be created for DNS database files. The default directory is /var/opt/ terraspring/named.
Solution:Ensure that the directory has not been previously created as a file. If so, delete the file and create the directory manually.
5018 DNS Warning: Error occurred (exception details). |
An unexpected exception occurred internally.
Solution:Restart the Segment Manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
5019 DHCP Warning: Error occurred (exception details). |
An unexpected exception occurred internally.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
5020 Unable to open file: |
The system is unable to open the DHCP configuration file.
Solution:Check the file permissions of /etc/dhcp.conf.
5021 Unable to write to file: |
The system is unable to write to the DHCP configuration file.
Solution:Check the file permissions of /etc/dhcp.conf.
Farm Management Errors (ID 6120 through 6823 and 9300 through 9316)
-
CREATED
-
NEW CONFIG
-
ALLOCATED
-
WIRED
-
DISPATCHED
-
ACTIVE
-
SHUTDOWN
-
IDLE
-
UPDATED
-
STANDBY
-
ACTIVE
-
CREATED
-
NEW CONFIG
-
ALLOCATED
-
WIRED
-
DISPATCHED
-
ACTIVE
-
UPDATED
-
SHUTDOWN
-
IDLE
-
NEW CONFIG
-
ALLOCATED
-
WIRED
-
DISPATCHED
-
ACTIVE
-
SHUTDOWN
-
IDLE
-
UPDATED
-
UNWIRED
-
STANDBY
-
CREATED
-
DEACTIVATED
-
ACTIVE
-
SHUTDOWN
-
IDLE
-
UNWIRED
-
CREATED
-
NEW CONFIG
-
ALLOCATED
-
WIRED
-
DISPATCHED
-
ACTIVE
-
SHUTDOWN
-
IDLE
-
UPDATED
-
STANDBY
-
ACTIVE
-
CREATED
-
NEW CONFIG
-
ALLOCATED
-
WIRED
-
DISPATCHED
-
ACTIVE
-
UPDATED
-
SHUTDOWN
-
IDLE
-
NEW CONFIG
-
ALLOCATED
-
WIRED
-
DISPATCHED
-
ACTIVE
-
SHUTDOWN
-
IDLE
-
UPDATED
-
UNWIRED
-
STANDBY
-
CREATED
-
DEACTIVATED
-
ACTIVE
-
SHUTDOWN
-
IDLE
-
UNWIRED
6120
FixedServerConfig.:{error-details}
|
Internal Error.
Solution:Check the logs for earlier messages that might help explain the root of the problem.
6130
{method-name}: No common subnet found between lb {load-balancer-ID} and bind elements.
|
This message is associated with the farm's FML and WML.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6131
LBConfig. {method-name}: No such subnet {subnet-ID} found on lb {load-balancer-ID}.
|
This message is associated with the farm's FML and WML.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6132
LBConfig. {method-name}: Cannot instantiate class: {exception-details}
|
Internal error.
Solution:Restart the segment manager and retry the operation or reissue the command that previously failed.
6133
LBConfig. {method-name}: Cannot access database {exception-details}
|
Database connection error.
Solution:Ensure that the database is running and the connection values are properly specified in /etc/opt/terraspring/tspr.properties.
6134
LBConfig. {method-name}: No such if {logical-network-interface-name} found for device device name.
|
This message is associated with the farm's FML and WML.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6135
LBConfig: {method-name}: bind list empty for lb {load-balancer-ID}
|
This message is associated with the farm's FML and WML.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6136
LBConfig {method-name}: no interface found for lb {load-balancer-ID}
|
This message is associated with the farm's FML and WML.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6137
LBConfig: no interface found for bind element: {bind-element}
|
The load balancer cannot find the interfaces to the bind device.
Solution:This message is associated with the farm's FML. Contact http://sun.com/service/contacting/index.html for assistance.
6300
Farm {farm-id} cannot access the database during allocation (exception-details).
|
Database connection error.
Solution:Ensure that the database is running and the connection values are properly specified in /etc/opt/terraspring /tspr.properties.
6307
SQL Error: Farm {farm-ID} cannot re-allocate physical devices (exception-details).
|
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6308
Config Error: Insufficient resource to re-allocate physical devices in farm
{farm-ID} (exception-details).
|
No more free devices are available for reallocation to the farm.
Solution:Free up resources that are occupied by other farms.
6309
Config Error: Error occurred while re-allocating physical devices in farm
{farm-ID} (exception-details).
|
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6310 SQL Error: Farm farm-ID cannot replace failed devices (device-ID). |
The farm manager was trying to replace a failed device but failed.
Solution:Use the device command to check the device manually.
6311 Config Error: insufficient resource to replace failed device in Farm farm-ID (exception-details). |
No more free devices are available for replacing the failed device.
Solution:Free some resources by deactivating unused farms or add more devices to the resource pool.
6312 Config Error: Error occurred while replacing failed devices in Farm farm-ID (exception-details). |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6313 Config Error: Database error occurred while allocating Farm farm-ID (exception-details). |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6314 Config Error: Insufficient resource to allocate Farm farm-ID (exception-details). |
No more free devices are available for allocation to the farm.
Solution:Free some resources by deactivating unused farms or add more devices to the resource pool.
6315 Config Error: Invalid argument error while allocating Farm farm-ID (exception-details). |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6316 Config Error: Error occurred while allocating Farm farm-ID (exception-details). |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6317 FML Error: Subnet subnet-ID referred in the Interface interface-ID is not defined in the FML. |
The subnet ID is incorrect or does not exist.
Solution:From the Control Center ensure that the correct subnet ID was defined. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details. If the error persists after redefining the correct subnet ID from the Control Center, contact Customer Support for assistance.
6318
FML Error: Subnet {subnet-ID }referred in VIP {VIP ID} for load balancer
{load-balancer-ID} is not defined in the FML.
|
The subnet ID is incorrect or does not exist.
Solution:From the Control Center ensure that the correct subnet ID was defined. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details. If the error persists after redefining the correct subnet ID from the Control Center, contact Customer Support for assistance.
6319
FML error: Subnet {subnet-ID} referred in the intferface {interface-ID}
of load balancer {load-balancer-ID} is not defined in the FML.
|
The subnet ID is incorrect or does not exist.
Solution:From the Control Center ensure that the correct subnet ID was defined. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details. If the error persists after redefining the correct subnet ID from the Control Center, contact Customer Support for assistance.
6320 Alloc Error: Cannot find the FML file for Farm farm-ID (exception-details). |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6329 FML Parser: Null or Empty content |
The FML specifies an invalid empty string.
Solution:Check the FML for syntax accuracy.
6330 FML Parser: Parsing Error (error) |
A parsing error occurred when the FML was parsed.
Solution:Check the FML for syntax accuracy.
6331 FML Parser: I/O error (error) |
An I/O error occurred during FML parsing.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6332 FML Parser: DTD error (error) |
An error occurred while retrieving or using the FML document type definition (DTD) file.
Solution:Check the permissions of the FML DTD file found under /opt/terraspring/etc/fml.dtd.
6333 FML Parser: device-name is not a valid DNS name |
An invalid device name has been entered into the FML.
Solution:Change the device name to a valid DNS name through the Control Center or modify the FML.
6334 FML Parser: Cannot create parser with requested configuration |
An FML parser error occurred.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6335 FML Parsor: Unknown Protocol. |
Internal error.
Solution:This message is associated with the farm's FML. Contact http://sun.com/service/contacting/index.html for assistance.
6340 Wiring Error: Invalid device id device-ID in FAILED state, needs reallocation. |
A failed device has been allocated to a farm.
Solution:Check the database error log for related messages that might help explain the root of the problem.
6341 Wiring Error: Invalid internal state for device id device-ID with FREE device in wired phase. |
Inconsistencies exist in the database.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
6342 Wiring Error: Invalid internal state for device id device-ID marked OFF with power. |
Inconsistencies exist with the physical device and its state in the database.
Solution:Properly shut down the device and try to reactivate the farm.
6343 Wiring Error: Cannot control power of device id device-id (exception-details). |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6344 Wiring Error: Interface interface-ID not found in device id 1. |
Inconsistencies exist in the database.
Solution:This error concerns the device tables that hold all the information on all devices. Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
6345 Wiring Error: I/O error while moving cpu cpu-ID:1 to VLAN VLAN-ID (exception-details). |
Error configuring the switch to move the CPU to the indicated virtual local area network (VLAN).
Solution:Check the accessibility of the switch connected to the CPU device.
6346 Wiring Error: I/O error while hiding cpu cpu-ID:1 to VLAN VLAN-ID (exception-details). |
Error configuring the switch to move the CPU to the idle VLAN.
Solution:Check the accessibility of the switch connected to the CPU device.
6347 Wiring Error: Cannot find device id device-ID. |
Inconsistencies exist in the database.
Solution:This error concerns the device tables that hold all the information on all devices. Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
6350 Wiring Error: Image not found for role role-name. |
The image specified in the FML does not exist in the database.
Solution:Use the image command to list all images. This error concerns the disk and image tables that collectively hold all the information on all images. Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
6352 Wiring Error: I/O error occurred during wiring (exception-details). |
The CPU or disk might be inaccessible.
Solution:Check the physical CPU and disk as well as their connection to ensure accessibility.
6353 Wiring Error: I/O error while unbinding disk error-details. |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6354 Wiring Warning: Device device-id is marked ON with no power, resetting the DB state to OFF |
The device was marked ON but was not powered on.
Solution:Ignore this error.
6355 Wiring Error: Cannot get vlan VLAN-id for farm farm-id |
The control plane VLAN cannot connect to the resource layer VLAN for a device in the farm.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6356 Wiring Error:Image (name: name, id: id) is not ready (error) |
The specified image is not in the ready state.
Solution:Use the image -p and image -r commands to properly prepare and release the image, or select another image that has been properly prepared. See the image man page or Chapter 3, Managing Software Images for details on how to use this command.
6357 Wiring [methodName] Warning: Cannot power off device deviceid |
An error occurred when the system tried to power off the device.
Solution:Use the power tool to check that the device can be powered off by the power controller.
6360 Wiring Error: Cannot remove scsi bindings due to error error-details |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6361 Wiring Error: Copying All Disks for LogicalStorage Device, deviceid, Failed due to error (error) |
An error occurred while copying disks for a storage device.
Solution:Examine the logs for the cause of the failed copy operation. Make sure that the storage manager client (STMC) process is running.
6362 Wiring Warning: A Failed Server has No Snapshot Image, using the original Role Image |
A warning that a failed resource pool server has no snapshot image available to copy to the replacement server.
Solution:Ignore this message.
6363 Wiring Warning: A Standby Farm has No Snapshot Image, using the original Role Image |
A warning that a server that was in standby has no snapshot image available to copy to the new server.
Solution:Check that the local disk was properly snapshot to a standby image. Contact http://sun.com/service/contacting/index.html for assistance if an image is available and done.
6364 Wiring Error: Error Deleting the StandbyImage due to error (error). |
An error occurred while deleting the standby image after activating a farm in standby mode.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6365 Wiring Error: Chosen DiskImage can not be NULL for LogicalDisk [name=diskname, imid=imageId. |
An error occurred while retrieving the image specified for the logical disk.
Solution:Use the image -l command to check for the existence of the image.
6366 Wiring Error: Error Copying Global Disks due to error (error). |
An error occurred while copying an image to the global disks.
Solution:Examine the logs for a possible cause of the failed operation. Check the STMC for indications that might help explain the root of the problem.
6367 Wiring Error: Error Configuring Disks due to (error). |
An error occurred while configuring the disks.
Solution:Check the STMC for indications that might help explain the root of the problem.
6368 Wiring Error: Configuring switch fabric for logical device logical-device-ID failed. |
The switch fabric configuration in the fabric layer for a device failed.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6370 Dispatch Error: Cannot get NIC interface (exception-details). |
An interface specified as associated with a particular farm does not exist in the database.
Solution:Bring the farm to STANDBY and reactivate.
6371 Dispatch Error: Farm farm-id is already dispatched on cp |
A farm is already dispatched on the N1 Provisioning Server.
Solution:Ignore this message.
6373 Dispatch Error: DNS error (error) |
A DNS error occurred during dispatch.
Solution:Check the log for earlier error messages that might help explain the root of the problem.
6374 Dispatch Error: DHCP error (error) |
A DHCP error occurred during dispatch.
Solution:Check the log for earlier error messages that might help explain the root of the problem.
6375 Dispatch Error: Cannot find subnet id subnet-ID. |
A subnet specified as associated with a particular farm does not exist in the database.
Solution:A database inconsistency exists. Contact http://sun.com/service/contacting/index.html for assistance.
6377 Dispatch Error: Illegal argument error (exception-details). |
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6379 Insufficient resource (exception-details) |
Insufficient network interfaces available to complete deployment of the farm.
Solution:Free some of the network interfaces.
6380 FM Dispatch: Cannot find VLAN id for Subnet subnet-ID (VLAN name = VLAN-name). |
Inconsistencies exist between the database and the FML.
Solution:Compare the subnet ID specified in the FML to that in the database. Contact http://sun.com/service/contacting/index.html for assistance.
6381 FM Dispatch: NIC interface for IP address ipaddr does not exist on CP |
Internal error
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6384 Dispatch Warning: No subnet found. |
The farm has no subnet.
Solution:FML must declare at least one subnet. Contact http://sun.com/service/contacting/index.html for assistance if a subnet exists.
6385 Dispatch Error: Farm farm-id has no owner. |
The farm has no owner. The owner might have been removed manually from the CPDB.
Solution:Reactivate the farm. Doing so enables the segment manager to assign an owner automatically.
6386 Dispatch Error: Farm farm-id has a null Runtime/-Logical list. |
The farm has no associated logical resources during dispatch.
Solution:A database inconsistency exists. Contact http://sun.com/service/contacting/index.html for assistance.
6387 Idle Error: Unable to deregister device deviceid |
The system is unable to unregister the device from monitoring during idle state.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6388 FMDispatch Error: Cannot stop customer monitoring for farm farm-id device devicename (deviceid) due to error (error). |
The system cannot stop account monitoring for the device.
Solution:Make sure that the TSPR N1 Provisioning Server agent is running on the device.
6389 Idle Error: Farm farm-id has a null Runtime/Logical list. |
The farm has no associated logical resources during idle state.
Solution:A database inconsistency exists. Contact http://sun.com/service/contacting/index.html for assistance.
6390 Farm farm-id failed to dispatch. |
The farm failed to dispatch.
Solution:Check the log for earlier error messages that might help explain the root of the problem.
6392 Farm farm-id failed to idle. |
The farm failed to idle.
Solution:Check the log for earlier error messages that might help explain the root of the problem.
6400 Activation Error: Cannot register for monitoring (exception-details) |
A device cannot be registered to the monitoring manager for monitoring.
Solution:Refer to Chapter 7, Troubleshooting.
6401 Activation Error: Cannot activate device device-name (device-id). |
The farm failed to activate.
Solution:Check the log for earlier error messages that might help explain the root of the problem.
6402 Activation Error: Cannot shutdown device device-ID device id device-ID (exception-details). |
The device or its power controller might be inaccessible.
Solution:Check the physical device or its power controller to ensure accessibility.
6403 Activation Error: Cannot unconfigure device device-ID device id device-ID (exception-details). |
The device might be inaccessible.
Solution:Check the physical device's power controller to ensure accessibility.
6404 method name Warning: Cannot clean device device-ID (exception-details). |
The system cannot scrub the device.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed. Check the physical device.
6406 Activation Error: No physical device found for logical-id; cannot deregister with. |
No physical devices were found for the associated logical device.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6407 Arp cache of router(s) may need to be cleared. |
Informational message.
Solution:Check whether the ARP cache or router need to be cleared.
6408 method name Error: Cannot power on device device-ID (exception-details). |
An error occurred while trying to power on the device.
Solution:Check the physical device and ensure accessibility and its connection to the power controller.
6409 Activation Error: Waiting for UP Device Status has timed out. |
Some of the devices failed to come up and send an UP event to the farm manager.
Solution:Check whether the device can be pinged and make sure that the monitoring process is running on the CP.
6410 Activation Warning: Property name value value is invalid, using default (default). |
The property value specified is invalid, and a default value will be used.
Solution:Check the tspr.propperties file to see if the property entered is invalid.
6411 Activation Warning: Error occurred while notifying disk addition (exception). |
An error occurred while notifying monitoring of a new disk addition.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6430 Backup Error: SQL Exception while retrieving the DNS name for the fixed-server name=server-name id=server-ID of Farm farm-ID (exception-details). |
The database could not retrieve a valid DNS name for the specified server.
Solution:This error concerns the database table Request that holds all the requests. Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
6460 FMShutdown Warning: Cannot power off device device-ID due to error (error). |
The system cannot power off the device.
Solution:Make sure that the device power controller is configured properly.
6461 method name Error: Cannot power off device device-ID (exception-details) |
The system is unable to power off the device.
Solution:Check the physical device.
6490 FMDeactivate Error: Disks cannot be unconfigured (error) |
The disk cannot be unconfigured.
Solution:Check the STMC for indications that might help explain the root of the problem.
6491 FMDeactivate Error: Disk diskid has error (error). |
An error occurred during farm deactivation.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6492 FMdeactivate Warning: Farm fmid cannot delete image imgname (imgid) of device devname (devid) due to error (error). |
Warning that an image cannot be deleted.
Solution:Check CPDB availability and rerun the command.
6493 FMDeactivate Error: Scrubbing all the Disks due to error (error) |
An error occurred while scrubbing the disks during deactivation or standby.
Solution:Check the STMC for indications that might help explain the root of the problem.
6494 Config Error: Cannot unconfigure the disk disk-ID (exception-details) |
The disk is in an invalid state, it must be in CONFIGURED state.
Solution:Use the disk command to change the state of the disk. See the disk man page.
6495 FM Warning: Scrubbing bypassed for disk (disk-ID) |
Disk scrubbing during deactivation is ignored because the com.terraspring.cs.FM.scrubbing property is set to false.
Solution:If you want disks to be scrubbed during deactivation, set the scrubbing property to true.
6496 FM Warning: Scrubbing bypassed for all disks in farm farm-id. |
Disk scrubbing during deactivation is ignored because the com.terraspring.cs.FM.scrubbing property is set to false.
Solution:If you want disks to be scrubbed during deactivation, set the scrubbing property to true.
6510 FMStandby Warning: Farm 0 cannot rename image imgid of device devname (devid) from origName to newName due to error (error). |
An error occurred while renaming a device's image during standby.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6511 FMStandby Error: Farm farm-id server serverName has failed Scrubbing Disk due to error (error). |
An error occurred while scrubbing a disk during standby.
Solution:Check the tspr.debug log for indications that might help explain the root of the problem.
6512 FMStandby Error: Farm farm-id server serverName has failed due to error (error). |
An error occurred during standby.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6540 Snapshot Error: Cannot find the source disk disk-ID on server server-ID of farm farm-ID. |
A snapshot has been issued on a nonexistent source disk or target.
Solution:The command was probably issued with the wrong parameters. Reissue the command using the correct parameters.
6541 Snapshot Error: Cannot find the destination disk with target disk-ID on host hostname of Farm farm-ID. |
A snapshot has been issued on a nonexistent destination disk or target.
Solution:The command was probably issued with the wrong parameters. Reissue the command using the correct parameters.
6543 Snapshot Error: Image image name already exists. |
An attempt to overwrite an existing snapshot image was made.
Solution:Delete the existing image with the image command or reissue the command using a different name for the image.
6544 Snapshot Error: Cannot create image disk. |
The destination image could not be created for the snapshot.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6545 Snapshot Error: Error occurred (error). |
An error occurred during a snapshot operation.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6546 Snapshot Error: Cannot quiesce fixed-server. |
An error occurred while trying to prepare the device for shutdown.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6547 Snapshot Error: Cannot copy disk. |
An error occurred while trying to copy the disks during snapshot.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6548 Snapshot Error: Cannot shut down fixed-server (name:server-name, id:server-ID) of farm farm-ID due to error (error). |
An error occurred while trying to power off the server for the snapshot operation.
Solution:Check the physical device and ensure accessibility and its connection to the power controller.
6549 Snapshot Error: Cannot re-enable monitoring for CPUDev: cpu-dev-id due to error (error). |
A snapshot error occurred while re-enabling monitoring for the device.
Solution:Ensure that the device is running and that it can be pinged. Ensure that the N1 Provisioning Server agent on the device is running.
6550 Snapshot Error: Cannot query Power for CPUDev: cpu-dev-id due to error (error). |
An error occurred while querying the power status for the device.
Solution:Check the physical device and ensure accessibility and its connection to the power controller.
6551 Snapshot Error: Cannot safely power off Server server because server is not monitored. |
Monitoring is not enabled so the system cannot send a remote procedure call (RPC) message to safely shut down the server.
Solution:Manually shut down the server.
6552 Snapshot Error: Cannot set the Last Snapshot Image: imgageid for LogicalDisk diskid due to error (error). |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6553 Snapshot Error: Device device-ID is not a valid device ID in farm-ID. |
The snapshot operation cannot proceed because the device is not in the specified farm.
Solution:Check the resources allocated to the farm and correct the inputs to the snapshot.
6554 Snapshot Error: FixedServer server-ID of Farm farm-ID does not contain CPUs. |
Inconsistencies exist in the database.
Solution:This error concerns the device tables that hold all the information on all devices. Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
6555 FM Error: Snapshot failed (farm id: farm-ID, hostname: hostanme, target: disk-ID, image name: image-ID, console id: console-ID) with the following message: exception-details. |
A snapshot operation failed.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6580 FMMonitor Error: Error occurred. |
Error occurred during an FMMonitor operation.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6581
FMMonitor Error: Cannot start monitoring for farm {fmid} on device {deviceid}
due to error ({exception}).
|
Monitoring for the device cannot be started.
Solution:Check that the monitoring service is running. Contact http://sun.com/service/contacting/index.html for assistance.
6582
FMMonitor Error: Cannot stop monitoring for farm {fmid} on device {deviceid}
due to error {exception}.
|
Monitoring for the device cannot be stopped.
Solution:Check that the monitoring service is running. Contact http://sun.com/service/contacting/index.html for assistance.
6583
FM Warning: Cannot quiesce storage device (name: {device name}, id: {deviceid})
due to error ({error}).
|
The resource pool server cannot be prepared for shutdown.
Solution:Ensure that the N1 Provisioning Server agent is running on the resource pool server and that the device can be pinged.
6584
Monitoring Warning: Server {servername} cannot be notified of {adding/remove} disk {diskinfo}
due to error ({error}).
|
A problem with notifying the monitoring system of a change in a resource pool server's disk occurred.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6585
Monitoring Warning: Cannot find image for disk {diskid} due to error ({error}).
|
Monitoring cannot find the image for the disk. Inconsistencies in the database exist.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6586
Monitoring Warning: Cannot find DNS name for device {deviceid} due to error ({error}).
|
Monitoring cannot get the DNS name for the device.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6620
Farm {fmid}: needs to unblock an update request for failover of device {devid}.
|
A request to replace a failed device has been queued and blocked for a device in the farm.
Solution:Check the device. If the device needs to be replaced, unblock the queued request.
6621
Error occurred when retrieving Farm {fmid}'s context onto CP {cp name}.
|
An error occurred while trying to redispatch the farm onto the control plane (CP).
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6622
Farm {fmid}'s old InProgress Requests were Interrupted.
|
An in-progress farm request was abruptly interrupted.
Solution:Reissue the request to the farm.
6623
Warning: Device {device ID} Device id {device ID} is not a network device,
so cannot act as a gateway.
|
The FML specifies that the device act as a gateway.
Solution:Ensure that a network device is specified as a gateway within the FML.
6661
FM Warning: Storage-device (name: {dev name}, id: {dev id}) has no power controller;
cannot power it {errMsg}.
|
The storage device has no power controller associated.
Solution:Use the device -lv command to check the device's connections to the power controller.
6662
FM Warning: Storage-device (name: {dev name}, id: {dev id} has no configuration class;
cannot shut it down.
|
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6663
FM Warning: Cannot power off storage-device (name: {dev name}, id: {dev id})
due to error ({error Msg}).
|
An error occurred while powering off the storage device.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6664
FM Warning: Cannot power on storage-device (name: {dev name}, id: {dev id})
due to error ({error Msg}).
|
An error occurred while powering on the storage device.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6701
FarmManagerImpl: SQLException in method {method name}, Farm {farm ID}:
({Exception Details}).
|
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6702
FarmManagerImpl: IllegalArgument Exception in method {method name}, Farm {farm ID}:
({Exception Details}).
|
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6703
FarmManagerImpl: IllegalState Exception in method {method name}, Farm {farm ID}:
({Exception Details}).
|
The farm manager for a farm has been instructed to make an illegal state transition.
Solution:Do not issue illegal state transition instructions.
For activating a farm, the following values are legal states:
For updating a farm, the following values are legal states:
If a previous attempt of updating a farm failed and no changes were made, the following states are also valid:
For deactivating a farm, the following values are legal states:
For deleting a farm, the following values are legal states:
For putting a farm into standby mode, the following values are legal states:
6704
FarmManagerImpl: Failed to reach state {State No}.
|
The farm manager has encountered errors.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6705
FarmManagerImpl: Failed to get subnet number from {subnet}.
|
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6706
FarmManagerImpl: Error occurred in method {method} farm {fmid}: ({error})
|
Internal error.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6707
FM Error: Cannot snapshot image {imageid} on node {dnsname} target {target} of
farm {fmid} due to error ({error}).
|
An error occurred while taking a snapshot of an image on the node's target disk.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6708
FM Error: Cannot snapshot configuration for device {dev id} of farm {farm id}
due to error ({error}).
|
An error occurred while taking a snapshot the configuration of a device.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6801
SQLException in method {method name}, Farm {farm ID}, at host {hostname}:
{exception details}.
|
Internal error.
Solution:Restart the segment manager (refer to Chapter 7, Troubleshooting) and retry the operation, or reissue the command that previously failed.
6802
IllegalArgument Exception in method {method name}, Farm {farm ID}.
|
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6803
IllegalState Exception in method {method name}, Farm {farm ID}.
|
The farm manager for a farm has been instructed to make an illegal state transition.
Solution:Do not issue illegal state transition instructions.
For activating a farm, the following values are legal states:
For updating a farm, the following values are legal states:
If a previous attempt of updating a farm failed and no changes were made, the following states are also valid:
For deactivating a farm, the following values are legal states:
For deleting a farm, the following values are legal states:
For putting a farm into standby mode, the following values are legal states:
6804
PostService Exec found Farm {farm ID} with error {error NO} in {State NO}.
|
Internal error.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6808
SM: on {CP server ID} can not start, ({Segment Manager ID}) not removed.
|
A segment manager is already running.
Solution:Stop and restart the segment manager.
6809
SM: {Aid} cannot create ({Aid Filename}).
|
A file must be created when the segment manager starts and this file cannot be created.
Solution:Check that the disk has read/write permissions.
6812
SM: moveFarm ({fmid}) to same CP ({cp}) not allowed.
|
An attempt was made to move the farm to the same CP on which it already resides.
Solution:Use the farm -m command to specify another CP.
6813
SM: moveFarm ({fmid}) to CP machine ({cp}) does not have enough interfaces.
|
The CP does not have enough interfaces to support the move of the farm.
Solution:Use the farm -m command and move the farm to an CP with enough free interfaces.
6814
SM: moveFarm ({fmid}) failed to remove the CP Context from SM {sm}: {error}.
|
The source CP had an error removing the farm's CP interface from the CP.
Solution:Check the source CP's log for earlier messages that might help explain the root of the problem.
6818
{method}: SM {smname} encountered error ({error}).
|
The segment manager process experienced a monitoring error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6819
{method}: SM {smname} has no timestamp.
|
The segment manager has no timestamp.
Solution:Ensure that the segment manager is running. Stop and restart the segment manager if necessary.
6820
{method}: SM {smname} encountered SQL error ({error}).
|
Internal error.
Solution:Check the database. Stop and restart the segment manager if necessary.
6821
{method}: SM {smname} encountered illegal access error ({error}).
|
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
6822
FMException in method {method} from farm {fmid}.
|
Internal error.
Solution:Check the log for earlier messages that might help explain the root of the problem.
6823
SM {spname} stat request error ({error}).
|
An error occurred while processing the sminfo request.
Solution:Retry the sminfo command. Stop and restart the segment manager if necessary.
9300
FM Error: Internal error, cannot set state {state NO}({Exception Details}).
|
Unable to update an entry in the Farm table.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
9302
FM Error: Farm id {farm ID} does not exist.
|
The specified farm does not exist in the farm table.
Solution:Refer to Chapter 7, Troubleshooting for details on how to remedy database problems.
9303
{classname} invalid classname ({error}).
|
The specified class name is invalid.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9304
Unexpected exception: {error}.
|
An unexpected error has occurred.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9305
FM Error: {method} for farm {fmid} encountered error ({error}).
|
Internal error.
Solution:Check the log for earlier messages that might help explain the root of the problem.
9306 FMDispatch Error: Cannot clear config. |
An error occurred while removing the network interface card (NIC) interfaces on the CP for a farm.
Solution:Check the log for earlier messages that might help explain the root of the problem.
9307
FMDispatch Error: Cannot get DNS/DHCP handle for farm {fmid} due to error ({error}).
|
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9308
FMDispatch Warning: {DNS/DHCP} sync for farm {fmid} failed due to error ({error});
continuing
|
An error occurred while synchronizing the configuration for the DNS or DHCP daemons.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9309
FMDispatch Warning: Cannot sync customer monitoring for farm {fmid}
due to error ({error}).
|
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9310 FMDispatch Error: Cannot delete node from monitoring for farm fmid device devname (id=devid, ip=ipaddr) due to error (error). |
The system cannot delete a device node from monitoring.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9311 FM Warning: Farm fmid had error state state in db; resetting to state. |
Informational warning.
Solution:Ignore this message.
9312 FM Error: state state (stateid) is not valid. |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9313 FMDispatch Error: Cannot check monitoring for registration of the farm fmid, node nodeid due to error (error). |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
9314 FM Error: Error occurred (error) |
An error occurred during a farm action.
Solution:Check the log for earlier messages that might help explain the root of the problem.
9315 Error: Database error occurred (error). |
An error occurred while accessing the database.
Solution:Check the log for earlier messages that might help explain the root of the problem.
9316 FM Error: Invalid Goal State goal-state from state current-state. |
Internal error.
Solution:Contact http://sun.com/service/contacting/index.html for assistance.
- © 2010, Oracle Corporation and/or its affiliates