Message ID |
Message |
|---|---|
KARS13000-E |
Internal process terminated abnormally. [Cause] An unexpected error occurred. (Job ID = xxx) [Solution] If you are a system administrator, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS13001-W |
Requests are suspended. [Cause] Processing many requests. (Job ID = xxx) [Solution] If you are a system administrator, wait a while, and then retry the operation. If you are a VPS administrator, wait for a while, and then retry the operation. If the same error occurs, report the message contents to the system administrator. |
KARS13002-W |
Invalid request has been detected. [Cause] The request was rejected due to environmental factors. (Job ID = xxx) [Solution] Confirm Job ID, and then issue the request again if necessary. |
KARS13003-I |
Suspends acceptance of requests. [Event Name] Suspension of receiving requests [Category] Service [Solution] Processing many requests. Do not send any requests for a while. |
KARS13004-I |
Resumes acceptance of requests. [Event Name] Restart of receiving requests [Category] Service |
KARS13005-E |
The job could not be stopped. [Cause] There is no Job to be stopped. [Solution] See the job list, and check the existence and status of the job to be stopped. |
KARS13006-E |
An unexpected error occurred. (Job ID = xxx) [Event Name] Internal error [Category] Service [Solution] Collect the logs, and then contact customer support. |
KARS13007-W |
The request was rejected because many requests are being processed. (Job ID = xxx) [Event Name] Suspension of receiving requests [Category] Service [Solution] Wait a while, and then retry the operation. |
KARS13008-W |
The request was rejected due to environmental factors. (Job ID = xxx) [Event Name] Detection of rejecting requests [Category] Service [Solution] Confirm Job ID, and then issue the request again if necessary. |
KARS13009-I |
The job has started. (Operation = xxx, Job ID = xxx) [Event Name] Start of job [Category] Service Note: User operation changed the job status. Although "xxx" of "Operation= xxx" in the message indicates a CLI subcommand, the user operation that caused job status transition was not necessarily through the CLI. It might be through another user-operated interface, such as a REST API. |
KARS13010-I |
The job has completed successfully. (Operation = xxx, Job ID = xxx) [Event Name] Successful completion of job [Category] Service Note: User operation changed the job status. Although "xxx" of "Operation= xxx" in the message indicates a CLI subcommand, the user operation that caused job status transition was not necessarily through the CLI. It might be through another user-operated interface, such as a REST API. |
KARS13011-I |
The job has ended abnormally. (Operation = xxx, Job ID = xxx) [Event Name] Failure to complete job [Category] Service [Solution] See the error details with the job ID described in the message, and then take action. Note: User operation changed the job status. Although "xxx" of "Operation= xxx" in the message indicates a CLI subcommand, the user operation that caused job status transition was not necessarily through the CLI. It might be through another user-operated interface, such as a REST API. |
KARS13012-I |
The job has stopped. (Operation = xxx, Job ID = xxx) [Event Name] Stop of job [Category] Service Note: User operation changed the job status. Although "xxx" of "Operation= xxx" in the message indicates a CLI subcommand, the user operation that caused job status transition was not necessarily through the CLI. It might be through another user-operated interface, such as a REST API. |
KARS13013-W |
The request was rejected. [Cause] An unsupported request was specified. (Job ID = xxx) [Solution] If you are a system administrator, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS13014-W |
The request was rejected because it was not supported. (Job ID = xxx) [Event Name] Detection of unknown requests [Category] Service [Solution] Collect the logs, and then contact customer support. |
KARS13015-E |
The request was rejected. [Cause] Base license is invalid. (Job ID = xxx) [Solution] Purchase a base license. Or, if the event log (KARS11014-E) is output, see the event log, and then take the required action. |
KARS13016-E |
The request was rejected because the base license is invalid. (Job ID = xxx) [Event Name] Invalid base license [Category] Service [Solution] Purchase a base license. Or, if the event log (KARS11014-E) is output, see the event log, and then take the required action. |
KARS13017-E |
The request was rejected. [Cause] License is invalid. (Job ID = xxx, Program product name = xxx) [Solution] Inform the Program product name to the license issuer, and purchase a license. |
KARS13018-E |
The request was rejected because the license is invalid. (Job ID = xxx, Program product name = xxx) [Event Name] Invalid program product license [Category] Service [Solution] Inform the Program product name to the license issuer, and purchase a license. |
KARS13019-E |
An invalid request was detected. [Cause] The request was rejected because the storage cluster was being started or blocked. (Job ID = xxx) |
KARS13020-E |
The request was rejected because the storage cluster was being started or blocked. (Job ID = xxx) [Event Name] Rejecting requests due to the storage cluster in starting process or in blocked [Category] Service |
KARS13101-I |
The storage node is recovered from maintenance by the auto-recovery function. (Storage node ID = xxx) [Event Name] Storage node auto-recovery [Category] StorageNode |
KARS13102-E |
The storage node is in persistent blockage status. (Storage node ID = xxx, Cause = xxx) [Event Name] The storage node is in persistent blockage status [Category] StorageNode |
KARS13104-E |
Internal processing terminated abnormally. [Cause] An unexpected error occurred. [Solution] Collect the logs, and then contact customer support. |
KARS13105-I |
The auto-recovery function performs replacement of the storage node. (Storage node ID = xxx) [Event Name] Storage node replacement by the storage node auto-recovery function [Category] StorageNode |
KARS13106-I |
Spare node switchover is automatically performed to recover the storage node because a spare node is registered. (Storage node ID = xxx) [Event Name] Change to the target of spare node switchover [Category] StorageNode |
KARS13107-I |
The auto-recovery function performs spare node switchover for the storage node. (Storage node ID = xxx, Spare node ID = xxx) [Event Name] Spare node switchover by the storage node auto-recovery function [Category] StorageNode |
KARS13110-E |
A configuration backup file could not be created. [Cause] Another operation that conflicts with this operation is in progress. [Solution] Wait a while and execute the operation again. |
KARS13111-E |
A configuration backup file could not be created. [Cause] The software version is different between storage nodes. [Solution] Complete the software update, and then retry the operation. |
KARS13112-E |
A configuration backup file could not be created. [Cause] A problem might have occurred in the environment or storage cluster. |
KARS13113-E |
A configuration backup file could not be created. [Cause] An unexpected error occurred. |
KARS13114-E |
A configuration backup file could not be created. [Cause] This is not supported configuration for making configuration backup file. |
KARS13115-E |
A configuration backup file could not be created. [Cause] Drive data relocation is manually aborted. |
KARS13116-E |
A configuration backup file could not be created. [Cause] Switching of the write back mode with cache protection has not been completed. |
KARS13117-E |
A configuration backup file could not be created. [Cause] A storage node on which the number of installed drives (for which storage pool expansion was performed) is less than three exists. |
KARS13118-E |
A configuration backup file could not be created. [Cause] Accesses to the database are congested, or the database is not operating correctly. [Solution] Wait a while, and then retry the operation. |
KARS13119-E |
A configuration backup file could not be created. [Cause] An internal error occurred. [Solution] Wait for a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS13120-I |
Creation of a configuration backup file started. [Event Name] Configuration backup file creation started [Category] StorageCluster |
KARS13121-I |
Creation of a configuration backup file is completed. Downloading of a configuration backup file starts. [Event Name] Configuration backup file creation completed [Category] StorageCluster |
KARS13122-E |
A configuration backup file could not be created. [Event Name] Configuration backup file creation failure due to other conflicting operations [Category] StorageCluster [Solution] Wait a while and execute the operation again. |
KARS13123-E |
A configuration backup file could not be created. [Event Name] Configuration backup file creation failure due to mixed software versions [Category] StorageCluster [Solution] Complete the software update, and then retry the operation. |
KARS13124-E |
A configuration backup file could not be created. [Event Name] Configuration backup file creation failure due to failure detection [Category] StorageCluster |
KARS13125-E |
A configuration backup file could not be created. [Event Name] Configuration backup file creation failure due to unsupported configuration [Category] StorageCluster |
KARS13126-E |
A configuration backup file could not be created. [Event Name] Configuration backup file creation failure due to manual suspension of drive data relocation [Category] StorageCluster [Solution] and complete drive data relocation. Then, reperform backup of configuration information. |
KARS13127-E |
A configuration backup file could not be created. [Event Name] Configuration backup file creation failure by switching write back mode with cache protection [Category] StorageCluster [Solution] the storage cluster or cancel switching of the write back mode with cache protection. Then, reperform backup of configuration information. |
KARS13128-E |
A configuration backup file could not be created because there are less than three drives for which storage pool expansion has been performed. (Storage node ID = xxx, Deficit number of drives = xxx) [Event Name] Configuration backup file creation failed because of insufficient storage devices [Category] StorageCluster [Solution] Perform storage pool expansion for the drive whose status is Offline on the specified storage node. If there are insufficient drives, add drives to the specified storage node, and then perform storage pool expansion. Then, reperform backup of configuration information. |
KARS13129-E |
A configuration backup file could not be created because the database could not be accessed. [Event Name] Configuration backup file creation failed because of a database access error [Category] StorageCluster [Solution] Wait for a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS13130-E |
Restore of configuration information failed. [Cause] The configuration restoration function is already running. [Solution] Specify the storage node on which the configuration restoration function was already executed, and then run the storage_restoration_status_show command. (Node name = xxx, Node address = xxx) |
KARS13131-E |
Internal process terminated abnormally. [Cause] An unexpected error occurred. [Solution] Wait a while, and then retry the operation. If the error persists, collect the logs, and then contact customer support. |
KARS13132-E |
Restore of configuration information failed. [Cause] Prerequisites for performing the operation are not met. |
KARS13133-E |
A configuration backup file could not be created because an internal error occurred. [Event Name] Configuration backup file creation failed because of an internal error [Category] StorageCluster [Solution] Wait for a while, and then retry the operation. If the same error occurs, collect the logs, and then contact customer support. |
KARS13140-E |
Restore of configuration information failed. [Cause] The configuration backup file is corrupted. |
KARS13141-E |
Restore of configuration information failed. [Cause] An unexpected error occurred. |
KARS13142-E |
Restore of configuration information failed. [Cause] The configuration backup file is invalid. [Solution] Destroy the storage cluster, and then retry the restore operation of the configuration information with another configuration backup file. |
KARS13143-E |
Restore of configuration information failed. [Cause] An unexpected error occurred. (Failed nodes = xxx) |
KARS13144-E |
Restore of configuration information failed. [Cause] The version of configuration backup file and the one of the storage cluster you installer is different. [Solution] Use configuration backup file which version is coincide with the storage cluster. Or, install a storage cluster again with the correct version, and then retry restore operation. (Storage cluster version = xxx, Configuration backup file version = [configuration_backup_file_version]) |
KARS13201-E |
The request could not be executed. [Cause] The specified parameters are invalid. [Solution] Verify the parameter settings, and then retry the operation. |
KARS13202-E |
The request could not be executed. [Cause] Operations that cannot be executed concurrently are being executed. [Solution] Verify whether no other operation is being performed. If no other operation is being performed, retry the operation. If any other operation is being performed, wait until it is complete, and then retry the operation. |
KARS13203-E |
The request could not be executed. [Cause] Accesses to the database are congested, or the database is not operating correctly. [Solution] Wait a while, and then retry the operation. |
KARS13204-E |
The request could not be executed. [Cause] Memory is insufficient. [Solution] See the event logs, confirm that no job is running, and then retry the operation. If the error persists, collect the logs, and then contact customer support. |
KARS13205-E |
The request could not be executed. [Cause] The required parameter is not specified. [Solution] Verify the parameter settings, and then retry the operation. |
KARS13210-E |
An encryption key could not be created. [Cause] The maximum number of encryption keys that can be created has been exceeded. [Solution] Review the number of encryption keys to be created. If the number of encryption keys to be created exceeds the upper limit, delete unnecessary encryption keys, and then retry encryption key creation. |
KARS13211-E |
An encryption key could not be created. [Cause] The encryption environment setting is not enabled. [Solution] Enable the encryption environment setting. |
KARS13212-E |
Not all the encryption keys could be created. (The number of created encryption keys = xxx) [Cause] Accesses to the database are congested, or the database is not operating correctly. [Solution] Wait a while, and then retry the operation. |
KARS13213-E |
Not all the encryption keys could be created. (The number of created encryption keys = xxx) [Cause] Memory is insufficient. [Solution] See the event logs, confirm that no job is running, and then retry the operation. If the error persists, collect the logs, and then contact customer support. |
KARS13214-E |
Not all the encryption keys could be created. (The number of created encryption keys = xxx) [Cause] An unexpected error occurred. [Solution] Collect the logs, and then contact customer support. |
KARS13215-E |
The encryption key could not be deleted. [Cause] The specified encryption key has already been assigned to a drive. (Drive ID = xxx) [Solution] Check the parameters. |
KARS13216-E |
The encryption key could not be deleted. [Cause] The specified encryption key does not exist. [Solution] Check the parameters. |
KARS13220-E |
The request could not be executed. [Cause] In an environment in which storage pool expansion has been performed, this operation cannot be performed. [Solution] To change the setting, reperform the operation from storage cluster configuration. |
KARS13221-E |
The request could not be executed. [Cause] The specified storage pool does not exist. [Solution] Check the parameters. |
KARS13223-E |
Editing of encryption environment settings did not succeed and some setting edits could not be applied. (Number of created encryption keys = xxx) [Cause] Accesses to the database are congested, or the database is not operating correctly. [Solution] Wait a while, and then retry the operation. |
KARS13224-E |
Editing of encryption environment settings did not succeed and some setting edits could not be applied. (Number of created encryption keys = xxx) [Cause] An unexpected error occurred. [Solution] Collect the logs, and then contact customer support. |
KARS13225-E |
The request could not be executed. [Cause] The encryption environment setting is not enabled. [Solution] Enable the encryption environment setting. |
KARS13226-E |
The request could not be executed. [Cause] When the encryption setting of the storage pool is enabled, the encryption environment setting cannot be disabled. [Solution] See storage pool information to verify the encryption setting, and then disable the encryption setting. In an environment in which storage pool expansion has already been performed, the encryption setting cannot be disabled. To change the setting, reperform the operation from storage cluster configuration. |
KARS13230-E |
The request could not be executed. [Cause] An error occurred while assigning encryption keys to drives. [Solution] See the event logs with the same job ID as this job, and then take action. |
KARS13231-E |
The request could not be executed. [Cause] The specified drive has already been assigned an encryption key. (Drive ID = xxx) |
KARS13232-E |
The request could not be executed. [Cause] An unexpected error occurred while assigning encryption keys to drives. [Solution] Collect the logs, and then contact customer support. |
KARS13279-E |
The request could not be executed. [Cause] An unexpected error occurred. [Solution] Collect the logs, and then contact customer support. |
KARS13280-W |
The number of encryption keys that have not been assigned to encryption targets is below the threshold. (Number of unassigned encryption keys = xxx) [Event Name] Caution on the number of unassigned encryption keys [Category] Encryption [Solution] Create an encryption key as required. |
KARS13281-W |
The number of encryption keys to be assigned to encryption targets is insufficient. (Job ID = xxx, Deficit number of unassigned encryption keys = xxx) [Event Name] The number of unassigned encryption keys is insufficient [Category] Encryption [Solution] Create the deficit number of encryption keys. |