httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marten Lehmann <lehm...@cnm.de>
Subject [users@httpd] Hugh httpd-process
Date Fri, 25 Jan 2008 14:01:17 GMT
Hello,

using "top", I noticed this output:

top - 08:48:40 up 24 days, 17:21,  1 user,  load average: 173.78, 113.81,
52.58
Tasks: 449 total,  47 running, 397 sleeping,   0 stopped,   5 zombie
Cpu(s):  5.2% us, 56.6% sy,  0.4% ni,  0.0% id, 37.5% wa,  0.0% hi,  0.2% si
Mem:   2056328k total,  2038468k used,    17860k free,     3216k buffers
Swap:  2040244k total,  2040244k used,        0k free,    29344k cached

   PID USER      PR  NI %CPU    TIME+  %MEM  VIRT  RES  SHR S COMMAND
    68 root      16   0   49  16:59.70  0.0     0    0    0 R kswapd0
17689 nobody    16   0   12   1:00.98 65.2 3665m 1.3g 1832 D httpd
21497 u11754    16   0    4   0:00.16  0.4 63240 8072 4604 D php
21064 u12732    16   0    3   0:00.30  0.5  109m 9628 4652 D php
18761 nobody    16   0    3   0:00.36  0.1 38808 2124 1632 S httpd
21068 u12072    18   0    3   0:00.31  0.8 72212  16m 4616 R php
21093 nobody    16   0    3   0:00.12  0.1 38612 1940 1444 S httpd

In our configuration, httpd runs as user nobody to deliver static 
content. We have SSL and non-SSL hosts (mostly). As soon as perl or php 
scripts are started, a cgiwrapper is being used, so the processes do 
have a different user id and another command name (php in this case).

So I'm really wondering, why there is a httpd process which uses 65% of 
the memory. As you can see in the load average line, the process is 
getting even greater. This occurs every now and then. And there are 
following effects of this:

- swapd is used to get more memory which slows down the system
- sometimes the httpd-process us killed automatically (or at least 
disappears at some point and the system goes back to usual load, or:
- httpd-process is consistently consuming more and more memory, even 
swapd can't help, the whole system crashes.

Within our cgiwrapper, we have memory limits, But since this all is 
happens within apache, we cannot set any limits.

We are currently using httpd-2.2.4. Hoe comes, that httpd processes can 
get that hugh?

Regards
Marten

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message