Hello All.
I am trying to set up a rails+mongrel+mod_proxy_balance application. Unfortunately the stock apache install on centos is the 2.0 series which does not support mod_proxy_balance. I could not find the 2.2X RPMs on dag or dries either.
Is there a yummy way to upgrade to the 2.2 series of apache? I tried with the individual RMPS but no joy there due to comples web of dependencies.
On Thursday 02 November 2006 12:39, Tim Uckun wrote:
Hello All.
I am trying to set up a rails+mongrel+mod_proxy_balance application. Unfortunately the stock apache install on centos is the 2.0 series which does not support mod_proxy_balance. I could not find the 2.2X RPMs on dag or dries either.
Is there a yummy way to upgrade to the 2.2 series of apache? I tried with the individual RMPS but no joy there due to comples web of dependencies.
I assume you mean the RPMs available from apache at http://www.apache.org/dist/apr/binaries/rpm/i386/ and http://www.apache.org/dist/httpd/binaries/rpm/i386/ ?
After removing all the stuff that depends on apache (mod_python, mod_ssl, http_suexec, webalizer, subversion, etc.), the Apache supplied RPMs seem to install fine. Of course you wouldn't be using all the same patches and configs from the CentOS rpm version, and there's no guarantee it will work well with the provided libraries (it probably will provided they have all their requires in the spec file correct). If you don't need any functionality out of Apache other than what you are putting in yourself (rails, mongrel, mod_proxy_balance), this might work.
The other solution if there isn't a CentOS RPM out is to grab the SRPM for httpd 2.2 from Apache, the SRPM for httpd 2.0 from CentOS, and try to try to put the relevant good bits of the CentOS RPM spec file into the apache spec file and build your own RPM. Fairly daunting if you aren't familiar with the build system (or if you are and the spec file is overly complex on either end). I wouldn't recommend this for something as complex as Apache...
After removing all the stuff that depends on apache (mod_python, mod_ssl, http_suexec, webalizer, subversion, etc.), the Apache supplied RPMs seem to install fine. Of course you wouldn't be using all the same patches and configs from the CentOS rpm version, and there's no guarantee it will work well with the provided libraries (it probably will provided they have all their requires in the spec file correct). If you don't need any functionality out of Apache other than what you are putting in yourself (rails, mongrel, mod_proxy_balance), this might work.
I didn't want to start down that path of uninstalling everything and then reinstalling them again. I was kind of hoping there would be a repository I could add to repos.d and then yum upgrade httpd.
I am afraid I don't have the time or the expertise to try and roll my own RPMs.
On Fri, 2006-11-03 at 13:09 +1300, Tim Uckun wrote:
After removing all the stuff that depends on apache (mod_python, mod_ssl, http_suexec, webalizer, subversion, etc.), the Apache supplied RPMs seem to install fine. Of course you wouldn't be using all the same patches and configs from the CentOS rpm version, and there's no guarantee it will work well with the provided libraries (it probably will provided they have all their requires in the spec file correct). If you don't need any functionality out of Apache other than what you are putting in yourself (rails, mongrel, mod_proxy_balance), this might work.
I didn't want to start down that path of uninstalling everything and then reinstalling them again. I was kind of hoping there would be a repository I could add to repos.d and then yum upgrade httpd.
I am afraid I don't have the time or the expertise to try and roll my own RPMs.
---- I certainly don't see packages in either dev.centos.org or centos.karan.org which is the places that I would check for something like this.
Apache 2.2 rpm's for CentOS 4 (or RHEL 4) would seem to be something of interest to more than just you.
Craig
I certainly don't see packages in either dev.centos.org or centos.karan.org which is the places that I would check for something like this.
These packages have been requested a few times, but it's more an implementation issue than anything else. apache has a fair amount of stuff built against it, and it would require rebuilding all of those packages, which will then not work with the current apache.
The end result is you'd have httpd-2.0.52-x, and httpd-2.2-x, which would each have their own php builds, mod_perl builds, mod_auth-foo builds etc. It basically causes several packages to be built twice to accomodate one package, and it's been an effort vs demand thing.
Apache 2.2 rpm's for CentOS 4 (or RHEL 4) would seem to be something of interest to more than just you.
If more people are interested and pipe up, then it may be that the demand is enough to warrant a separate build for this. So far that hasn't been the case. Suggestions and support are always welcome.
The end result is you'd have httpd-2.0.52-x, and httpd-2.2-x, which would each have their own php builds, mod_perl builds, mod_auth-foo builds etc. It basically causes several packages to be built twice to accomodate one package, and it's been an effort vs demand thing.
I thought having loadable modules were supposed to ease this problem not make it harder.
I guess the 2.2 branch must be different enough to require all new modules to be built.
On Thu, 2006-11-02 at 21:28 -0500, Jim Perrin wrote:
I certainly don't see packages in either dev.centos.org or centos.karan.org which is the places that I would check for something like this.
These packages have been requested a few times, but it's more an implementation issue than anything else. apache has a fair amount of stuff built against it, and it would require rebuilding all of those packages, which will then not work with the current apache.
The end result is you'd have httpd-2.0.52-x, and httpd-2.2-x, which would each have their own php builds, mod_perl builds, mod_auth-foo builds etc. It basically causes several packages to be built twice to accomodate one package, and it's been an effort vs demand thing.
Apache 2.2 rpm's for CentOS 4 (or RHEL 4) would seem to be something of interest to more than just you.
If more people are interested and pipe up, then it may be that the demand is enough to warrant a separate build for this. So far that hasn't been the case. Suggestions and support are always welcome.
---- FWIW - I am in a similar situation where I am running CentOS 4 and resorted to using fcgid for interaction with ruby on rails since Apache 2.2 and mod_proxy_balance hasn't been available to me. See the OP trying to implement rails/apache-2.2/mod_proxy_balancer/mongrel solution which is at the moment, the high performance solution - much more so than apache-2.0 or lighttpd with fcgid.
I would love to see Apache 2.2 packages (perhaps built against the PHP-5.x packages also in dev.centos.org) built but so far, that only makes 2 of us.
I should note though, that I anticipated simply upgrading this server to CentOS-5 in order to achieve this when it becomes available/stable in order to switch over to Apache-2.2.
I do appreciate all that you have done - especially the ruby packages in dev.centos.org which I have been using for nearly 10 months now. I can also appreciate that a one-time roll of the packages is one thing but it almost becomes a commitment to errata re-rolls too, which given the history of apache & php, is not infrequent.
Craig
Tim Uckun spake the following on 11/2/2006 4:09 PM:
After removing all the stuff that depends on apache (mod_python, mod_ssl, http_suexec, webalizer, subversion, etc.), the Apache supplied RPMs seem to install fine. Of course you wouldn't be using all the same patches and configs from the CentOS rpm version, and there's no guarantee it will work well with the provided libraries (it probably will provided they have all their requires in the spec file correct). If you don't need any functionality out of Apache other than what you are putting in yourself (rails, mongrel, mod_proxy_balance), this might work.
I didn't want to start down that path of uninstalling everything and then reinstalling them again. I was kind of hoping there would be a repository I could add to repos.d and then yum upgrade httpd.
I am afraid I don't have the time or the expertise to try and roll my own RPMs.
You might have to wait for Enterprise 5 (CentOS 5) for apache 2.2 if you don't want to fight. Shouldn't be more than a few months. You could play on Fedora Core 6, as I think that is what RHEL 5 will be based on.
On Thursday 02 November 2006 16:09, Tim Uckun wrote:
After removing all the stuff that depends on apache (mod_python, mod_ssl, http_suexec, webalizer, subversion, etc.), the Apache supplied RPMs seem to install fine. Of course you wouldn't be using all the same patches and configs from the CentOS rpm version, and there's no guarantee it will work well with the provided libraries (it probably will provided they have all their requires in the spec file correct). If you don't need any functionality out of Apache other than what you are putting in yourself (rails, mongrel, mod_proxy_balance), this might work.
I didn't want to start down that path of uninstalling everything and then reinstalling them again. I was kind of hoping there would be a repository I could add to repos.d and then yum upgrade httpd.
When I tested, I just kept pasting the conflicting rpms into an rpm -e command line, and removed them all at once. After confirming they isntalled correctly and then uninstalling them, I just replaced the rpm -e (or yum remove) in the remove command with yum install.
On my system it was: rpm -e mod_perl-1.99_16-4.centos4.i386 mod_python-3.1.3-5.1.i386 mod_ssl-2.0.52-28.ent.centos4.i386 php-5.1.4-1.centos.i386 httpd-manual-2.0.52-28.ent.centos4.i386 httpd-suexec-2.0.52-28.ent.centos4.i386 httpd-devel-2.0.52-28.ent.centos4.i386 httpd-2.0.52-28.ent.centos4.i386 system-config-httpd-1.3.1-1.noarch webalizer-2.01_10-25.i386 apr apr-devel apr-util apr-util-devl subversion
and
yum install mod_perl-1.99_16-4.centos4.i386 mod_python-3.1.3-5.1.i386 mod_ssl-2.0.52-28.ent.centos4.i386 php-5.1.4-1.centos.i386 httpd-manual-2.0.52-28.ent.centos4.i386 httpd-suexec-2.0.52-28.ent.centos4.i386 httpd-devel-2.0.52-28.ent.centos4.i386 httpd-2.0.52-28.ent.centos4.i386 system-config-httpd-1.3.1-1.noarch webalizer-2.01_10-25.i386 apr apr-devel apr-util apr-util-devel subversion
yum really makes this easy. I would recommend using rpm -e fpr the uninstall because it will error and not remove any packages until you correctly specify all the packages, making you specify them all at once (useful to make sure you have a full list of what you've removed).
I am afraid I don't have the time or the expertise to try and roll my own RPMs.
Understood. This would most likely be a massive undertaking with Apache.
-
Craig White -
Jim Perrin -
Kevan Benson -
Scott Silva -
Tim Uckun