Help Center>
ModelArts>
Troubleshooting>
Training Jobs>
Permission Issues>
What Should I Do If Error "stat:403 reason:Forbidden" Is Displayed in Logs When a Training Job Accesses OBS
Updated on 2024-04-30 GMT+08:00
What Should I Do If Error "stat:403 reason:Forbidden" Is Displayed in Logs When a Training Job Accesses OBS
Symptom
When a training job accesses OBS, an error occurs.
Figure 1 Error log
Possible Causes
The possible causes are as follows:
- The OBS permission is incorrect. As a result, data cannot be read.
Solution
Verify that OBS permissions are correctly assigned. If the problem persists, troubleshoot by following the instructions provided in Why Can't I Access OBS (403 AccessDenied) After Being Granted with the OBS Access Permission?.
Summary and Suggestions
Before creating a training job, use the ModelArts development environment to debug the training code to maximally eliminate errors in code migration.
- Use the online notebook environment for debugging. For details, see Using JupyterLab to Develop a Model.
- Use the local IDE (PyCharm or VS Code) to access the cloud environment for debugging. For details, see Using the Local IDE to Develop a Model.
- If an error occurred in OBS, identify the cause based on the error information, including the error code and message. For details about OBS error codes, see OBS Server-Side Error Codes.
Parent topic: Permission Issues
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
