ispconfig 3.2.11 debian 12 I have no issues for ages, then last 2 weeks im having a run of them.. having this today Code: scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit. Internet google search states Code: MaxRequestsWorkers = ServerLimit x ThreadsPerChild do i add this to mpm_event.conf or mpm_prefork.conf ServerLimit does not exist in either, do i add this to both files?
The webserver has 16GB allocated RAM I edited /etc/apache2/mods-available/mpm_event.conf and set the following Code: StartServers 3 ServerLimit 3 MinSpareThreads 250 MaxSpareThreads 200 ThreadLimit 64 ThreadsPerChild 50 MaxRequestWorkers 500 MaxConnectionPerChild 1000 Apache2 starts for a few seconds then stops rendering pages. I then Code: root@apache:~# systemctl stop apache2 root@apache:~# a2dismod mpm_event root@apache:~# a2enmod mpm_prefork root@apache:~# apache2ctl configtest Syntax OK root@apache:~# service apache2 restart but seems really slow compared to before.
You enabled a slower and older MPM model which is not used anymore on recent installations, that's why your server is slower now. The old mpm_prefork you switched to now also does not support modern modes like http/2, so I highly recommend you undo these changes.
Hey Till, When i do the server grinds to a halt. pages refuse to render. page not found after time. I reverted the settings back to original, earlier and same happened. Resources are at 50% so only 8GB ram used (proxmox)
one difference till, this server states Code: root@web01:~# apache2ctl configtest AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message Syntax OK and other server does not. which config file is it set.. i have looked in /etc/apache2/apache2.conf - not there
This does not matter for the problem. Your issue is basically that your system currently receives more requests than it can handle or that it reached the limits. Have you checked how high the system load is? Maybe its a DOS attack, so increasing server limits in Apache might not be the solution as it would reach its limits anyway.
with the base settings inside /etc/apaceh2/mods-enabled/mpm_events.conf do they scale up if i allocate more ram, or will i have to play with the numbers based on requests = serverlimit x threadsperchild
You must set the numbers to match what your server can handle. The limits exist to prevent your server from being overloaded.
