hazza/jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/jupyterhub.git synced 2025-10-18 15:33:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

[pre-commit.ci] auto fixes from pre-commit.com hooks

Browse Source 
for more information, see https://pre-commit.ci
This commit is contained in:
pre-commit-ci[bot]
2022-10-10 22:41:58 +00:00
parent b98e981e6a
commit a2852b1b2b
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/source/admin/log-messages.md
View File

@@ -9,15 +9,16 @@ log messages, and what necessary actions to take.
### Example ### Example
Your log might display lines that seem cryptic Your log might display lines that seem cryptic
``` ```
[W 2022-03-10 17:25:19.774 JupyterHub base:1349] Failing suspected API request to not-running server: /hub/user/<user-name>/api/metrics/v1 [W 2022-03-10 17:25:19.774 JupyterHub base:1349] Failing suspected API request to not-running server: /hub/user/<user-name>/api/metrics/v1
``` ```
### Most likely cause ### Most likely cause
The possible reason may be that the user's server has stopped running The possible reason may be that the user's server has stopped running
but they still have a browser tab open. For example, you might have 3 tabs open and you shut but they still have a browser tab open. For example, you might have 3 tabs open and you shut
the server down via one. The other possible reason could be that you closed your laptop and the server was culled for inactivity, then reopen the laptop! However, the client-side code (JupyterLab, Classic Notebook, etc) doesn't interpret the shut-down server and continues to make some API requests. the server down via one. The other possible reason could be that you closed your laptop and the server was culled for inactivity, then reopen the laptop! However, the client-side code (JupyterLab, Classic Notebook, etc) doesn't interpret the shut-down server and continues to make some API requests.
JupyterHub's architecture means that the proxy routes all requests that JupyterHub's architecture means that the proxy routes all requests that
don't go to a running user server to the hub process itself. The hub don't go to a running user server to the hub process itself. The hub
process then explicitly returns a failure response, so the client knows process then explicitly returns a failure response, so the client knows