Apache → configurable-http-proxy "Broken pipe"

[kaliko]

Thanks for your reply @manics

@manics

• Can you show us your JupyterHub config with secrets redacted

Here is the config I use on a Debian Buster (up to date) with jupyterhub 1.2.1 and CHP 4.2.2.

@manics

• Do you only see these issues when you have a lot of users simultaneously using JupyterHub?

No, I can see the “Broken pipe” issue even when there are only a couple of users.

@manics

• Have you looked at your CPU, memory and network usage around the time the errors occur?

I run users servers in dedicated slice with limited CPU/memory, I never noticed the user suffering from a lack of resources at the moment of the issue (I’ll control that again to be sure). Though when the error occurs the request did not hit the server yet, if I understand correctly, the request is still between the http server and CHP.

@manics

What sort of compute loads are your users putting on your server?

The platform is used for python training (for beginners), then exercises are plain python code but in the hand of neophyte programmers (we often have cpu intensive endless loops and some OOM kill however seldom). Resources guardrail (within systemd cgroups) works fine and does not seem related/correlated to the “Broken pipe” issue though.

@manics

• Can you show us your logs for JupyterHub (and CHP if it’s running separately) at the time the failure occurs? It might be helpful to turn on debug logging too.

I’ll try to reproduce with debug on.