Message ID |
Message |
|---|---|
KARS20000-E |
Internal processing terminated abnormally. [Cause] An unexpected error occurred. [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. |
KARS20001-E |
Internal processing terminated abnormally. [Cause] An unexpected error occurred. [Solution] If you are a system administrator, perform maintenance blockade for the cluster master node (primary). Block the cluster master node (primary), and then retry the operation. If the error occurs again, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20002-E |
Internal processing terminated abnormally. [Cause] An unexpected error occurred. [Solution] If you are a system administrator, wait a while, and then retry the operation. If the error occurs again, collect the logs, and then contact customer support. 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. |
KARS20003-E |
The request could not be executed. [Cause] The information specified by the parameter does not exist. [Solution] Specify the argument of the parameter correctly. |
KARS20004-E |
The request could not be executed. [Cause] The number of xxx reached the upper limit. [Solution] Delete unnecessary xxx, and then retry the operation. |
KARS20005-E |
The request could not be executed. [Cause] xxx cannot be specified if xxx is xxx. [Solution] Specify the parameter correctly. |
KARS20006-E |
The request could not be executed. [Cause] xxx is already in use. [Solution] Specify the parameter correctly. |
KARS20007-E |
The request could not be executed. [Cause] Any change that will cause the number of valid users having a Security or Service role privilege to become 0 is not allowed. [Solution] Create a user having the Security or Service role, and then retry the operation. |
KARS20008-E |
The request could not be executed. [Cause] The user does not have a role required for the operation. [Solution] Verify the role setting. |
KARS20009-E |
The request could not be executed. [Cause] The number of sessions reached the upper limit. [Solution] Retry the operation after a while. Or retry the operation after deleting unnecessary sessions. |
KARS20010-E |
The request could not be executed. [Cause] xxx failed. [Solution] Specify the parameter correctly. |
KARS20011-E |
User authentication failed. [Cause] For Basic authentication, the specified user ID or password is incorrect, or the account is invalid or locked. For session authentication, the specified token is incorrect or the session is invalid. [Solution] For Basic authentication, specify the correct user ID and password, or enable the account if the account is invalid. If the account is locked, do so after the account is unlocked. For session authentication, specify the correct token. If the session is invalid, do so after you regenerate a session. |
KARS20012-E |
User authentication failed. [Cause] The password has expired. |
KARS20014-E |
The request could not be executed. [Cause] The password complexity rules were not followed. [Solution] Set a password following the password complexity rules. |
KARS20015-E |
The request could not be executed. [Cause] It is prohibited to change the password again. [Solution] Wait until you can change the password again, and retry the operation. |
KARS20016-E |
The request could not be executed. [Cause] This API can be executed only for the cluster master node (primary). [Solution] Execute the API for the cluster master node (primary). |
KARS20017-E |
The request could not be executed. [Cause] A conflict occurred in the user management operation processing. [Solution] Retry the operation after a while. |
KARS20018-E |
The request could not be executed. [Cause] The maximum number of user groups to which a user can belong has been reached. [Solution] Delete the user from unnecessary user groups, and then retry the operation. |
KARS20019-E |
The request could not be executed. [Cause] A user group to which the user belongs cannot be deleted. [Solution] Delete all users who belong to the user group, and then retry the operation. |
KARS20020-E |
The request could not be executed. [Cause] A user must belong to at least one user group. [Solution] Specify the parameter correctly. |
KARS20021-E |
The request could not be executed. [Cause] The operation for a built-in user or user group is prohibited. [Solution] Review the operation target. |
KARS20022-E |
The request could not be executed. [Cause] This operation is prohibited for an external user group. [Solution] Review the operation target. |
KARS20023-E |
A failover of the cluster master node occurred during processing. [Cause] An error occurred on the cluster master node (primary). [Solution] Perform the reference operation corresponding to the setting operation and verify whether the setting is reflected. If the setting is not reflected, perform the setting operation again. |
KARS20024-E |
The request could not be executed. [Cause] If the DNS server is not set, True cannot be specified for isStartTlsEnabled and ldaps cannot be specified for primaryLdapServerUrl or secondaryLdapServerUrl. [Solution] Specify the parameter correctly. |
KARS20025-E |
The request could not be executed. [Cause] ldap and ldaps cannot both be specified for primaryLdapServerUrl and secondaryLdapServerUrl. [Solution] Specify the parameter correctly. |
KARS20026-E |
User authentication failed. [Cause] Only session authentication can be used for this request. [Solution] Use session authentication for this request. |
KARS20050-E |
User authentication with the authentication ticket did not succeed. [Cause] User ID, password, or the authentication ticket is not correct. [Solution] Review the user ID, password, and the authentication ticket. |
KARS20051-E |
User authentication with the authentication ticket did not succeed. [Cause] The authentication ticket has expired. [Solution] Issue new authentication ticket. |
KARS20052-E |
An authentication ticket could not be created. [Cause] Basic authentication must be used to create an authentication ticket. [Solution] Create an authentication ticket with Basic authentication. |
KARS20053-E |
User authentication failed. [Cause] An authentication ticket is required for authentication. [Solution] Create an authentication ticket. |
KARS20054-E |
The request could not be executed. [Cause] The operation for the storage cluster conflicts with another one. [Solution] Wait a while, and then retry the operation. If you are performing another update operation, wait until it is complete, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. |
KARS20055-E |
The operation cannot be started due to conflict with another operation for the storage cluster. (Job ID = xxx) [Event Name] Conflict with another storage cluster operation [Category] StorageCluster [Solution] Wait a while, and then retry the operation. If you are performing another update operation, wait until it is complete, and then retry the operation. If the phenomenon does not change, collect the logs, and then contact customer support. Note: This message is published by ticket revocation API. (POST /v1/objects/tickets/actions/revoke-all/invoke, ticket_revoke_all) The message is associated with KARS20054-E provided in the response of ticket revocation REST API or CLI. Take action according to KARS20054-E and then ignore KARS20055-E message. |
KARS20056-E |
An issued authentication ticket could not be invalidated for the storage node. (Storage node ID = xxx) [Event Name] Authentication ticket invalidation failed [Category] StorageCluster |
KARS20057-E |
The part of the request did not end normally. [Cause] An issued authentication ticket could not be invalidated for some storage nodes. |
KARS20058-E |
Internal processing terminated abnormally. [Cause] An error occurred during the authentication process. |
KARS20061-E |
The request could not be executed. [Cause] If you want to use the specified user in the console interface, authentication must be local. [Solution] If you are a system administrator, for the user to be used in the console interface, specify local for authentication. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20062-E |
The request could not be executed. [Cause] If you want to use the specified user in the console interface, the user must have a Security or Service role privilege. [Solution] If you are a system administrator, specify a user group for the user to be used in the console interface so that the user has a Security or Service role privilege. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20063-E |
The request could not be executed. [Cause] The user cannot be disabled because doing so causes the number of users that can be used in the console interface to become 0. [Solution] If you are a system administrator and there are other users that are permitted to be used in the console interface but whose password is not changed, change their passwords, and then retry the operation. If there are no other users that are permitted to be used in the console interface, create such a user, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20064-E |
The request could not be executed. [Cause] When enabling a user that is permitted to be used in the console interface, you also need to specify a password. [Solution] If you are a system administrator, specify a password. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20065-E |
The request could not be executed. [Cause] Any operation that will cause the number of users that are permitted to be used in the console interface to become 0 is not allowed. When forced password change is set in the user authentication settings before the initial login, a user whose password has not yet been changed is not allowed to be used in the console interface. [Solution] If you are a system administrator and there are other users that are permitted to be used in the console interface but whose password is not changed, change their passwords, and then retry the operation. If there are no other users that are permitted to be used in the console interface, create such a user, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20066-E |
The request could not be executed. [Cause] The user cannot be deleted because doing so causes the number of users that are permitted to be used in the console interface to become 0. [Solution] If you are a system administrator and there are other users that are permitted to be used in the console interface but whose password is not changed, change their passwords, and then retry the operation. If there are no other users that are permitted to be used in the console interface, create such a user, and then retry the operation. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20067-I |
User information was reflected to the console interface. (Storage node ID = xxx) [Event Name] User information reflection to the console interface [Category] StorageNode |
KARS20068-I |
User authentication settings were reflected to the console interface. (Storage node ID = xxx) [Event Name] User authentication setting reflection to the console interface [Category] StorageNode |
KARS20069-I |
A login message was reflected to the console interface. (Storage node ID = xxx) [Event Name] Login message reflection to the console interface [Category] StorageNode |
KARS20070-E |
Internal processing terminated abnormally. [Cause] An unexpected error occurred. [Solution] If you are a system administrator, delete the user, and then create a user again. If the same error occurs, collect the logs, and then contact customer support. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20071-E |
The request could not be executed. [Cause] Only certain characters can be specified for user names to be used in the console interface. (Detailed information = xxx) [Solution] If you are a system administrator, specify the parameter correctly. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20072-W |
User information, authentication settings, or login messages could not be reflected to the console interface. (Storage node ID = xxx) [Event Name] Failure to reflect to console interface [Category] StorageNode [Solution] If this message is output repeatedly, collect the logs, and then contact customer support. If a message indicating that reflection to the console interface was successful is output after this message, there is no problem. |
KARS20073-E |
The request could not be executed. [Cause] The specified user group contains a user permitted to use the console interface. For this reason, both the Security role and Service role cannot be deleted. [Solution] If you are a system administrator, reedit the user group roles while adding the Security role or Service role to the user group. Alternatively, add the user that is permitted to use the console interface and belongs to the specified user group to a different user group with the Security role or Service role. Then, reedit the roles of the specified user group. If you are a VPS administrator, report the message contents to the system administrator. |
KARS20080-E |
The request could not be executed. [Cause] If you specified the parameter of a VPS ID, you must also specify the same VPS ID for the parameter of a scope. If the VPS ID parameter was omitted, the ID of the VPS to which the user who performed this operation belongs must be specified in the parameter of a scope. [Solution] When you specify the parameter of a VPS ID, also specify the same VPS ID for the parameter of a scope. If the VPS ID parameter is omitted, specify the ID of the VPS to which the user who performed this operation belongs in the parameter of a scope. |
KARS20081-E |
The request could not be executed. [Cause] The ID of a non-existent VPS was specified for the parameter of a scope. [Solution] Specify the parameter correctly. |
KARS20082-E |
The request could not be executed. [Cause] You do not have access right to the VPS specified for the parameter of a VPS ID. [Solution] Verify whether a user who performed this operation has access right to the specified VPS. If the user does not have access right, make the user belong to an appropriate user group, and then retry the operation. Or, specify the ID of the VPS to which the user who performed this operation has access right. |
KARS20083-E |
The request could not be executed. [Cause] If you specified the parameter of a VPS ID, you must also specify the same VPS ID for the parameter of a scope for a user group who manages the VPS. If the VPS ID parameter was omitted, the ID of the VPS to which the user who performed this operation belongs must be specified in the parameter of a scope for a user group who manages the VPS. [Solution] When you specify the parameter of a VPS ID, also specify only the same VPS ID for the parameter of a scope. If the VPS ID parameter is omitted, specify only the ID of the VPS to which the user who performed this operation belongs for the parameter of a scope. |
KARS20084-E |
The request could not be executed. [Cause] One or more roles not applicable to a system administrator is specified for a user group of a system administrator. [Solution] Specify the parameter correctly. |
KARS20085-E |
The request could not be executed. [Cause] One or more roles not applicable to a VPS administrator is specified for a user group of a VPS administrator. [Solution] Specify the parameter correctly. |
KARS20086-E |
The request could not be executed. [Cause] The ID of the VPS to which the operation-target user group belongs is not specified for the parameter of a scope for a user group who manages the VPS. [Solution] Specify only one ID of the VPS to which the operation-target user group belongs for the parameter of a scope. |
KARS20087-E |
The request could not be executed. [Cause] You must include the ID of the VPS to which the operation-target user group belongs for the parameter of a scope. [Solution] Specify the parameter correctly. |
KARS20088-E |
The request could not be executed. [Cause] All the user groups to be specified must belong to the same VPS. [Solution] Specify user groups belonging to the same VPS. |
KARS20089-E |
The request could not be executed. [Cause] You do not have access right to the specified user group. [Solution] Verify whether a user who performed this operation has access right to the scope that the specified user group has. If the user does not have access right, make the user belong to an appropriate user group, and then retry the operation. Or, specify the user group with scope to which the user who performed this operation has access right. |
KARS20090-E |
The request could not be executed. [Cause] Users to be used on the console interface must be a system administrator. [Solution] Specify a user group who manages the entire storage system for userGroupIds. Or, when you do not use the console interface, specify "false" for isEnabledConsole. |
KARS20091-E |
The request could not be executed. [Cause] The maximum number of system administrator users has been reached. [Solution] Delete unnecessary system administrator users, and then retry the operation. |
KARS20092-E |
The request could not be executed. [Cause] The maximum number of VPS administrator users has been reached for the entire storage system. [Solution] Delete unnecessary VPS administrator users, and then retry the operation. Or, report the message contents to the system administrator and ask them to delete other VPS administrator users. |
KARS20093-E |
The request could not be executed. [Cause] The maximum number of users that can belong to the VPS has been reached. [Solution] Delete unnecessary VPS administrator users, and then retry the operation. |
KARS20094-E |
The request could not be executed. [Cause] The maximum number of user groups who can manage the entire storage system has been reached. [Solution] Delete unnecessary user groups who manage the entire storage system, and then retry the operation. |
KARS20095-E |
The request could not be executed. [Cause] The maximum number of user groups who can manage a VPS has been reached for the entire storage system. [Solution] Delete unnecessary user groups who manage a VPS, and then retry the operation. Or, report the message contents to the system administrator and ask them to delete user groups who manage other VPSs. |
KARS20096-E |
The request could not be executed. [Cause] The maximum number of user groups that can be registered for the VPS has been reached. [Solution] Delete unnecessary user groups who manage the VPS, and then retry the operation. |
KARS20097-E |
The request could not be executed. [Cause] The specified limit value is lower than the number of users created in the VPS. [Solution] Reduce the number of users belonging to the VPS or increase the maximum number of users to equal to or more than the number of users belonging to the target VPS, and then retry the operation. |
KARS20098-E |
The request could not be executed. [Cause] The specified limit value is lower than the number of user groups created in the VPS. [Solution] Reduce the number of user groups belonging to the VPS or increase the maximum number of user groups to equal to or more than the number of user groups belonging to the target VPS, and then retry the operation. |
KARS20099-E |
The request could not be executed. [Cause] The specified limit value is lower than the number of sessions created in the VPS. [Solution] Reduce the number of sessions of users belonging to the VPS or increase the maximum number of user sessions to equal to or more than the number of sessions of users belonging to the target VPS, and then retry the operation. |
KARS20100-E |
The request could not be executed. [Cause] More than one user group belongs to the VPS. [Solution] Delete user groups belonging to the VPS, and then retry the operation. |
KARS20101-E |
The request could not be executed. [Cause] The maximum number of sessions of a system administrator has been reached. [Solution] Delete unnecessary sessions of a system administrator, and then retry the operation. |
KARS20102-E |
The request could not be executed. [Cause] The maximum number of sessions of a VPS administrator has been reached for the entire storage system. [Solution] Delete unnecessary sessions of a VPS administrator, and then retry the operation. Or, report the message contents to the system administrator and ask them to delete sessions of other VPS administrators. |
KARS20103-E |
The request could not be executed. [Cause] The maximum number of sessions of users belonging to the VPS has been reached. [Solution] Delete unnecessary sessions of a VPS administrator, and then retry the operation. |
KARS20104-E |
The request could not be executed. [Cause] User groups to be specified must belong to the same VPS as that of the operation-target users. [Solution] Specify user groups belonging to the same VPS as that of the operation-target users. |