Open dstndstn opened 1 year ago
I think you shouldn't use wrapspawner from git right now, try the latest release instead? See #54. There's some confusion about what version that fix actually worked for, it must be a very old one. I think we ought to revert that or at least move it off to some other branch for "study."
Actually I guess you said you tried that @dstndstn. Well, I'm kind of in the same situation as you, I want to re-rationalize my deployment but I'm kind of stuck on the same batchspawner issue that's been addressed multiple times by different people, and then this thing here.
I'm still running off my fork at https://github.com/rcthomas/wrapspawner.git@vivify-server, with a mismatched JupyterHub (2.x on the remote side, 3.x on the hub), batchspawner 1.2.0.
Thanks for your reply! I will check out these leads -- much appreciated! -- and, if I manage to get it working, fingers crossed!, try to put in a PR that lists what my setup is in the README (or maybe some other file).
Hi! Did you manage to make it work? It is painful for me to still use an ancient hub version =(
I ran out of time to work on it without getting it working :(
Hm. I got it working eventually (slurm part). I had to use the current version of batchspawner from git. I still can not run systemdspawner for some reason and have no idea how to debug it, as I can not understand where to search for logs.
Package Version
--------------------------------------- -----------
...
batchspawner 1.2.0 as of https://github.com/jupyterhub/batchspawner/tree/d5f9a0bbaa92748267bb1dd2cc4d4a0436670482
ipykernel 6.22.0
ipympl 0.9.3
ipython 7.34.0
jupyter_client 8.1.0
jupyter_core 5.3.0
jupyter-events 0.6.3
jupyter-jsmol 2022.1.0
jupyter_server 2.5.0
jupyter-telemetry 0.1.0
jupyterhub 3.1.1
jupyterhub-systemdspawner 0.17.0
jupyterlab 3.5.0
jupyterlab_server 2.21.0
notebook 6.5.3
traitlets 5.9.0
wrapspawner 1.0.1 (pip release)
EDIT It turned out, that I just got an old systemd version (we are proudly running Ubuntu 18.04 because reasons) and rolling back to systemdspawner 0.15 did the trick. So for now everything is working.
Hi,
I'm trying to update my Jupyterhub installation again, and seemingly facing new incarnations of the same bugs I've encountered previously.
Long story short, I have a python3.9 setup with default pip versions of most things, specifically,
and I'm getting the common behavior that batchspawner (Slurm, in my case) works, but once wrapped in ProfilesSpawner, it fails; the user's jupyter server starts up, but never seems to contact the jupyterhub server.
I have read through and tried the things mentioned in #54, #41, #35, and my own ancient #24, but no dice.
I'll give some details on what I'm seeing below, but I guess my question is are there known versions of these packages that work together, and would it be possible to please document them in the README?
Brief Jhub logs:
This log message seems to point directly at the issue:
where
mn003
is the name of my front-end (jhub) server; it looks like the.server
attribute isn't getting set, which sounds deeply familiar. On the second line, it looks like batchspawner is reporting the URL of the server (cn002:58213
).Thanks for any suggestions!