I have been fighting a problem on a box for week or more and can find a resolution. Fedora / WHM .

The memory on this box is slowly consumed until there is but just a few megs left, and the server will either go down, or you have to restart apache to free it up. I have recompiled apache in every config I can, no change, reinstalled cpanel, changed config settings, in apache, mysql, and php.ini, no effect. The logs are showing me nothing. Any body have a clue. I have looked at similar posts, with no resolution found. This box has very few accounts on it. I am at a total loss. This is a new setup, has been doing this from the start.

Jim

Are you sure its just not being linux? Linux caches almost all ram for later use.

Originally posted by thelinuxguy
Are you sure its just not being linux? Linux caches almost all ram for later use.

Yeh prety sure as the box slows to a halt, or crahes. The only way to get running like it should is restart apache, and then it will work for 3 to 5 hours before it is down to a crawl, or crashes.
I will look and see if I have an older free, just restarted it again so it looks ok now.

Jim

total used free shared buffers cached
Mem: 472748 466032 6716 0 37024 108152
-/+ buffers/cache: 320856 151892
Swap: 262136 44892 217244


Not even sure when this was, just something I had in a note.

This box is a VPS, thus the odd looking mem numbers.

Originally posted by newpoint
total used free shared buffers cached
Mem: 472748 466032 6716 0 37024 108152
-/+ buffers/cache: 320856 151892
Swap: 262136 44892 217244


Not even sure when this was, just something I had in a note.

This box is a VPS, thus the odd looking mem numbers.


Sorry, first time i want to know how to tell the memory thing?

like 472748 = 47MB?

One thing I am going by, is you can check the stats in whm every 30 minutes or so, and see the mem in use creeping up to over 90% usage, at which point the server has become slow or totaly unresponsive.


Jim

Originally posted by terran11355@
Sorry, first time i want to know how to tell the memory thing?

like 472748 = 47MB?

Would be 472 megabytes.

Jim

hi,

I wonder how to tell how much memory do you allow to use?
and how much are you using now?

i have a VPS account

in whm? or somewhere else?


thanks
sean

Steve what would you charge me to get a look at the box.

Just to add the last recompile I did on apache killed the front page extensions.

Jim

Originally posted by terran11355@
hi,

I wonder how to tell how much memory do you allow to use?
and how much are you using now?

i have a VPS account

in whm? or somewhere else?


thanks
sean

In WHM you can look under Server Status, if you log into shell you type in free, and hit enter, or top and hit enter, will give you a idea of what is going on with your server.

Jim

If you haven't done so already, in WHM under the "Security" menu heading, click on "Modify apache memory usage" this should aid in keeping the box alive. If you use mysql, you may want to look into fixing that up to via /etc/my.cnf. There are other things to look into ( may just need more ram ) but its hard to diagnose such things without direct access to the box.

All of this has been done numerous times, with many different configs to mysql and apache, different versions of WHM/Cpanel.

Any way I do believe the problem or problems have been found.

First upgraded to the latest version of Zend optimizer, this stabalized the memory issue. The memory stayed at around 40% to 50%. Which seems a little high for this box. But better than the constant apache restarts.

I next downgraded WHM/Cpanel to the last Stable version, had upgraded to the latest Edge during all of this. Amazingly the memory usage dropped to around 20% immediatly and has reamainded at about that level since, this is the normal level for this machine.

Front page had quit working on all sites, during one of the apache recompiles, come to find out after much digging. That the AddModule mod_frontpage.c was commented out in httpd.conf, uncommenting fixed that issue.

What a total night mare this has been. See what tommorrow brings.

Jim

Because if you are, apparently the httpd that is packaged with it leaks semaphores. Having said that, memory consumption will continue to go up until there is nothing left. Hence, you'll have to restart/reboot.

Lamp.