-
Notifications
You must be signed in to change notification settings - Fork 43
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
Pods are running but registry is unresponsive at some point after installation #144
Comments
Hey team, we just ran into this same exact issue, same symptoms as well. I thought perhaps we just had a one-off issue, but then noticed this issue, so I thought I'd add a comment. I'll get some troubleshooting logs posted here. I can connect via netcat to port It just.... stops responding to http traffic. |
I should have captured the output, but failed to - I did notice that a curl -vvv https://<quay-server>:8443 | head
* Rebuilt URL to: https://<quay-server>:8443/
* TCP_NODELAY set
* Connected to <quay-server> port 8443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
< hangs right here where we should get a Server hello> We never get the server hello back, nor anything beyond that - and, as noted above the port is open and responds via |
Anyone find a solution to this issue? We had a newly installed mirror registry that was working just fine for a week or two suddenly start exhibiting this behavior. We've ruled out all sorts of networking issues, time sync, disk and permission issues, etc. Everything seems perfectly healthy and functional except that the quay-app makes no reply to any communication. There is a window of a few seconds about 15 seconds after a quay-app restart where it will respond normally but then it just stops. No more log entries from nginx at all and no errors of any sort but no replies either. For a moment we thought we'd solved it by running a mirror-registry upgrade. We initially had the exact container versions listed in SalaryTheft's original post and noticed the current mirror registry made some major changes like swapping out pgsql for sqlite. So we ran the upgrade and the mirror-registry became responsive and stayed that way overnight. However, it didn't survive a service restart. We are now on these container versions and back to a completely healthy but unresponsive registry:
Any hint or workaround would be appreciated. |
All the pods are running but registry server is unresponsive at some point after installation.
(no response at
curl https://localhost:8443
)I have to restart the pods or even have to reboot the host to get it working.
All the pods are running:
New logs are comming up, so the containers are running fine... I guess?
Nothing strange on the
quay-app
container deatails.The text was updated successfully, but these errors were encountered: