-
Notifications
You must be signed in to change notification settings - Fork 16
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
Hub and single-user notebook fail to connect out-of-the-box #24
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
This appears to be the same issue dealt with in #23. I have not tried the fix there, and it's not obvious to me why it was never merged? |
@ajs6f have you tested it with Jupyterhub 5.1.0? I'm encountering a runtime warning and unable to access the provided URLs after the server starts. The warning and logs are as follows
Even though the server appears to start and the URLs are generated, I am unable to access the JupyterLab interface via the provided URLs (e.g., http://node2:53601/user/hadoop/lab?token=...). Afterward, the skein application running on Yarn is killed, and the user fails to spawn. The user cannot access their environment or run JupyterLab. What could be causing this runtime warning, and could it be related to the access issue?
Any guidance would be greatly appreciated. Thank you! |
I'm sorry to say that we gave up on this mode of deployment, @raibrahim. We are moving on to using Kubernetes for resource management. |
Thanks to much help from @mahendrapaipuri at this issue I was able to fix this bug. I can prepare a PR if that is desired.
Bug description
There is an error in
YarnSpawner
'syarnspawner/yarnspawner/singleuser.py
Lines 15 to 19 in 1c40f52
After v3 of JupyterHub, HubAuth._api_request() is now an
async
method.A corrected
YarnSingleUserNotebookApp.start(self)
looks like:Expected behaviour
I thought the hub would correctly wait for the single-user notebook to be spawned and then communicate therewith.
Actual behaviour
The single-user notebook spawns, the hub and notebook exchange activity messages, but the hub never correctly returns from the notebook spawn and eventually kills the notebook, even though it was running perfectly well.
How to reproduce
Install and configure YarnSpawner. This will happen every time.
Your personal set up
CentOS Linux release 7.9.2009 (Core)
Full environment
Configuration
The text was updated successfully, but these errors were encountered: