I recently upgraded a web server from Debian 8 to Debian 11, no errors concerning Apache were noted. Before the upgrade the website performed smoothly. The only configuration change made was to switch to php7.4 from php5.
Apache is set to use mpm-prefork with a MaxRequestWorkers, initially set to 150.
After the upgrade the max connections limit has been reached multiple times. The first few times I upped the MaxRequestWorkers to 200, then 256. I then analyzed the server hardware, not having set it up, and set the ServerLimit to 400 with a MaxRequestWorkers at 300. It is still hitting this limit. When it does I have to restart the Apache service, systemctl restart apache2. If I do not it will continue to be unresponsive until it is restarted.
I have pulled and analyzed the logs using GoAccess and have found no evidence of DOS attacks or bad clients. It feels as if the upgrade caused an issue somewhere. Looking for possible ideas as to why this may be.
Edit: Found a second possibly related issue where files that were accessible to download no longer complete the download. The download gets "stuck" after a percentage, 2%-40% in tests, of the file is downloaded. This leaves processes in a limbo state which is most likely causing the original issue noted. The files do test as good, via SHASUM comparison with the originals on other servers, and text files can be read directly on the web server via console.