-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Closed
Labels
bugstatus:resolved-lockedClosed issues are locked after 30 days inactivity. Please open a new issue for related discussion.Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.tag:Server Change
Milestone
Description
When I start JupyterLab in my container I've just started seeing Adapting to protocol v5.1
messages cropping up in the server logs with corresponding websocket connection lost errors in the front-end:
Copy/paste this URL into your browser when you connect for the first time,
to login with a token:
http://204de7712a62:8888/?token=56da9ee4440a1503a020f58b6d8e9a5ff083d855ae1ce3c5&token=56da9ee4440a1503a020f58b6d8e9a5ff083d855ae1ce3c5
[I 14:39:11.033 LabApp] 302 GET /lab (10.200.18.81) 2.00ms
[I 14:39:20.994 LabApp] 302 POST /login?next=%2Flab (10.200.18.81) 2.00ms
[W 14:39:24.600 LabApp] 404 GET /iframes (10.200.18.81) 11.99ms referer=http://dc1thwn01:8888/lab
[I 14:39:26.324 LabApp] Build is up to date
[I 14:40:27.131 LabApp] Writing notebook-signing key to C:\Users\ContainerAdministrator\AppData\Roaming\jupyter\notebook_secret
[W 14:40:27.143 LabApp] Notebook jupyter/Pricing/ProfilePricing.ipynb is not trusted
[I 14:40:28.583 LabApp] Kernel started: 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:40:29.923 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:40:29.955 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:40:34.515 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:40:44.517 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:40:49.894 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:40:49.917 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:40:54.524 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:03.120 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:04.542 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:14.515 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:17.111 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:17.140 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:17.170 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:17.197 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:24.510 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:24.531 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:34.482 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:34.545 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:37.076 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:37.110 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:37.142 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:37.172 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:37.200 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:44.467 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:44.514 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:44.547 LabApp] Adapting to protocol v5.1 for kernel 4cf7c0bd-8a50-447a-9a86-51996812bb27
[I 14:41:47.178 LabApp] Interrupted...
[I 14:41:47.179 LabApp] Shutting down 1 kernel
[I 14:41:47.985 LabApp] Kernel shutdown: 4cf7c0bd-8a50-447a-9a86-51996812bb27
After a while I see a Server Connection Error
and JupyterLab becomes entirely unresponsive:
I suspect some networking problem on my end however I'm at a loss as to how to debug it so am soliciting any and all advice!
The problem is the same in incongnito mode or not in either FireFox (Quantum) or Chrome.
djsd123
Metadata
Metadata
Assignees
Labels
bugstatus:resolved-lockedClosed issues are locked after 30 days inactivity. Please open a new issue for related discussion.Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.tag:Server Change