https://www.orchest.io/ logo
Powered by
Title
a

Alexsander Pereira

10/05/2022, 5:47 PM
What would this error be? 
[W 2022-10-05 17:45:33.160 ServerApp] HTTP 500: Internal Server Error (Error attempting to connect to Gateway server url '<http://jupyter-eg-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e:8888/jupyter-server-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e>'.  Ensure gateway url is valid and the Gateway instance is running.)
r

Rick Lamers

10/05/2022, 5:49 PM
This means that the Jupyter Enterprise Gateway container could not be reached. This container is started as part of a session. The container image is 
orchest/jupyter-enterprise-gateway
On the cluster you have Orchest installed, do you have access to 
k9s
?
a

Alexsander Pereira

10/05/2022, 5:52 PM
I'm using EKS (AWS)
The gateway is running
r

Rick Lamers

10/05/2022, 5:53 PM
When debugging these issues having access to the EKS cluster with 
k9s
can be very useful. You could quickly check for example the logs of the jupyter-enterprise-gateway to see whether there is an issue with it (some error).

https://www.youtube.com/watch?v=hwMevai3_wQ▾

This might be helpful if you haven't used k9s + EKS before
a

Alexsander Pereira

10/05/2022, 5:54 PM
See logs with Kubernetes Dashboard.
r

Rick Lamers

10/05/2022, 5:55 PM
(Kubernetes Dashboard should be sufficient too 👍 just a tip) Do you see any errors in the gateway log? You can also dump the log here and we can scan it for potential issues
a

Alexsander Pereira

10/05/2022, 6:01 PM
Any way to recreate a jupiter notebook?
Some jupyter notebooks were deleted to free up space in the cluster.
r

Rick Lamers

10/05/2022, 6:05 PM
recreate a jupiter notebook
Do you mean restore a Jupyter notebook file (e.g. 
my-notebook.ipynb
)?
a

Alexsander Pereira

10/05/2022, 6:06 PM
Not, I would like to recreate the deployment and pods that were deleted.
r

Rick Lamers

10/05/2022, 6:07 PM
If you start a new session (in the Orchest UI) it should create the deployment/pods automatically. They're managed by the 
orchest-controller
.
A session is started by opening a pipeline file (e.g. 
main.orchest
) in the pipeline editor
a

Alexsander Pereira

10/05/2022, 6:11 PM
It worked, but I still have a problem with the gateway. 
HTTP 500: Internal Server Error (Error attempting to connect to Gateway server url '<http://jupyter-eg-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e:8888/jupyter-server-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e>' . Ensure gateway url is valid and the Gateway instance is running.)
r

Rick Lamers

10/05/2022, 6:14 PM
Can you paste the logs of the gateway?
a

Alexsander Pereira

10/05/2022, 6:18 PM
I just found out I don't have enough pods.
r

Rick Lamers

10/05/2022, 6:18 PM
Do you mean nodes? That it couldn't schedule the pod on a node? (What error did you find?)
From the log I can see that the 
orchest-api
could not be reached by the 
jupyter-enterprise-gateway
. Meaning that while the gateway tried to start the kernel by calling 
orchest-api
(a POST request), it failed to reach 
orchest-api
. Can you confirm the 
orchest-api
pod is running without errors (as reported by the k8s dashboard)?
I'll be AFK for a bit. Please leave any notes here if you still have issues and we'll help you out tomorrow 🙌
a

Alexsander Pereira

10/05/2022, 6:39 PM
The type of machine I'm using in the EKS only lets up 29 pods.
@Rick Lamers Any ideas on how to get around this pod limit? https://github.com/awslabs/amazon-eks-ami/blob/master/files/eni-max-pods.txt
y

Yannick

10/06/2022, 8:06 AM
As you can read in the Kubernetes docs (link and link) it is possible to set `ResourceQuota`s that determine the number of Pods someone is allowed to run. I am not sure whether EKS uses `ResourceQuota`s to enforce these limits, nor whether it would be possible to change them. I guess your best bet would be to upgrade the instance type so that you can spawn more Pods. Given the resources that Pods consume, EKS probably came up with (somewhat) sensible limits to prevent you from overloading the instance/node.
r

Rick Lamers

10/06/2022, 8:33 AM
Looks like a workaround could be https://stackoverflow.com/a/69715615
a

Alexsander Pereira

10/06/2022, 1:34 PM
Now all pods are OK, but communication error with jupyter gateway may continue: HTTP 500: Internal Server Error (Error attempting to connect to Gateway server url 'http://jupyter-eg-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e:8888/jupyter-server-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e'. Ensure gateway url is valid and the Gateway instance is running.)
r

Rick Lamers

