You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "D. J. Waletzky" <dj...@mediachannel.org> on 2006/09/14 19:33:18 UTC
[users@httpd] RPM upgrades from 2.0.54 to 2.0.59
Hi everyone-
I hope this is isn't too stupid a question, but is there any way I can
avoid recompiling PHP if I upgrade Apache from 2.0.54 to 2.0.59 with an
RPM package? I'm running a server on Fedora Core 3, and I'm really hoping
I can just rpm -i the new version of apache without having to reinstall
php.
The reason I need to do this (and maybe this is another problem entirely)
is because the server's traffic increased exponentially over the last few
days and it seems to be running out of memory every night, if my
/var/log/messages is to be believed. This is causing me to have to call
the hosting company and have the thing rebooted every morning. I'm setting
up a bunch more swap files, but does anyone have some better ideas than
upgrading to 2.0.59 (or even 2.2.3) and increasing swap space?
--
D. J. Waletzky
dj@mediachannel.org
http://dj.waletzky.com/
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] RPM upgrades from 2.0.54 to 2.0.59
Posted by Joshua Slive <jo...@slive.ca>.
On 9/14/06, D. J. Waletzky <dj...@mediachannel.org> wrote:
> Hi everyone-
>
> I hope this is isn't too stupid a question, but is there any way I can
> avoid recompiling PHP if I upgrade Apache from 2.0.54 to 2.0.59 with an
> RPM package? I'm running a server on Fedora Core 3, and I'm really hoping
> I can just rpm -i the new version of apache without having to reinstall
> php.
>
> The reason I need to do this (and maybe this is another problem entirely)
> is because the server's traffic increased exponentially over the last few
> days and it seems to be running out of memory every night, if my
> /var/log/messages is to be believed. This is causing me to have to call
> the hosting company and have the thing rebooted every morning. I'm setting
> up a bunch more swap files, but does anyone have some better ideas than
> upgrading to 2.0.59 (or even 2.2.3) and increasing swap space?
Swap ain't gonna help you. If you are really running out of memory,
you need to start by lowering MaxClients to a level that can be
handled by your server without running out of physical memory. Then
you need to carefully analyze your traffic to see where the load is
coming from. Only then can you start to look for solutions. Likely
issues include slow database connections and otherwise power-hungry
php scripts.
All the configuration you do in apache will probably have a minimal
effect compared to tuning your php and database, but you can also look
here:
http://httpd.apache.org/docs/2.0/misc/perf-tuning.html
Regarding your original question, the two versions are binary API
compatible, so there should be no problem.
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] RPM upgrades from 2.0.54 to 2.0.59
Posted by "D. J. Waletzky" <dj...@mediachannel.org>.
Thanks to all who replied!
The install of 2.0.59 from rpm seemed to go fine, except that when I
restarted httpd, mod_ssl wouldn't load. Luckily I'm not running any SSL
stuff right now, but it is strange. It gave a specific line error for a
binary file.
At any rate, the MaxClients have been adjusted and the server seems to be
humming along. Thanks again, guys.
>
> On Sep 14, 2006, at 10:33 AM, D. J. Waletzky wrote:
>
>> The reason I need to do this (and maybe this is another problem
>> entirely)
>> is because the server's traffic increased exponentially over the
>> last few
>> days and it seems to be running out of memory every night, if my
>
> Further to Joshua's recommendation to adjust your MaxClients setting,
> you may have a memory leak in your setup that causes your httpd
> processes to bloat up as they serve requests. You should be able to
> see that happen in your 'top' display.
>
> Consider using the MaxRequestsPerChild directive to limit the
> lifespan of your httpd processes. Start with a very low value (like
> MaxRequestsPerChild 1000) and see if that causes the problem to go
> away. Then, play with this directive and MaxClients until you arrive
> at a combination that keeps your server alive.
>
> A server with fewer httpd child processes can serve fewer concurrent
> requests, and may be slower, but a slightly slower server is better
> than a dead server! Your operating system should never, ever have to
> swap. Once the OS goes into swap, your server is as good as dead.
>
> S.
>
> --
> sctemme@apache.org http://www.temme.net/sander/
> PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
>
>
>
--
D. J. Waletzky
dj@mediachannel.org
http://dj.waletzky.com/
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] RPM upgrades from 2.0.54 to 2.0.59
Posted by Sander Temme <sc...@apache.org>.
On Sep 14, 2006, at 10:33 AM, D. J. Waletzky wrote:
> The reason I need to do this (and maybe this is another problem
> entirely)
> is because the server's traffic increased exponentially over the
> last few
> days and it seems to be running out of memory every night, if my
Further to Joshua's recommendation to adjust your MaxClients setting,
you may have a memory leak in your setup that causes your httpd
processes to bloat up as they serve requests. You should be able to
see that happen in your 'top' display.
Consider using the MaxRequestsPerChild directive to limit the
lifespan of your httpd processes. Start with a very low value (like
MaxRequestsPerChild 1000) and see if that causes the problem to go
away. Then, play with this directive and MaxClients until you arrive
at a combination that keeps your server alive.
A server with fewer httpd child processes can serve fewer concurrent
requests, and may be slower, but a slightly slower server is better
than a dead server! Your operating system should never, ever have to
swap. Once the OS goes into swap, your server is as good as dead.
S.
--
sctemme@apache.org http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF