When the relevant seconds pass as defined in the jupyterhubconfig.py , the cull-idle service should stop the idle server of each user. So that when going to navigate the page, no terminals should be able to be started, no notebooks etc, unless the user explicitly presses Start server . (am I wrong?)_
Actual behaviour
When the relevant seconds pass, all that happens is this output in the log:
200 GET /hub/api/users (cull-idle@127.0.0.1) 10.47ms
And with this the server continues running normally, meaning I can start a terminal, make files etc.
Your personal set up
Version:
JupyterHub version 1.1.0
oauthenticator.generic.GenericOAuthenticator-0.11.0
Using Spawner: jupyterhub.spawner.LocalProcessSpawner-1.1.0
Using Proxy: jupyterhub.proxy.ConfigurableHTTPProxy-1.1.0
Bug description
I have followed exactly the steps here .
Expected behaviour
When the relevant seconds pass as defined in the jupyterhubconfig.py , the cull-idle service should stop the idle server of each user. So that when going to navigate the page, no terminals should be able to be started, no notebooks etc, unless the user explicitly presses Start server . (am I wrong?)_
Actual behaviour
When the relevant seconds pass, all that happens is this output in the log:
200 GET /hub/api/users (cull-idle@127.0.0.1) 10.47ms
And with this the server continues running normally, meaning I can start a terminal, make files etc.Your personal set up
Running as root .