| 1 |
On Wed, Jan 12, 2011 at 1:59 PM, Kaddeh <kaddeh@×××××.com> wrote: |
| 2 |
|
| 3 |
> So, I have run into an interesting problem while building out a web server |
| 4 |
> for a client which I haven't come across before and I was hoping that the |
| 5 |
> list would be a good way for me to find the answer. |
| 6 |
> |
| 7 |
> A little beckground on the systems: |
| 8 |
> P4 @ 3.0Ghz |
| 9 |
> 2GB PC2 4200 |
| 10 |
> 2x 250GB drives in RAID1 |
| 11 |
> |
| 12 |
> The system configurations are default for the most part with the server |
| 13 |
> running MySQL and Apache. |
| 14 |
> |
| 15 |
> The problem that I am running into at this point, however is that the |
| 16 |
> machine seems to run out of memory and will segfault either apache or mysql |
| 17 |
> when does so, when apache segfaults, it is a recoverable error, when mysql |
| 18 |
> does it, mysql can't recover short of restarting it. |
| 19 |
> |
| 20 |
> At this point, I have found a soft fix by running a cron job every 6 hours |
| 21 |
> or so to clear the cached memory, which seems to be the problem, however, I |
| 22 |
> would like to find a more permanent fix to this issue. |
| 23 |
> |
| 24 |
> Anything that would help at this point would be much appreciated. |
| 25 |
> |
| 26 |
> Cheers |
| 27 |
> |
| 28 |
> Kad |
| 29 |
> |
| 30 |
|
| 31 |
I've seen a similar problem before: a chrooted webhost running Apache, |
| 32 |
MySQL, and a very old version of phpnuke. MySQL ran a muck using 50%+ of |
| 33 |
CPU time, eventually. I had a cron job set to restart it once an hour, but |
| 34 |
even that became too much. We eventually moved the site to another server |
| 35 |
on a temporary basis, then migrated to vBulletin. |
Archives