stuck at forever connecting to kernel

[Fmajor]

Bug description

one of our user can successfully open the jupyterhub page and login
but when he try to execute python command in jupyter, no results return
I can see these log by docker logs -f

[I 2024-03-17 06:03:14.660 ServerApp] 101 GET /user/someone/api/kernels/844acba3-24e1-4570-aad4-71c55c512f1b/channels?session_id=7baeffed-9920-44ef-adef-4a2f20da9325 (someone@::ffff:10.53.0.7) 4.31ms
[I 2024-03-17 06:03:14.661 ServerApp] Connecting to kernel 844acba3-24e1-4570-aad4-71c55c512f1b.
[I 2024-03-17 06:03:14.901 ServerApp] Starting buffering for 844acba3-24e1-4570-aad4-71c55c512f1b:7baeffed-9920-44ef-adef-4a2f20da9325

[I 2024-03-17 06:03:15.105 ServerApp] 101 GET /user/someone/api/kernels/cad56779-2a16-4763-9443-d5271e094272/channels?session_id=8a2adf3f-a019-4ce0-8c82-8c72697b0682 (someone@::ffff:10.53.0.7) 4.31ms
[I 2024-03-17 06:03:15.105 ServerApp] Connecting to kernel cad56779-2a16-4763-9443-d5271e094272.
[I 2024-03-17 06:03:15.298 ServerApp] Starting buffering for cad56779-2a16-4763-9443-d5271e094272:8a2adf3f-a019-4ce0-8c82-8c72697b0682

[I 2024-03-17 06:03:15.724 ServerApp] 101 GET /user/someone/api/kernels/cad56779-2a16-4763-9443-d5271e094272/channels?session_id=2091440b-29fd-4fe3-b172-60485222921d (someone@::ffff:10.53.0.7) 3.70ms
[I 2024-03-17 06:03:15.725 ServerApp] Connecting to kernel cad56779-2a16-4763-9443-d5271e094272.
[I 2024-03-17 06:03:15.927 ServerApp] Starting buffering for cad56779-2a16-4763-9443-d5271e094272:2091440b-29fd-4fe3-b172-60485222921d

[I 2024-03-17 06:03:16.156 ServerApp] 101 GET /user/someone/api/kernels/844acba3-24e1-4570-aad4-71c55c512f1b/channels?session_id=29dd9f2f-ea47-4d80-b5bb-13cd22d31386 (someone@::ffff:10.53.0.7) 4.39ms
[I 2024-03-17 06:03:16.156 ServerApp] Connecting to kernel 844acba3-24e1-4570-aad4-71c55c512f1b.
[I 2024-03-17 06:03:16.587 ServerApp] Starting buffering for 844acba3-24e1-4570-aad4-71c55c512f1b:29dd9f2f-ea47-4d80-b5bb-13cd22d31386

[I 2024-03-17 06:03:16.772 ServerApp] 101 GET /user/someone/api/kernels/844acba3-24e1-4570-aad4-71c55c512f1b/channels?session_id=7baeffed-9920-44ef-adef-4a2f20da9325 (someone@::ffff:10.53.0.7) 3.98ms
[I 2024-03-17 06:03:16.772 ServerApp] Connecting to kernel 844acba3-24e1-4570-aad4-71c55c512f1b.
[I 2024-03-17 06:03:16.980 ServerApp] Starting buffering for 844acba3-24e1-4570-aad4-71c55c512f1b:7baeffed-9920-44ef-adef-4a2f20da9325

[I 2024-03-17 06:03:17.190 ServerApp] 101 GET /user/someone/api/kernels/cad56779-2a16-4763-9443-d5271e094272/channels?session_id=8a2adf3f-a019-4ce0-8c82-8c72697b0682 (someone@::ffff:10.53.0.7) 3.80ms
[I 2024-03-17 06:03:17.191 ServerApp] Connecting to kernel cad56779-2a16-4763-9443-d5271e094272.
[I 2024-03-17 06:03:17.374 ServerApp] Starting buffering for cad56779-2a16-4763-9443-d5271e094272:8a2adf3f-a019-4ce0-8c82-8c72697b0682

[I 2024-03-17 06:03:17.678 ServerApp] 101 GET /user/someone/api/kernels/cad56779-2a16-4763-9443-d5271e094272/channels?session_id=2091440b-29fd-4fe3-b172-60485222921d (someone@::ffff:10.53.0.7) 6.78ms
[I 2024-03-17 06:03:17.679 ServerApp] Connecting to kernel cad56779-2a16-4763-9443-d5271e094272.
[I 2024-03-17 06:03:17.862 ServerApp] Starting buffering for cad56779-2a16-4763-9443-d5271e094272:2091440b-29fd-4fe3-b172-60485222921d

[I 2024-03-17 06:03:18.068 ServerApp] 101 GET /user/someone/api/kernels/844acba3-24e1-4570-aad4-71c55c512f1b/channels?session_id=29dd9f2f-ea47-4d80-b5bb-13cd22d31386 (someone@::ffff:10.53.0.7) 7.19ms
[I 2024-03-17 06:03:18.069 ServerApp] Connecting to kernel 844acba3-24e1-4570-aad4-71c55c512f1b.
[I 2024-03-17 06:03:18.247 ServerApp] Starting buffering for 844acba3-24e1-4570-aad4-71c55c512f1b:29dd9f2f-ea47-4d80-b5bb-13cd22d31386

Notice that we have several different sessions:kernel pair and we have a forever loop try to connet each of them, but why?

How to reproduce

• I don't known, only one of our user get this error, other people use jupyterhub without any problem
• for the normal user, I only see one 101 GET, Connecting to kernel, Starting buffering sequence and then it works
• but for that special user, we get this forever loop
• if i start a single jupyterlab using jupyter lab (not use jupyterhub), that user can execute code without problem

Expected behaviour

• the use can connect to the kernel and execute codes

Actual behaviour

• get forever loop to connect to kernel

Your personal set up

linux kernel: 5.10.136
docker: 24.0.7
docker image: jupyterhub/jupyterhub:4.0.2

How can I further debug this problem?

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[bensdm]

same issue, any update or workaround?

[Fmajor]

same issue, any update or workaround?

no, just use jupyter notebook instead of jupyterhub