- Newest
- Most votes
- Most comments
Hello The following procedures will help you troubleshoot the endpoint health check issue even if the /ping endpoint displays a 200 status:
Perform a thorough analysis of the CloudWatch logs.
Analyze the CloudWatch logs for the endpoint in detail, keeping an eye out for any failures, warnings, or unusual activity that might be interfering with the health check success. When the health check fails, pay special attention to the logs. Verify that there are no conflicts within the container and that no resource exhaustion or dependency errors exist.
Check the Model Artifacts:
In the S3 tarball archive, make sure the adjusted model artifacts are appropriately packaged. Verify the presence of all required files and dependencies for the proper operation of the model. The model may not load correctly if any files are missing or corrupted, which could result in failed health checks.
Relevant content
- asked 4 months ago
- asked 4 years ago
- asked 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
Unfortunately nothing suspicious: no errors, tracebacks or warnings, application was started, then a lot of successful /ping responses. After process hit container_startup_health_check_timeout_in_seconds limit it was terminated