-
Notifications
You must be signed in to change notification settings - Fork 308
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
Service jupyter-xyz not found #333
Comments
I am having the same behavior here. Hub can launch a service, you can exec into the hub and use curl to verify the service is running at port 8888, but sometimes the hub can't detect that the service is running and generates a 500 error or a 'service unavailable' page. Refreshing will work around the second most times, the first requires re-attempting 'start my server' from the 'home' tab and isn't particularly reliable. It seems to work better if they first log all the way out then log back in. Running jupyterhub_config.py:
|
Hi! I’m going through and cleaning up old/stale issues on this repo. Sorry for not responding in a reasonable amount of time! I believe the issue here is a failure to wait for the previous removal to complete, as swarm, unlike regular docker, appears to leave services in a gettable state while waiting for delete to complete. The fix should be to add a wait to |
Hi guys,
I have problem with my JupyterHub+DockerSpawner implementation. In my system user can choose a image to sprawn (SwarmSpawner.image_whitelist) and change it by stoping existing server and starting another one. Many times during this process (and also during pure start of the spawning process) service response by "Service jupyter-xyz not found".
After couple of attempts (sometimes only one is needed) container is spawned properly and everything works well. In logs I see that the existing service is removed and new one is calling but spawner still call previous one.
It is possible to manage this issue or prevent it? Any ideas to remove this quite annoying issue?
The text was updated successfully, but these errors were encountered: