search

ministryofjustice / analytics-platform

Parent repository for the MOJ Analytics Platform
MIT License
14 stars 1 forks source link

"Unable to establish connection with R session" #101

Closed davidread closed 1 year ago

davidread commented 5 years ago

CG is suffering this in R Studio: connection

It’s occurred just now ... while trying to switch between Projects. Everything else seems to be working okay. I wondered whether it was my wifi but it doesn’t appear to be. It won’t even let me quit properly. All I can do at this point is X the tab, log out of AP and start again (and I usually paste my code into a blank doc just in case I lose any unsaved changes)... I have lost work every now and again if I’ve not saved prior to it crashing.

Related:

I keep getting a 503 error, and now can't start R at all. It's now working but this is something that keeps happening (most days). I end up closing down my R session and restarting until it works. Is there something else I can do to prevent losing data, or something I can do to stop it happening in the first place? I've get 502 errors quite regularly

This user is working on DOM1.

It might be due to flaky home wifi? Is a serious issue for this user.

davidread commented 5 years ago

RM just experienced this:

this has just happened to me right now, in case it is useful for you to see an example in progress. I was just viewing an array and scrolling down through it when it disconnected. I tried to view the array again and got a 503 error in the console. I refreshed and got a 503 in the browser.

The pod shows some events. He flagged it happening 10 minutes ago, so the second one is most relevant:

  Warning  Unhealthy  16m   kubelet, ip-192-168-10-250.eu-west-1.compute.internal  Liveness probe failed: Get http://100.96.49.15:3000/healthz: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy  11m   kubelet, ip-192-168-10-250.eu-west-1.compute.internal  Readiness probe failed: Get http://100.96.49.15:8787/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
davidread commented 5 years ago

We found that the node went bad briefly - NodeNotReady. So the 11 people with R Studio on this node suffered a short period of outage at this time. This would manifest as 503 and connection errors, as described.

So that's the explanation. Sorry about the disruption. We'll look at what we can do to prevent this in future.