I would look at /etc/security/limits.conf and /etc/security/limits.d and see if there is a special memory entry for the user httpd is running as. If there is
you could change it but this just moves the point of failure. Have you opened a ticket with Red Hat? They may be able to find a the fix from a newer version of Apache and backport it.
As to how Apache 2.4 handles reloads it gracefully stops the existing instances and spawns new ones I have not done an exhaustive test of your problem but I handle
about 200 virtual hosts on the central web server here at the University. I do reloads often and have not had the issue with Apache 2.4. Darryl Baker Sr. System Administrator Northwestern |
Information Technology www.it.northwestern.edu From: Michele Mase' [mailto:michele.mase@xxxxxxxxx]
I've tried with httpd.event, same result. Using a demo host with 260 vhosts, the httpd hangs after "only" 1000 reloads. The relationship seems to be the following: 10 virtualhosts = 100000 reloads 100 virtualhosts = 1000 reloads Tomorrow I 'll try to test httpd 2.4.x. Other better ideas? Regards On Wed, Jan 25, 2017 at 4:42 PM, Darryl Philip Baker <darryl.baker@xxxxxxxxxxxxxxxx> wrote:
|