You could temporarily increase your ThreadsPerChild, as 25 is extremely low and increases the chances of that bug occurring.
I'd have to find out what fix applies to this bug, and why your installation is still vulnerable. Perhaps your distro used backports. On Tue, 25 Oct 2022 at 20:02, Mike Dewhirst <mi...@dewhirst.com.au> wrote: > My Apache 2.4.52 is crashing with a bug apparently eliminated in 2.4.7. > > Server Version: Apache/2.4.52 (Ubuntu 2022.04) OpenSSL/3.0.2 > mod_wsgi/4.9.0 Python/3.10 > Server MPM: event > Server Built: 2022-06-14T12:30:21 > > DigitalOcean droplet 8GB memory, dedicated CPU. > > The log says ... > [Mon Oct 24 04:50:35.867241 2022] [mpm_event:error] [pid 904:tid > 140622640994176] AH03490: scoreboard is full, not at > MaxRequestWorkers.Increase ServerLimit. > > mpm-event.conf ... > # event MPM > # ServerLimit: Upper limit on configurable number of processes (default 16) > # StartServers: initial number of server processes to start (default 3) > # MinSpareThreads: minimum number of worker threads which are kept spare > (default 75) > # MaxSpareThreads: maximum number of worker threads which are kept spare > (default 250) > # ThreadLimit: upper limit on the configurable number of threads per > child process (default 64) > # ThreadsPerChild: constant number of worker threads in each server > process (default 25) > # MaxRequestWorkers: maximum number of worker threads > (ServerLimit*ThreadsPerChild) > # MaxConnectionsPerChild: maximum number of requests a server process > serves > <IfModule mpm_event_module> > ServerLimit 16 > StartServers 3 > MinSpareThreads 75 > MaxSpareThreads 250 > ThreadLimit 64 > ThreadsPerChild 25 > AsyncRequestWorkerFactor 2 > MaxRequestWorkers 400 > MaxConnectionsPerChild 0 > </IfModule> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
