Skip to content
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

Gogs Probe Failures - getsockopt: connection refused #82

Open
deepjyotsingh opened this issue Mar 15, 2018 · 2 comments
Open

Gogs Probe Failures - getsockopt: connection refused #82

deepjyotsingh opened this issue Mar 15, 2018 · 2 comments

Comments

@deepjyotsingh
Copy link

I'm getting the following errors on RHEL 7.3 while starting the Gogs pod, has anyone run into this same issue? Appreciate any help.

Unhealthy
Readiness probe failed: Get http://172.17.0.7:3000/: dial tcp 172.17.0.7:3000: getsockopt: connection refused

Unhealthy
Liveness probe failed: Get http://172.17.0.7:3000/: dial tcp 172.17.0.7:3000: getsockopt: connection refused

@Johnny2136
Copy link

I drastically increased the amount of ram and it seems to work, also the readiness probe was set to a really short cycle I set it to like 30 sec. Hope this helps.

@ikke-t
Copy link

ikke-t commented May 22, 2018

This seems to be caused due too short times allowed for gogs parts to start. Both work once manually started, but then again, the script has already failed setting the mirror and webhook. They also need to be done manually

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants