hazza/jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/jupyterhub.git synced 2025-10-17 23:13:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #4086 from ArafatAbdussalam/branch2

Browse Source 
Updated log messages
This commit is contained in:
Min RK
2022-10-17 13:45:16 +02:00
committed by GitHub
parent 147f029bf6 0a9d2b7f76
commit 8785ecd810
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -8,19 +8,20 @@ log messages, what they mean and what are the most common causes that generated
### Example ### Example
Your log might display lines that seem cryptic Your logs might be littered with lines that look scary
``` ```
[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 ### Cause
The possible reason may be that the user's server has stopped running This likely means that the user's server has stopped running but they
but they still have a browser tab open. For example, you might have 3 tabs open and you shut still have a browser tab open. For example, you might have 3 tabs open and you shut
the server down via one. the server down via one.
The other possible reason could be that you closed your laptop and the server was culled for inactivity, then reopened the laptop! Another possible reason could be that you closed your laptop and the server was culled for inactivity, then reopened 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. 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