Summary: With the below settings apache crashed on me. The error log told me it reached MaxRequestWorkers. It suggested increasing the size. To remedy the situation I increased MaxRequestWorkers to 10,0000. Then
I was fine. Based on the documentation it says that you are supposed to divide the MaxRequestWorkers by ThreadsPerChild to get to ServerLimit. I don’t recall how many running processes I had at the time of the crash. I was in a panic mode. I have not had
apache crash on me in so long I was not really prepared. Now I know I should have got a listing of the number of processes in use by apache. I should have also taken a snapshot of the memory usage by each process. Questions:
Httpd.conf: <IfModule mpm_worker_module> ServerLimit 250 StartServers 10 MinSpareThreads 75 MaxSpareThreads 250 ThreadLimit 64 ThreadsPerChild 32 MaxRequestWorkers 8000 MaxConnectionsPerChild 500 </IfModule> Apache info: Server version: Apache/2.4.6 (CentOS) Server built: Jun 27 2018 13:48:59 Server's Module Magic Number: 20120211:24 Server loaded: APR 1.4.8, APR-UTIL 1.5.2 Compiled using: APR 1.4.8, APR-UTIL 1.5.2 Architecture: 64-bit Server MPM: worker threaded: yes (fixed thread count) forked: yes (variable process count) Error log: [mpm_worker:error] [pid 31849:tid 140027731249280] AH00287: server is within MinSpareThreads of MaxRequestWorkers, consider raising the MaxRequestWorkers setting [Wed Aug 22 03:40:40.893477 2018] [mpm_worker:error] [pid 31849:tid 140027731249280] AH00286: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting [Wed Aug 22 03:41:16.264059 2018] [mpm_worker:notice] [pid 31849:tid 140027731249280] AH00296: caught SIGWINCH, shutting down gracefully Thanks, Lance |