Hello I got many /usr/local/apache/bin/httpd -k start -DSSL and the server load is going high up to 80 Any ideas how can i find what is giving so many /usr/local/apache/bin/httpd -k start -DSSL? I am using nginx plugin in front of Apache. When i stop apache the server load is 1. What is the latest version of Apache that easy apache installs? It seems that someone maybe use a denial of service exploit and i hope to get a new update soon so i can install it using easy apache. Thank you
Have you tried checking out your /server-status ? If you are running cPanel on your server, then you should already have a server-status built in in the left panel of your WHM. So when the server load goes high, just click it and check it out which site is actually consuming a lot of httpd processes. If you are not on the cPanel, then check it out if your server already has /server-status enabled (http://your-server-hostname.com/server-status) If not, then try enabling it in your httpd.conf file To enable server-status in httpd.conf try editing it pico -w /your/path/to/httpd.conf Code (markup): then CTRL+W and search for ExtendedStatus and make sure it states: ExtendedStatus On Code (markup): then again ctrl+w and search for server-status and make sure the lines there are NOT commented, so it looks something like this: <Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from all </Location> Code (markup): You can also change <Location /server-status> line to state something like <Location /server-status999> to avoid having someone else viewing your server-status if he types it in by accident, or just have an Allow from to point to only your IP address, so it denies everyone else (which is a great solution if you have a static IP address). After you have your server-status enabled, then just wait for the load problem to happen again, and when it does quickly open http://your-server-hostname.com/server-status to catch the url causing those problems. Note: Make sure to BACKUP your httpd.conf file prior to changing anything, so if you break it somehow you will have a working version saved to restore. Note2: After making those changes to httpd.conf make sure to restart your httpd/apache or server-status will not work.