| 1 |
Oh sorry... |
| 2 |
|
| 3 |
I forgot to mention the server details |
| 4 |
Apache: 2.0.49-r1 |
| 5 |
Mod_PHP: 4.3.6-r1 |
| 6 |
OpenSSL: 0.9.7c |
| 7 |
Kernel: 2.4.26 |
| 8 |
|
| 9 |
Previously I had mod_mono and mailman enabled but I shutted that down this |
| 10 |
week with no result. I also putted down mysql_log for apache, but for that |
| 11 |
component I had to overwrite a two modules mod_log_config.so and |
| 12 |
mod_logio.so . I am now compiling apache so that the modules are the |
| 13 |
default ones. |
| 14 |
|
| 15 |
When looking around I ran into was DO NOT USE Apache 2 and PHP in a |
| 16 |
production environment :( |
| 17 |
Also I already tried to look at ulimit before you mentioned, but it did |
| 18 |
not give really satisfying answers :( |
| 19 |
|
| 20 |
What could be a memory consuming item in the site might be: |
| 21 |
- a dynamically generated image (1x1) pixel, so that should not be too |
| 22 |
expensive for 800 pageviews a day, the script cleans up the mess itself. |
| 23 |
- A download of 50 Meg, which was streamed by PHP for leechprotection at |
| 24 |
the same time gzip was on, this could be a really memory consuming option. |
| 25 |
- The CMS (Mambo Open Source 4.5 1.0.7) |
| 26 |
|
| 27 |
Well still trying to get it stable :( |
| 28 |
|
| 29 |
> Hi! |
| 30 |
> |
| 31 |
> On Fri, 14 May 2004, Raymond den Ouden wrote: |
| 32 |
>> as I said a few days ago I launched a public web-site. after to days the |
| 33 |
>> server was like a zombie. |
| 34 |
> [... detective work ...] |
| 35 |
>> But on killing apache2 the server came back and the command free told |
| 36 |
>> me that 500 mb of swap and 350 MB was free-ed. |
| 37 |
>> |
| 38 |
>> I have looked around how I could strict apache in memory usage for the |
| 39 |
>> apache user. |
| 40 |
>> What is the best way to prevent that apache takes all memory or maybe |
| 41 |
>> exclude a amount of memory for apache? |
| 42 |
> |
| 43 |
> Well, such memory hogging may have different causes. First off: |
| 44 |
> about which exact version of Apache are we talking? Did you |
| 45 |
> google about that version and possibly known memleaks? Other than |
| 46 |
> that it's important to keep in mind that some forms of PHP and/or |
| 47 |
> CGIs may have leaks that pile onto Apache's account. |
| 48 |
> |
| 49 |
> Beyond that, limiting memory usage may be done with ulimit. But I |
| 50 |
> don't know how Apache handles (if at all) bumping into such a |
| 51 |
> limit. |
| 52 |
> |
| 53 |
> I for one would rather try to find the source of the leak than |
| 54 |
> just curing symptoms. Although I admit that getting your service |
| 55 |
> up and running first might be feasible, remember that the |
| 56 |
> underlying problem might be more grave and restarting your |
| 57 |
> webservice might grind you into deeper trouble. |
| 58 |
> |
| 59 |
> Greets & HTH, |
| 60 |
> Tobias |
| 61 |
> -- |
| 62 |
> Thank you for calling $PROVIDER helpdesk. If your cupholder is |
| 63 |
> broken, please press 1. If you want an actual knowledgable support |
| 64 |
> person, please enter the IP representation of a /28 netmask." |
| 65 |
> |
| 66 |
> -- |
| 67 |
> gentoo-security@g.o mailing list |
| 68 |
> |
| 69 |
> |
| 70 |
|
| 71 |
|
| 72 |
-- |
| 73 |
gentoo-security@g.o mailing list |
Archives