Jupyterhub - single user notebook servers shuts down
-
I would like to use the Jupyter Scheduler extension.
https://jupyter-scheduler.readthedocs.io/en/latest/users/index.html#installation
The installation is working fine.
I then set up a job that runs once a day. This also works without any problems.However, I have noticed one issue. If I don't use the app for a few days, my notebook server is shut down and thus the job will not run again until I start the notebook server.
Is there a way to prevent the Notebook Server from shutting down in the Jupyterhub settings?
-
@balticpenguin are you using Cloudron to deploy JupyterHub ? The Cloudron package has no code to shutdown notebooks
-
@balticpenguin OK, I was a bit wrong. When the app gets updated to use the latest notebook, the existing notebooks are shutdown so that they can be started with the newer image. I suspect that maybe the app is getting updated in the middle and thus the notebook is getting shutdown.
Is your job able to start up the notebook server automatically?
-
@girish: I have checked if the shutdown is related to an update and thus a restart of Jupyterhub. This is not the case.
There must be something running in the background of Jupyterhub that stops the notebook server/Docker container as soon as there is a certain amount of inactivity. -
Is some external service like culler enabled ? https://github.com/jupyterhub/jupyterhub-idle-culler . The default package doesn't enable all that, so I am just asking if you have enabled it in your own.
-
No manual changes have been made so far.
I could not find jupyterhub-idle-culler in the list of 'pip list' in the terminal of the Jupyterhub container. -
@balticpenguin think we have to check the logs of jupyterhub. Do you see any logs that it is removing a container ? Cloudron itself doesn't remove any containers.
-
