-
Notifications
You must be signed in to change notification settings - Fork 364
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
🐛[bug] Kernel status: pending #8976
Comments
hello, this is new and unexpected, we've never seen an issue like that. can you please share the task logs after you try to launch a kernel? (go to Tasks in det UI, find your notebook, click triple dots on the right -> View logs) are you using the default environment image or a custom one? |
Hi @ioga,
|
I've searched the jupyter github for these A couple ideas:
|
Same errors:
From the Chrome client I get 200 from all requests apart from these few requests: |
I just tried the 0.29.0 version and I get the same problem. This is the log:
|
In my previous experiments I was using Kubernetes 1.29, I have now tried to deploy a new Kubernetes 1.26 cluster but I have got the same problem. O don't know what to try more... any suggestion? |
How to solve this error in the log?
|
I tried Determined 0.28.0 package with similar results:
|
And this is the log with Determined 0.27.0 version:
|
I initially tested to ensure it was working correctly with the Determined LoadBalancer and without HTTPS. I discovered that the problem was related to my NGINX Ingress. I solved the issue by annotating the ingress to enable the WebSocket connection: |
great, thanks for the update. |
Describe the bug
I deployed Determined on AWS EKS Kubernetes cluster using the Helm chart. I tested to execute the MNIST experiment and worked perfectly. When I try to launch a new Jupyter Notebook, the new pod with the determined-container start correctly and the new window showing the Jupyter Notebook page. When I try to start a New Notebook the Kernel status remain in connecting state.
Reproduction Steps
Expected Behavior
Run correctly the notebook
Screenshot
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: