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

Health endpoint timeout #445

Closed
jdknives opened this issue Jul 21, 2020 · 1 comment · Fixed by #448
Closed

Health endpoint timeout #445

jdknives opened this issue Jul 21, 2020 · 1 comment · Fixed by #448
Assignees
Labels
bug Something isn't working

Comments

@jdknives
Copy link
Member

Describe the bug
When running skywire-visor and hypervisor on test deployment, the calls to get the health related infos are timing out:

2020/07/21 12:22:08 "GET http://localhost:8000/api/visors/0329cf58890dcbb16d52f9879b362d0234afe1680ce286dbf7ef74714caa70fdad/health HTTP/1.1" from [::1]:58892 - 408 15B in 5.000385542s

Also, the route finder and transport discovery are red and displayed as not online.

Environment information:

  • OS: Mac OS X

Steps to Reproduce

Setup a visor and a hypervisor on the same machine. Navigate to the visor page and you may get the same error. Not sure whether it can be reproduced with better network conditions.

@jdknives jdknives added bug Something isn't working documentation Improvements or additions to documentation milestone 4 labels Jul 21, 2020
@jdknives jdknives removed the documentation Improvements or additions to documentation label Jul 21, 2020
@jdknives
Copy link
Member Author

I did a few more tests and it does not always time out. It takes a visor about 5 seconds or more to return the health endpoint.

@nkryuchkov nkryuchkov linked a pull request Jul 23, 2020 that will close this issue
@nkryuchkov nkryuchkov self-assigned this Jul 23, 2020
@jdknives jdknives closed this as completed Aug 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants