That looks like it's simply processing the domlogs for that domain. That's an intensive process, but it doesn't typically last long per domain. Is this a "budget" or somewhat overloaded server that it's bogging things down when it runs?
Having problems, or maybe questions about WHT? Head over to the help desk!
Well it's actually a VPS, and it's definitely not overloaded (neither is the VPS node).
From what I can gather, it seems to take a long time and it always lingers around. New ones also pop up, so it never seems to go away. It's not bogging it down really, it just uses up the memory all the time and never goes back down to lower levels.
I have found that httpd always eats up excessive ram if apache is compiled with more advanced options like suhousin without the admin actually knowing how to configure them or what they do. This is probably where your issue is.
after installed php 5.2.10
nobody /usr/local/apache/bin/httpd -k start -DSSL
5896 nobody 0
1.3 /usr/local/apache/bin/httpd -k start -DSSL
os : centos 5.3
Has been very fast server. Guide is accurate and if you leave.
Hello. Unfortunately, the site that gave a blank at all clear what should we do, and only 2 to commands and very dumb is my opinion
Please explain here the same or better and do not pass to the other. With command and explain in detail all of us express that we understand. I went to the site and did not catch anything at all
Although Easy Apache is very powerful, a few years ago, I could not successfully make a build without high memory usage. A month or so ago, I really needed to run suphp (so that clients could specify php.ini files in their home directories). Unfortunately, everytime I attempted this, I ended up with apache compiling and not starting at all or running with very high memory usage per process.
With help from CPanel and buying a vps dedicated to testing and now that I have a solid week into reading what each option does and have tried building numerous options, I have a really good idea of what is easy to make work, and what is still a headache to myself. I simply posted the yaml profile for easy apache and the process (more or less an overview) on AR for anyone else that wants a quick way to build a profile that has most common options and user specified php.ini support.
On my test vps, I firmly believe that suhousin and source gaurdian are the culprits to high memory usage. I have spent countless hours building all sort of of builds (basic builds to every other option in easy apache) with these 2 options. At the end, I find that no matter what I do, both of these options suck up at least 400MB of ram per httpd process. Cpanel hinted towards suphp and suhousin are both compatible but you should only use these if you understand what they do and how to configure them. To this day, I still read about them and still don't fully understand why they use so much memory. One of these days I will eventually understand how to configure them correctly.
My best recommendation is what CPanel told me, if you don't understand what it is, don't build it. If you use the YAML file on AR, I can assure you that each HTTPD process won't consume more than 20MB. I have successfully compiled the same profile now on 5 servers (both dedicated and VPS) and have had no issues.
When CPanel compiled that profile with PHP 5.2.10, they ran into a tiny bug with the allow_furl_open directive in php.ini (its awful close to that if I got it wrong).
Due to that bug, I build 5.2.9 which is older and safer. Eventually I will move to 5.2.10, but right now, I have no real need for it.
And suphp works on this profile if you follow that post as a guide. Any internal server errors will be solved by running those commands and clearing the .htaccess files of php directives if you are running apache in dso mode.