-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when using Helm and S3 #24
Comments
Same problem here. # curl -v http://localhost:3000/readyz
* Trying 127.0.0.1:3000...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 3000 (#0)
> GET /readyz HTTP/1.1
> Host: localhost:3000
> User-Agent: curl/7.67.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< Content-Type: application/json
< Date: Tue, 02 Mar 2021 07:21:29 GMT
< Content-Length: 0
<
|
@teochenglim @tanora do either of you see anything in logs that shows an error specific to S3 or similar? |
@arschles That's no any helpful error message from the kubernetes pod. All we see is bunch of 200 (/healthz) and 500 (/readyz) status code because of helm charts's readiness. A more verbose debug log option would be helpful. i think it is from https://github.com/gomods/athens/blob/main/charts/athens-proxy/templates/deployment.yaml#L59-L70 INFO[12:04PM]: incoming request http-method=GET http-path=/readyz http-status=500
INFO[12:04PM]: incoming request http-method=GET http-path=/healthz http-status=200
INFO[12:04PM]: incoming request http-method=GET http-path=/readyz http-status=500
The other possible question is when the endpoint /readyz is not ready, how do we debug it? |
indeed the /readyz seems from this code and it only return the http status If some log is written somewhere would be good. Or maybe also return the "err" on what ready happen would be so helpful. The problem can range from permission error, the connection established error would be prefect. |
closes gomods/athens#5 closes #25 closes #24 --------- Co-authored-by: Nicholas Wiersma <nick@wiersma.co.za>
Describe the bug
ForcePathStyle is not included in the chart. I have tried setting ForcePathStyle to true and false.
Error Message
Logs from pod
When describing pod:
To Reproduce
Using Kube2iam and ingress is enabled.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: