SLES 11 SP2 and apache 2.2.12. We need a 3rd party module, mod_proxy_msrpc, installed in apache but it requires apache 2.4. My question, what is involved in upgrading to 2.4? Meaning, apache 2.2.12 was installed with the install of SLES11 (with rpm). There does not seem to be a 2.4 rpm for apache so i would have to install using source files. With all the config options and the different places on the disk that apache is installed, it seems to me to be 1 big headache to install from source. Has anyone updated to apache 2.4 using source? Can you share how you did this?
Hi
You would need to upgrade to SP3 as well as run an unsupported version from the Open Build Service;
https://build.opensuse.org/package/show/Apache/apache2
Then you would need to build the third party module, or maybe ask the following user to enable an SP3 build?
https://build.opensuse.org/package/show?project=home%3Aj-engel%3Aapache&package=apache2-mod_proxy_msrpc
[QUOTE=malcolmlewis;19379]Hi
You would need to upgrade to SP3 as well as run an unsupported version from the Open Build Service;
https://build.opensuse.org/package/show/Apache/apache2[/quote]
Define unsupported.
[quote]Then you would need to build the third party module, or maybe ask the following user to enable an SP3 build?
https://build.opensuse.org/package/show?project=home%3Aj-engel%3Aapache&package=apache2-mod_proxy_msrpc[/QUOTE]
I plan on installing from source but i am a little confused by this response. Mod_proxy_msrpc will only build and run with aoache 2.4 and if you have to have SP3 to get apache 2.4 (unsupported) then how is this user using a SP2 build?
Hi carnold6,
You won’t be able to complain to SuSE about things going wrong with Apache 2.4. If some other system (i.e. SMT) relies on an Apache2 server, you cannot ask for support for these other system, as you’re running it against an unofficial httpd version.
Malcolm offered a link to a pre-built (and still unsupported - it’s a “community build”) repository for Apache 2.4 - but that repository only contains 2.4 packages for SP3. Of course, you can either locate and install other RPMs matching the OS version of your choice, or even compile your own, then there’s no definite dependency on SP3.
Regards,
Jens
Hi
Unsupported by SUSE, you would/could be on your own if something breaks
that is not apache related etc or if raising an SR, they may require the
removal of the applications, then reproduce to get some action on it…
There is no build on OBS for apache2 2.4, well you could use it to
build for SP2 I guess.
If you use OBS to build or build your own rpms linked on OBS, a lot of
the security, bugs etc get fixed, rolling your own and there is say a
security fix, you need to patch, rebuild etc. It takes a lot of the leg
work out of the process for you… OBS is also the staging area for
SUSE to cherry pick the packages for inclusion in the next release,
then there is the SUSE specific configurations used, compile options,
the list goes on…
So, what I’m indicating is, a) look at upgrading to SP3 and pick the
already built items from OBS, or b) stick with SP2 (which is out of
support anyway) and use OBS to build (by linking the packages) to
create you own build repository (it’s free to create an account and
build your packages).
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!