kurtcostello
asked on
Web server issue
We are having issues with our redhat webeserver where every once in a while it you can't access the site. When this happens I look at the amount of HTTPD processes and it is at 241. I also look at CPU and Memory ussage and it does not seem to be affected. If i restart apache the process will go down and the site will come back up. I'm thinking it may be somekind of a loop. Can someone give me some advice of how to troubleshoot this issue?
check for free disk space
check for open file handles (ulimit must say unlimited or a high limit)
Paste the output of apache access (/var/log/httpd/access_log ) & error (/var/log/httpd/error_log) logs
check for open file handles (ulimit must say unlimited or a high limit)
Paste the output of apache access (/var/log/httpd/access_log
ASKER
I can't seem to figure our how to turn extendedstatus on. I change the config so it reads:
<Location /server-status>
SetHandler server-status
ExtendedStatus On
Order deny,allow
Deny from all
Allow from *.*.*.*
</Location>
But when I try to restart apache it says:
Starting httpd: Syntax error on line 914 of /etc/httpd/conf/httpd.conf :
ExtendedStatus not allowed here
am I missing something?
<Location /server-status>
SetHandler server-status
ExtendedStatus On
Order deny,allow
Deny from all
Allow from *.*.*.*
</Location>
But when I try to restart apache it says:
Starting httpd: Syntax error on line 914 of /etc/httpd/conf/httpd.conf
ExtendedStatus not allowed here
am I missing something?
ASKER
ok I got it to work actually. This won't use up space on the drive will it?
No not at all, it allows you to query the details of the server.
lynx -dump http://localhost/server-status - use this command to show the information about each process, including what files are being served at the time. If you fine one script or page constantly holding open processes you can then look at dealing with this page. How you do this is your choice as the admin.
lynx -dump http://localhost/server-status - use this command to show the information about each process, including what files are being served at the time. If you fine one script or page constantly holding open processes you can then look at dealing with this page. How you do this is your choice as the admin.
btw, the Allow from statement should be Allow from 127.0.0.1
The server-status provides ALOT of information about your server and shouldn't be open to everyone.
The server-status provides ALOT of information about your server and shouldn't be open to everyone.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Once you know what they were trying to serve you can then sort out that particular page.