Hey all. I recently swapped my apache 1.3 site (personal blog, albums,
etc) over to apache 2 (stable) and all seemed to go well. However
lately I've been having a lot of out of memory issues on the server.
Even when memory is still available
naked alan # free -m
total used free shared buffers cached
Mem: 505 475 29 0 33 219
-/+ buffers/cache: 222 282
Swap: 525 75 450
vmstat:
procs -----------memory---------- ---swap-- -----io---- --system--
----cpu----
r b swpd free buff cache si so bi bo in cs us sy
id wa
0 0 77020 50124 34212 206672 0 0 2 5 103 126 0 1
99 1
(sorry about the wrapping)
I'm still getting errors like this in my site's error log:
[Fri Mar 31 20:07:08 2006] [error] [client 209.123.8.19] (12)Cannot
allocate memory: couldn't create child process: 12: mt-tb.cgi
[Fri Mar 31 20:07:08 2006] [error] [client 209.123.8.19] (12)Cannot
allocate memory: couldn't spawn child
process: /var/www/arcterex.net/htdocs/mt/mt-tb.cgi[Fri Mar 31 20:07:09
2006] [error] [client 209.123.8.19] (12)Cannot allocate memory: couldn't
create child process: 12: mt-tb.cgi
This happens for most of the pages when I got to my movable site admin
pages (all cgi).
I'm using pretty much the stock apache2 config files on a 512mb athlon
xp2600 server. I've used "threads" "-threads" and "mpm-prefork" in my
USE flags, with pretty much the same results :( The server itself is a
standard samba/apache/mysql system which seemed to run mostly ok under
apache 1.3, so I'm really wondering what the heck is going on. When the
server reports the out of memory conditions I can sometimes hit the page
a couple of times and then it'll come up. Other times apache will run
with 100% cpu and slowly use up memory and swap until I have to (slowly)
login and kill it by hand.
Anyone seen anything like this or have an idea on how to fix?
TIA
Alan
--
Alan <[EMAIL PROTECTED]> - http://arcterex.net
--------------------------------------------------------------------
"Backups are for people who don't pray." -- big Mike
--
gentoo-user@gentoo.org mailing list