10/06/2022, 1:47 PM
From the log I can see the gateway is failing to reach the 
orchest-api
. (It's getting a 404). Running 
wget -O - <http://orchest-api/api/sessions>
in the gateway container would establish that the Orchest API is reachable from the gateway. Worth checking that quickly to establish a baseline.
a

Alexsander Pereira

10/06/2022, 1:58 PM
The request works. 
(base) root@jupyter-eg-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e-b6fd6b89-qpb4s:/usr/local/bin# wget -O - <http://orchest-api/api/sessions>
--2022-10-06 13:56:18-- <http://orchest-api/api/sessions>
Resolving orchest-api (orchest-api)... 10.100.209.91
Connecting to orchest-api (orchest-api)|10.100.209.91|:80...connected.
HTTP request sent, awaiting response... 308 PERMANENT REDIRECT
Location: <http://orchest-api/api/sessions/> [following]
--2022-10-06 13:56:18-- <http://orchest-api/api/sessions/>
Reusing existing connection to orchest-api:80.
HTTP request sent, awaiting response... 200 OK
Length: 2135 (2.1K) [application/json]
Saving to: 'STDOUT'
r

Rick Lamers

10/06/2022, 2:02 PM
Then it could be the case that the specific project/pipeline UUID that it's trying to start the kernel for don't have an active session. The gateway container has two environment variables ORCHEST_PROJECT_UUID and ORCHEST_PIPELINE_UUID. Can you confirm that the session endpoint (you truncated the output of that wget command) have a session that has the project and pipeline UUID that are the environment variables of the gateway? (You can inspect the gateway environment variables e.g. by running 
env
or checking the k8s manifest).
a

Alexsander Pereira

10/06/2022, 2:07 PM
{
  "project_uuid": "e4fd61e1-cfee-426a-83aa-1b0230681b16",
  "pipeline_uuid": "0bee97bf-8b41-4d2e-a502-45fd3f139f5d",
  "status": "RUNNING",
  "base_url": "/jupyter-server-e4fd61e1-cfee-426a0bee97bf-8b41-4d2e",
  "user_services": {
    "data-app": {
      "name": "data-app",
      "image": "environment@d839e5bc-ce97-479b-841f-2403e6e86a33",
      "order": 1,
      "ports": [
        8000
      ],
      "scope": [
        "interactive",
        "noninteractive"
      ],
      "exposed": false,
      "requires_authentication": true
    },
    "fast-api": {
      "name": "fast-api",
      "image": "environment@d839e5bc-ce97-479b-841f-2403e6e86a33",
      "order": 2,
      "ports": [
        8000
      ],
      "scope": [
        "interactive",
        "noninteractive"
      ],
      "exposed": false,
      "requires_authentication": true
    },
    "tensorboard-demo": {
      "name": "tensorboard-demo",
      "image": "environment@d839e5bc-ce97-479b-841f-2403e6e86a33",
      "order": 3,
      "ports": [
        8000
      ],
      "scope": [
        "interactive",
        "noninteractive"
      ],
      "exposed": false,
      "requires_authentication": true
    }
  }
}
y

Yannick

10/06/2022, 3:15 PM
@Alexsander Pereira You could try to trigger a build of the JupyterLab image: settings > configure jupyterland > build. Although we didn’t change the jupyter-server and gateway dependencies some time, still worth a shot.
r

Rick Lamers

10/07/2022, 10:26 AM
@Alexsander Pereira did you verify that the environment variables of ORCHEST_PROJECT_UUID and ORCHEST_PIPELINE_UUID match any of the session objects you get from the /api/sessions/ object?
a

Alexsander Pereira

10/07/2022, 12:51 PM
Yes, match. And the build didn't work either.
y

Yannick

10/07/2022, 2:02 PM
And the build didn't work either.
Okay that is strange... Could you share the 
OrchestCluster
object so that we can see what parts of the system you've configured. Thanks
a

Alexsander Pereira

10/07/2022, 2:15 PM
apiVersion: <http://orchest.io/v1alpha1|orchest.io/v1alpha1>
kind: OrchestCluster
metadata:
  name: cluster-1
  namespace: orchest
  annotations:
    <http://controller.orchest.io/deploy-ingress|controller.orchest.io/deploy-ingress>: "false"
spec:
  singleNode: true
  orchest:
    version: v2022.10.0
    authServer:
      image: public.ecr.aws/u5k1d2l0/orchest-auth-server:v2022.10.0-1.0.2
    orchestWebServer:
      image: public.ecr.aws/u5k1d2l0/orchest-webserver:v2022.10.0-1.0.2
y

Yannick

10/07/2022, 2:51 PM
And so when freshly installing the above 
OrchestCluster
you can't build JupyterLab and you can't connect to the 
Gateway
? (Asking again to make sure I have everything correct.)
a

Alexsander Pereira

10/07/2022, 2:52 PM
Yes!
Orchest Controller YAML
orchest-controller.yml
y

Yannick

10/07/2022, 2:55 PM
And you are running on a single-node EKS cluster? Nothing "special" there?
a

Alexsander Pereira

10/07/2022, 2:55 PM
Yes, is a EKS Single-Node: r5.xlarge
y

Yannick

10/07/2022, 3:11 PM
Hmmm... doesn't ring a bell for me whatsoever. @Navid H Any ideas?
🙌 1
n

Navid H

10/07/2022, 3:14 PM
@Alexsander Pereira: Could you kill docker-registry pod (so new one will be created) and try again. never mind
@Alexsander Pereira: Can you check the jupyter-egw and the associated service labels and see if they match?
👀 1
It can also be lack of resources for core dns pod.
a

Alexsander Pereira

10/07/2022, 5:05 PM
I will do these checks, the DNS can is up and running. I'm creating a new cluster to see if the problem can only be in this one.
y

Yannick

10/10/2022, 8:06 AM
I'm creating a new cluster to see if the problem can only be in this one.
Any luck? 🤞
2 Views
#announcementsJoin Slack
Powered by