On 2024-08-09 09:03, Matus UHLAR - fantomas wrote:
FTR, I sent the info privately, but we can continue
discussing/solving it here.
maybeMakeSpaceAvailable: request buffer full: client_request_buffer_max_size=524288
ReadNow: ... size 0, retval 0, errno 0
terminateAll: 1/1 after ERR_CLIENT_GONE/WITH_CLIENT
On 09.08.24 09:51, Alex Rousskov wrote:
AFAICT, you are suffering from a Squid bug that goes back to 2015
commit 4d1376d7 (that was fixing Squid bug 4206) or even earlier code.
Red flags were raised back in 2015, but nobody followed through. We
need to refactor Server::maybeMakeSpaceAvailable()-related code to fix
this bug.
FWIW, we did similar work for Squid-to-peer communication in commit
cc8b26f9 and commit 50c5af88. Similar principles should apply to
client-Squid communication. Unfortunately, I do not have enough free
time to volunteer to fix this client-Squid bug now.
At the expense of using more memory for some upload cases, you may be
able to work around the bug in some (but not all!) cases by making
client_request_buffer_max_size sufficiently large. For example,
setting client_request_buffer_max_size to 16 megabytes may allow you
to pass the test case you have privately shared.
Thanks for info.
I have tried rising client_request_buffer_max_size to 11MB and file uploaded
correctly, so your guess is apparently correct.
I will try logging PUT/POST sizes just to see what should be the correct
value for now.
Further I'll analyze so I'll be able to guess how will it affect squid
cache.
--
Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Depression is merely anger without enthusiasm.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
