On Tue, Mar 30, 2021 at 2:42 AM Jim Albert <j...@netrition.com> wrote:
> > Have you checked your request logs at the time of restart for any > request activity associated with the restart? > Yes, I did have a look at this to see if there was anything out of the ordinary. However, I didn't see anything interesting -- no scans or attacks that would result in especially high numbers of connections. The reload happens during a relatively quiet overnight period. > Does https://yourserver.com/server-status present any clues, > particularly the processes section or will that also not respond? > Nothing would respond until I forcibly restarted the httpd process. I was getting the "scoreboard is full" error logged once per second to the error_log during this period. > Does a restart, graceful or full restart, outside of a logrotate present > the same issue? > A full restart always works fine -- no errors. It just takes some time and is disruptive. For the graceful restart, I was able to reproduce the issue on a test machine when I fed it simulated traffic from the tool slowhttptest. I'd issue the reload command, see the "scoreboard is full" in the logs, and then the system would be unresponsive as long as my simulated traffic was continuing. As soon as the simulated traffic ends, the system seems to recover. It would appear, though, that in production, the system never gets a chance to recover, because there are always incoming connection requests. At least that's my guess. > > Maybe give MaxConnectionsPerChild a setting. I believe the default is 0 > which indicates httpd children do not expire. Maybe try 2000 so httpd > children expire occasionally and restart new... just in case of some > memory issue you are facing. > > https://httpd.apache.org/docs/2.4/mod/mpm_common.html#maxconnectionsperchild I'll consider it. Thanks very much. > >
