How Do I Resolve Error "AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct" When I Start the Agent?
Symptom
The AK and SK of your Huawei Cloud account were entered in the Agent, but the AK/SK-based authentication fails. The specific error message depends on the OS.
- Windows: AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct."
- Linux: AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct.
For details about how to obtain an AK/SK pair, see How Do I Create an AK/SK Pair for a Huawei Cloud Account? or How Do I Create an AK/SK Pair for an IAM User?
Possible Causes
Possible causes are:
- The entered AK or SK is incorrect.
- The system time of the source server is consistent with the local standard time.
- The time zone in the source server is configured incorrectly.
- The AK/SK pair has been deleted or disabled.
- The programmatic access method is not enabled for the Huawei Cloud account you used for migration.
Handling Methods
- Case 1: The entered AK or SK is incorrect.
Check whether the entered AK/SK pair of the Huawei Cloud account is correct, especially whether any spaces or characters are missed during the copy. Enter the AK/SK pair for authentication again.
- Case 2: The system time of the source server is consistent with the local standard time.
Check whether the system time of the source server is consistent with the standard time of the time zone where the source server is located.
If it is not, change the system time to the local standard time, and enter the AK/SK pair for authentication again.
If services on the source server depend on the system time, check whether the time can be changed to avoid impact on services.
- Case 3: The time zone in the source server is configured incorrectly.
Change the time zone in the source server so that the system time plus the time zone is equal to the standard UTC time. For details, see Changing the Time Zone. Enter the AK/SK pair for authentication again.
- Case 4: The AK/SK pair has been deleted or disabled.
- Case 5: The programmatic access method is not enabled for the Huawei Cloud account you used for migration.
- Log in to the management console.
- Click the username in the upper right corner and choose Identity and Access Management.
- In the navigation pane on the left, choose Users and click the username you used for migration.
- On the Basic Information tab page, check whether Programmatic access is selected for Access Type.
- If it is not, click , select Programmatic access, and click OK.
Agent Installation and Startup FAQs
- How Do I Download and Install the Agent on Source Servers?
- What Can I Do If I Fail to Download the Agent Installation File?
- How Do I Verify the Integrity of the Agent Installation File?
- Why Wasn't My Source Server Added to the SMS Console After I Configured the Agent?
- How Do I Configure Certificate Verification in the SMS-Agent Configuration File?
- Where Can I Find the Agent Run Logs?
- Why Is My Target Server Locked During the Migration?
- How Do I Unlock a Target Server Manually?
- How Do I Resolve Error "rsync not installed on the source server" When I Start the Agent Installed on a Linux Source Server?
- How Do I Resolve Error "The application cannot be started due to incorrect parallel configuration" When I Start the Agent?
- Why Does the Agent Not Start the First Time I Launch It?
- Why Does the Windows Agent Executable Not Run When I Double-Click It?
- How Do I Fix Error "Failed to start the I/O monitoring module" When I Start the Agent?
- How Do I Fix Error "INTERNAL ERROR: cannot create temporary directory!" When I Start the Agent?
- How Do I Resolve Error "AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct" When I Start the Agent?
- How Do I Troubleshoot Failures of Pasting the AK/SK Pair When I Start the Agent (Python 2)?
- How Do I Resolve Error "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte" When I Start the Agent?
- How Do I Resolve Error "Failed to load wmi" During the Agent Startup?
- How Do I Restart the Agent?
- How Do I Fix Agent Startup Failures Due to Insufficient Space in /tmp on a Linux Source Server?
- How Do I Fix Error "Agent startup failed because the noexec permission is not allowed on /tmp for SMS Agent. Please remount /tmp without noexec" When I Start the Linux Agent?
- How Do I Resolve Error "Only servers with x86 architecture can be migrated"?
- How Do I Fix Error "Failed to start sms agent! 'disks'" When I Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.1901, Agent cannot read disk information" When I Start the Agent Installed on a Windows Source Server?
- How Do I Fix Error "Failed to obtain information about disk X" When I Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.6562: component i386-pc not found on source server. For solution, see SMS API Reference." When I Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.6563: File initrd or initramfs of the xxxx version not found under /boot directory. For solution, see SMS API Reference." When I Start the Agent on a Linux Source Server?
- How Do I Choose When the System Asks Whether to Disable the Google Services Detected on My Source Server on the Google Cloud?
- How Do I Fix Error "SMS.0410: Failed to obtain NicName/IPAddress information of source server " When I Start the Agent on a Linux Server?
- What Do I Do If the SMS-Agent Fails to Start and Error "SMS.0609 An earlier version of Agent is detected. Please exit the old Agent, uninstall the old Agent completely, and install the latest version" Is Displayed?
- How Do I Fix Error "SMS.1353: Bind mount or repeated mount detected on /xxx of the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.1352: Unknown physical volumes detected on the source server" When I Fail to Start the Agent on a Linux Source Server?
- How Do I Fix Error "SMS.1351: Mount point /xxx detected on the source server, which has no free space. Ensure that there is at least 1 MB of space" When I Fail to Start the Agent on a Linux Source Server?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore