On Tue, Mar 30, 2021 at 11:52 AM Daniel Ferradal <dferra...@apache.org> 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 testbed I could reproduce the issue regardless of whether mod_security was being used. > If I were you I would first check the list of modules and with > mod_status the state of workers before issuing a graceful. > I had a look at this on my testbed. I tried to send about 50 requests per second with the slowhttptest utility, which caused all worker processes to be used up. When I issued a graceful reload, I could see some of those processes enter the "G" state. After that, I was unable to refresh the server stats, because all connections were used. Eventually, however, the system came back to life again. I don't know if that's because slowhttptest was backing off, or if things were just working as intended. On my production system, that didn't happen: it sat for over 2 hours in an unresponsive state after the graceful restart. Perhaps that's because it was receiving constant connection attempts, and these were occupying all available connections and preventing the reload from finishing? I'm at a loss regarding what else might have been misbehaving to hold onto the connections. Everything was working fine up until the reload. Thanks!
