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

Websocket connection reset on sign-in (not sign up) #24

Open
alastairong opened this issue Sep 23, 2020 · 4 comments
Open

Websocket connection reset on sign-in (not sign up) #24

alastairong opened this issue Sep 23, 2020 · 4 comments

Comments

@alastairong
Copy link
Contributor

Steps to reproduce:
With chaperone.holohost.dev running 2020-09-17-fix-retrieve-host-agent-key

  1. Go totestfuel.holo.host
  2. Sign-up
  3. Refresh browser on freeze (or sign-in again if necessary

Screenshot 2020-09-23 at 13 14 16

)
@alastairong
Copy link
Contributor Author

Envoy logs showed a validation failure. I don't have those logs to hand right now

@mjbrisebois
Copy link
Contributor

mjbrisebois commented Sep 24, 2020

I have gone over all the logs from Envoy and there is not enough information to determine where the root cause is.

What I am seeing

  • many anonymous requests come in
  • service request logs seem to be successful
  • zome calls all fail because there is no public instance
  • service response logs seem to be successful
  • confirmations start coming in but fail because HostResponse entry not found (which I think is the commit hash for the request response log)

Since the service response logs appear to be successful, the entries should be there. I cannot determine if log_response is returning a false-positive, or if log_service (confirmation) is failing to find an existing entry. Perhaps @zippy has insight here.

Let's wait for PR #22 to be merged so that the logging is clearer. Then we can evaluate the next steps for debugging.

cc @alastairong

@alastairong
Copy link
Contributor Author

Note: when I originally saw this issue holo-envoy logs showed no activity
When @zippy tried to debug it yesterday 25 Sep he again saw no envoy log activity

@alastairong
Copy link
Contributor Author

It could be that this is not related to envoy and the logs we saw were accidental

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

2 participants