From 9b44eec7f79a0a521a75feb667c79e1851022929 Mon Sep 17 00:00:00 2001 From: mahamtariq58 Date: Wed, 12 Oct 2022 02:53:43 +0500 Subject: [PATCH] Update docs/source/admin/log-messages.md Co-authored-by: Georgiana --- docs/source/admin/log-messages.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/source/admin/log-messages.md b/docs/source/admin/log-messages.md index 3288dea0..47cf20a8 100644 --- a/docs/source/admin/log-messages.md +++ b/docs/source/admin/log-messages.md @@ -18,7 +18,9 @@ Your log might display lines that seem cryptic 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 -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 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. 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 process then explicitly returns a failure response, so the client knows