Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a 10.04.01 Ubuntu server running webmin version 1.620 and I want to upgrade my apache version from 2.2.14 to 2.2.24 before I upgrade to 2.4. Since this is the first time I"m doing this I did the following steps.
Code:
gunzip -d httpd-2.2.24.tar.gz
tar xvf httpd-2.2.24.tar
./configure
But After i ran ./configure I got this output with an error
Code:
apache2/httpd-2.2.24# ./configure
checking for chosen layout... Apache
checking for working mkdir -p... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
Configuring Apache Portable Runtime library ...
checking for APR... reconfig
configuring package in srclib/apr now
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
Configuring APR library
Platform: i686-pc-linux-gnu
checking for working mkdir -p... yes
APR Version: 1.4.6
checking for chosen layout... apr
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/etc/apache2/httpd-2.2.24/srclib/apr':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details
configure failed for srclib/apr
How can I overcome this? did I miss a step or am I missing some elements in my current apache install?
That totally helped thanks.
But before I install I noticed that there is a specific set of instructions for upgrading apache as opposed to installing a whole version which was the steps I was following.
What would be the better option to do then?
should I do what the apache document says to do during an upgrade or should I just do a whole new install with the upgraded version of apache?
Here are the instructions for upgrading in the apache docs
Quote:
to upgrade across minor versions, start by finding the file config.nice in the build directory of your installed server or at the root of the source tree for your old install. This will contain the exact configure command line that you used to configure the source tree. Then to upgrade from one version to the next, you need only copy the config.nice file to the source tree of the new version, edit it to make any desired changes, and then run:
$ ./config.nice
$ make
$ make install
$ PREFIX/bin/apachectl -k graceful-stop
$ PREFIX/bin/apachectl -k start
Should I just do these steps? I'm guessing I still have to download that newer version of apache and then run this or?
I would use the stable, Ubuntu-supported apache, personally (unless I had a specific reason to upgrade, a spare testing system, and time/manpower to address any issues that might arise due to the upgrade).
Well I have a working web server now with a site on it, would upgrading to the full version change any of the settings I have now for my site? Thats my biggest worry actually. I have two options I can do a slow upgrade from 2.2.14 to 2.2.24 then go to 2.4 or I can just go straight into 2.2.14 to 2.4.
Also is there an Ubuntu specific version of Apache? I was just going to use the package from the apache.org site.
If your web server is working fine, what is the reason/purpose for the upgrade? The more details you give, the better advice you will get from the forum experts.
I ran a scan and one of the critical issue it found was that I have an older version of Apache
Quote:
We found 3 security issues on your server xxx.xxx.com
* important* Apache 2.2 Security Update Available
The version of Apache you are running does not contain the
most recent security fixes.
More Information: http://httpd.apache.org/security/vul...lities_22.html
So that particular secuirty issue is addrssed in apache version 2.2.24. So that is why I wanted to upgrade to that version.
I see that it was patched with three security updates (maybe the ones you are concerned about, though I have absolutely know way of knowing that) on March 8, 2013.
Here is an article to help you understand version numbering in long-term-support Linux distributions: https://access.redhat.com/security/u...g/?sc_cid=3093
(written for Red Hat but the concepts also apply to Ubuntu)
Quote:
Backporting has a number of advantages for customers, but it can create confusion when it is not understood. Customers need to be aware that just looking at the version number of a package will not tell them if they are vulnerable or not. For example, stories in the press may include phrases such as "upgrade to Apache httpd 2.0.43 to fix the issue," which only takes into account the upstream version number. This can cause confusion as even after installing updated packages from a vendor, it is not likely customers will have the latest upstream version. They will instead have an older upstream version with backported patches applied.
Also, some security scanning and auditing tools make decisions about vulnerabilities based solely on the version number of components they find. This results in false positives as the tools do not take into account backported security fixes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.