Sponsored Content
Operating Systems Linux Red Hat Upgrade Apache from 2.2 to 2.4 Post 302920895 by gkman on Monday 13th of October 2014 12:16:41 PM
Old 10-13-2014
Upgrade Apache from 2.2 to 2.4

hello everyone.

let me start by stating I am relatively new to Linux and do not consider myself to be a very professional Linux administrator.

I have a red-hat 6.2 server used as a web server in a closed network (no internet access). however we do have a repository server with many applications (I do NOT manage the repository server, only the web server)

I am currently trying to upgrade the Apache on the server from 2.2 to 2.4, and I find it surprisingly difficult.

first I tried of course to use the repository server.

on the repository server I found the packages of apache-httpd, though they were named httpd24-httpd, httpd24-apr and etc.
I went on to install the packages and found out that this did not update the apache already on the server, but instead installed a new apache on the server. I found that I had two httpd services, and the chkconfig command showed me to have httpd and httpd24-httpd starting up. I later realized the new installation was installed in some weird place under /opt/..(something) directory, while the older version was under /user/sbin/

I didn't find any useful help on Google, only instructions on how to install\upgrade Apache from a tar.gz file. so since I have that file as well, I uninstalled the httpd24 and tried to upgrade from the tar.gz file.

here everything went smoothly (I extracted everything from the archive and ran the configure file successfully), until I tried running 'make' where I received the following error:

Code:
libtool: link: cannot find the library `/usr/lib/libexpat.la' or unhandled argument `/usr/lib/libexpat.la'

I have the libtool installed but the file libexpact.la does not exist (I do have other files in that directory though).

At some point I also finally figured out that the different files of Apache (and almost all the applications on the server) are spread at different directories: /usr/sbin/httpd , /usr/lib64/httpd , and -/usr/include/httpd.

I am stuck with no success in this seemly simple task with no solution in the horizon.

I would very much appreciate help in:
  1. understanding why different apps are spread across so many directories and not under one folder like in windows.
  2. help with updating Apache in it's current place instead of installing an additional Apache

Thanks in advance for the help!
 

5 More Discussions You Might Find Interesting

1. Solaris

help for Upgrade

hi administrator i need help to find solution for this . i have sun fire v880 server with configuration metioned below sun fire v880 2*750 MHz UltraSPARC 111 with 4 GB Memory ( 256*16 ) 36*6 GB hard disks( Internal) with other configuration and now i need to upgrade this server.... (3 Replies)
Discussion started by: dhasanka
3 Replies

2. AIX

OS upgrade

Hello, fellows: I have an old H80 with AIX 4.3, I want to upgrade to AIX 5.3, is this possible? I have read in some documentation that is necesary do it version to version, I mean... 4.3->5.1 5.1->5.2 5.2->5.3, anybody have this experience? I will aprecciate yor help. Kind regards. (2 Replies)
Discussion started by: GEIER
2 Replies

3. Solaris

Upgrade Apache to new version? Solaris 10, goal:PHP

Hello, I have been searching on unix.com and google in general. I can't find what I am looking for. Maybe too dumb of a question. I've downloaded and installed the sunfreeware package for PHP 5.3.6 and made sure all dependencies are satisfied. Apache 2.2.8 is currently installed and... (2 Replies)
Discussion started by: CSLibrary
2 Replies

4. Web Development

Apache module development on apache 2.2

Hi, I'm new to developing modules for Apache. I understand the basics now and can develop something simple which allows a 'GET' request to happen, but what I want to do is actually 'POST' information to my site. I know the basic POST Request works and I can see that it is post by looking at... (2 Replies)
Discussion started by: fishman2001
2 Replies

5. Red Hat

Process not running: /opt/java15/jdk/bin/java -classpath /opt/apache/apache-ant-1.7.0-mod/lib/ant-la

Have no idea on what the below error message is: Process not running: /opt/java15/jdk/bin/java -classpath /opt/apache/apache-ant-1.7.0-mod/lib/ant-launcher.jar org.apache.tools.ant.launch.Launcher -buildfile build.xml dist. Any help? (3 Replies)
Discussion started by: gull05
3 Replies
MOD_APPARMOR(8) 						     AppArmor							   MOD_APPARMOR(8)

NAME
mod_apparmor - fine-grained AppArmor confinement for Apache DESCRIPTION
An AppArmor profile applies to an executable program; if a portion of the program needs different access permissions than other portions, the program can "change hats" via aa_change_hat(2) to a different role, also known as a subprofile. The mod_apparmor Apache module uses the aa_change_hat(2) mechanism to offer more fine-grained confinement of dynamic elements within Apache such as individual php and perl scripts, while still allowing the performance benefits of using mod_php and mod_perl. To use mod_apparmor with Apache, ensure that mod_apparmor is configured to be loaded into Apache, either via a2enmod, yast or manual editing of the apache2(8)/httpd(8) configuration files, and restart Apache. Make sure that apparmor is also functioning. Once mod_apparmor is loaded within Apache, all requests to Apache will cause mod_apparmor to attempt to change into a hat named by the URI (e.g. /app/some.cgi). If no such hat is found, it will fall back to attempting to use the hat DEFAULT_URI; if that also does not exist, it will fall back to using the global Apache profile. Most static web pages can simply make use of the DEFAULT_URI hat. Additionally, before any requests come in to Apache, mod_apparmor will attempt to change hat into the HANDLING_UNTRUSTED_INPUT hat. mod_apparmor will attempt to use this hat while Apache is doing the initial parsing of a given http request, before its given to a specific handler (like mod_php) for processing. Because defining hats for every URI/URL often becomes tedious, mod_apparmor provides the AAHatName and AADefaultHatName Apache configuration options. AAHatName AAHatName allows you to specify a hat to be used for a given Apache <Directory>, <DirectoryMatch>, <Location> or <LocationMatch> directive (see the Apache documenation for more details). Note that mod_apparmor behavior can become confused if <Directory*> and <Location*> directives are intermingled and it is recommended to use one type of directive. If the hat specified by AAHatName does not exist in the Apache profile, then it falls back to the behavior described above. AADefaultHatName AADefaultHatName allows you to specify a default hat to be used for virtual hosts and other Apache server directives, so that you can have different defaults for different virtual hosts. This can be overridden by the AAHatName directive and is checked for only if there isn't a matching AAHatName or hat named by the URI. If the AADefaultHatName hat does not exist, it falls back to the DEFAULT_URI hat if it exists (as described above). URI REQUEST SUMMARY
When profiling with mod_apparmor, it is helpful to keep the following order of operations in mind: On each URI request, mod_apparmor will first aa_change_hat(2) into ^HANDLING_UNTRUSTED_INPUT, if it exists. Then, after performing the initial parsing of the request, mod_apparmor will: 1. try to aa_change_hat(2) into a matching AAHatName hat if it exists and applies, otherwise it will 2. try to aa_change_hat(2) into the URI itself, otherwise it will 3. try to aa_change_hat(2) into an AADefaultHatName hat if it has been defined for the server/vhost, otherwise it will 4. try to aa_change_hat(2) into the DEFAULT_URI hat, if it exists, otherwise it will 5. fall back to the global Apache policy BUGS
mod_apparmor() currently only supports apache2, and has only been tested with the prefork MPM configuration -- threaded configurations of Apache may not work correctly. There are likely other bugs lurking about; if you find any, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>. SEE ALSO
apparmor(7), subdomain.conf(5), apparmor_parser(8), aa_change_hat(2) and <http://wiki.apparmor.net>. AppArmor 2.7.103 2012-06-28 MOD_APPARMOR(8)
All times are GMT -4. The time now is 10:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy