Broken Pipe After Potman Concurrency Test Ended

Using Django Mystery Errors
1

So It was just a simple 2min test with 100 virtual users and 10 request per second appx with a total of 1207 request sent throught the test.

Now When the test ended, up until now all the requests were served there were no errors.
But as soon as it ended, lots of broken pipe error showed up, still the server was not halted and served the very next request i sent manually with normal response time.

All the API endpoint is doing is returning a array of items(products) in my ecommerce website.

.
.
.

[06/Sep/2023 20:45:48] "GET /api/items/ HTTP/1.1" 200 549315
[06/Sep/2023 20:45:48] "GET /api/items/ HTTP/1.1" 200 549315
[06/Sep/2023 20:45:48] "GET /api/items/ HTTP/1.1" 200 549315
[06/Sep/2023 20:45:48] "GET /api/items/8/ HTTP/1.1" 200 155
[06/Sep/2023 20:45:48] "GET /api/items/8/ HTTP/1.1" 200 155
[06/Sep/2023 20:45:48] "GET /api/items/8/ HTTP/1.1" 200 155
[06/Sep/2023 20:45:48,988] - Broken pipe from ('127.0.0.1', 56385)
[06/Sep/2023 20:45:49,286] - Broken pipe from ('127.0.0.1', 56454)
[06/Sep/2023 20:45:49,300] - Broken pipe from ('127.0.0.1', 56451)
[06/Sep/2023 20:45:49,573] - Broken pipe from ('127.0.0.1', 56426)
[06/Sep/2023 20:45:49,585] - Broken pipe from ('127.0.0.1', 56411)
[06/Sep/2023 20:45:49,753] - Broken pipe from ('127.0.0.1', 56406)
.
.
.
(so on)
.
.
[06/Sep/2023 20:46:00,763] - Broken pipe from ('127.0.0.1', 56404)
[06/Sep/2023 20:46:00,763] - Broken pipe from ('127.0.0.1', 56389)
[06/Sep/2023 20:46:40] "GET /api/items/8/ HTTP/1.1" 200 155

Idk what’s wrong? what happend

No errors were listed in Potmam, according to it there was 0% error rate

2

I also had this error in testing, no idea what caused it, I was testing it from a different phone, sending requests to the server and monitoring them, I kept seeing that same error of broken pipe, tried the same with the exact same phone later on but didn’t see the error, no idea what’s going on

3

This is a information logged by the django.server logger, it’s with the info level. This can be disabled by:

  • Using a higher logging level for this logger ( I believe that by doing this you won’t see any logs for 200 responses )
  • Or by setting a filter to this logger.

But on my opinion this is not something that you should worry about anyway.