Re: [users@httpd] Apache 2.4.37 graceful restart causes error “scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.”

2021-03-30 Thread A.J. Gatlin
On Tue, Mar 30, 2021 at 4:58 PM Jim Albert wrote: > > How about a graceful restart right after a fresh full restart. Does that > immediate graceful restart present the same issue or does the problem > require some period of requests before a graceful restart will present the > problem. Some

Re: [users@httpd] Apache 2.4.37 graceful restart causes error “scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.”

2021-03-30 Thread A.J. Gatlin
On Tue, Mar 30, 2021 at 11:52 AM Daniel Ferradal wrote: > I may be adding noise, but it is worth checking if you are using third > party modules and which ones. > Thanks for the tip. I'm not using any third party modules. I had a hunch that maybe mod_security was causing issues, but on my

Re: [users@httpd] Apache 2.4.37 graceful restart causes error “scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.”

2021-03-30 Thread A.J. Gatlin
On Tue, Mar 30, 2021 at 2:49 AM Eric Covener wrote: > What are your current MPM settings and how busy is your server during > rotation? If ServerLimit is above MaxClients/ThreadsPerChild the extra > scoreboard space is what allows the old generation of processes to > gracefully exit while a new

Re: [users@httpd] Apache 2.4.37 graceful restart causes error “scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.”

2021-03-30 Thread A.J. Gatlin
On Tue, Mar 30, 2021 at 2:42 AM Jim Albert 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

Re: [users@httpd] Apache 2.4.37 graceful restart causes error “scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.”

2021-03-29 Thread A.J. Gatlin
On Tue, Mar 30, 2021 at 2:11 AM Paul A wrote: > > I'm not sure where "rich" becomes "poor"? Been using both for a couple > of decades or more. If it ain't broken, don't fix it. Try "Apache's > rotatelogs" and if you're really unhappy that it needs tweaking, > probably someone here can help you.

Re: [users@httpd] Apache 2.4.37 graceful restart causes error “scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.”

2021-03-29 Thread A.J. Gatlin
On Mon, Mar 29, 2021 at 9:52 PM angel Hall-Coulston wrote: > Try this: > https://httpd.apache.org/docs/2.4/programs/rotatelogs.html > I appreciate the tip, and I believe the use of Apache's own log rotation would allow me to sidestep the problem. However, Apache's rotatelogs isn't quite as

[users@httpd] Apache 2.4.37 graceful restart causes error “scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit.”

2021-03-29 Thread A.J. Gatlin
Hi there, I'm running some PHP-based sites on CentOS 8, which uses version 2.4.37 of Apache. Apache is set to use MPM Event mode, which is also the default. Once per day during a quiet period, logrotate rotates the Apache logs by doing a graceful restart (reload) as part of a postrotate command: