Do you have everything *else* updated? And what kind of web service are you running?
There's a lot of third party freeware and commercial tools that was not written with any kind of resource management in mind, and which may require a simple web server restart on a regular baris to free memory. (MusicBrainz: I remember porting MusicBrainz.....)
Yes, all the packages are up to date. General web services -- static HTML, and the rest is mainly wordpress.
You may be right about the restart, but I would like to know WHAT is crashing my web server regardless. We are not running any shiftily coded sites or apps on this server that I'm aware of (obviously something is shifty!). Is anyone aware of any other methods for drilling into the problem?
Look in /var/log/http/*.
Yes, these are the web server logs I am referring to having checked.
Do you have a search engine scanning your web server?
Hmm, no, nothing systematic. The usual crawlers out there but nothing we are doing. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 12/28/2010 01:41 PM, james wrote:
Do you have everything *else* updated? And what kind of web service are you running?
There's a lot of third party freeware and commercial tools that was not written with any kind of resource management in mind, and which may require a simple web server restart on a regular baris to free memory. (MusicBrainz: I remember porting MusicBrainz.....)
Yes, all the packages are up to date. General web services -- static HTML, and the rest is mainly wordpress.
You may be right about the restart, but I would like to know WHAT is crashing my web server regardless. We are not running any shiftily coded sites or apps on this server that I'm aware of (obviously something is shifty!). Is anyone aware of any other methods for drilling into the problem?
Look in /var/log/http/*.
Yes, these are the web server logs I am referring to having checked.
Do you have a search engine scanning your web server?
Hmm, no, nothing systematic. The usual crawlers out there but nothing we are doing. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I think the answer will come from analyzing your log files and possibly running something under cron (or in a shell script that wakes up periodically) to gather memory/resource utilization. Even look at a web log analyzer, like analog and see if there is a correlation between web server hits and resource usage. You could also try upgrading your web server/plugins or checking bugzilla for related bugs.
Nataraj
On 12/28/2010 5:18 PM, Nataraj wrote:
On 12/28/2010 01:41 PM, james wrote:
Do you have everything *else* updated? And what kind of web service are you running?
There's a lot of third party freeware and commercial tools that was not written with any kind of resource management in mind, and which may require a simple web server restart on a regular baris to free memory. (MusicBrainz: I remember porting MusicBrainz.....)
Yes, all the packages are up to date. General web services -- static HTML, and the rest is mainly wordpress.
You may be right about the restart, but I would like to know WHAT is crashing my web server regardless. We are not running any shiftily coded sites or apps on this server that I'm aware of (obviously something is shifty!). Is anyone aware of any other methods for drilling into the problem?
Look in /var/log/http/*.
Yes, these are the web server logs I am referring to having checked.
Do you have a search engine scanning your web server?
Hmm, no, nothing systematic. The usual crawlers out there but nothing we are doing. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I think the answer will come from analyzing your log files and possibly running something under cron (or in a shell script that wakes up periodically) to gather memory/resource utilization. Even look at a web log analyzer, like analog and see if there is a correlation between web server hits and resource usage. You could also try upgrading your web server/plugins or checking bugzilla for related bugs.
Nataraj
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
What's your http.conf? There's an setting where you can limit the amount of time a process/thread stays alive..you can limit ram usage by lowering that value.
On 12/28/2010 01:41 PM, james wrote:
You may be right about the restart, but I would like to know WHAT is crashing my web server regardless. We are not running any shiftily coded sites or apps on this server that I'm aware of (obviously something is shifty!). Is anyone aware of any other methods for drilling into the problem?
You may be dealing with a request that crashes before any data makes it into the logs.
Here's a trick I have used (posted Feb 10, 2008 by "Phantom" in alt.apache.configuration):
ls -l `ps -C httpd h | sed -r "s/^\s*([0-9]+) .+$//proc/\1/cwd/"`
which prints out the directory that each Apache worker thread is accessing. If you can narrow it down to the pid, you can use lsof to identify the particular file being being processed. Please keep us posted!
On 29/12/10 17:06, cpolish@surewest.net wrote:
On 12/28/2010 01:41 PM, james wrote:
You may be right about the restart, but I would like to know WHAT is crashing my web server regardless. We are not running any shiftily coded sites or apps on this server that I'm aware of (obviously something is shifty!). Is anyone aware of any other methods for drilling into the problem?
You may be dealing with a request that crashes before any data makes it into the logs.
Here's a trick I have used (posted Feb 10, 2008 by "Phantom" in alt.apache.configuration):
ls -l `ps -C httpd h | sed -r "s/^\s*([0-9]+) .+$//proc/\1/cwd/"`
which prints out the directory that each Apache worker thread is accessing. If you can narrow it down to the pid, you can use lsof to identify the particular file being being processed. Please keep us posted!
If you can track down the pid, you can easily check which file descriptors being in used and which files or sockets they relate to by checking the /prod/$PID/fd directory.
kind regards,
David Sommerseth
-
cpolish＠surewest.net -
David Sommerseth -
james -
Nataraj -
William Warren