LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 06-30-2012, 02:37 AM   #1
aceone
Member
 
Registered: Apr 2009
Posts: 55

Rep: Reputation: 15
upgrading apache


Hi,
It may appear very noob,but i want to know how apache 2.2 to is upgraded higher version on production server?
since a production server has many specific configurations in files,does'nt upgrading apache would overwrite those files?
we may take backup and restore the files but it could cause conflicts.
whats the ideal way of upgrading apache on production server?

guys i have searched a lot about this question but of no help.please guide me.

Thanks & regards
 
Old 06-30-2012, 03:17 AM   #2
lithos
Senior Member
 
Registered: Jan 2010
Location: SI : 45.9531, 15.4894
Distribution: CentOS, OpenNA/Trustix, testing desktop openSuse 12.1 /Cinnamon/KDE4.8
Posts: 1,144

Rep: Reputation: 217Reputation: 217Reputation: 217
Hi,

you don't write what System OS is your server running (RHEL, Ubuntu ...)
and if you have tried (for example on RHEL/CentOS/Fedora)

Code:
# yum check-update httpd
Loading mirror speeds from cached hostfile
 * base: mirror.domain.com
base                                    | 1.1 kB     00:00     

httpd.i386                 2.2.3-63.el5.centos         base
That would obviously upgrade the current version (on my server) to v 2.2.3-63
Code:
httpd -v
Server version: Apache/2.2.3
Server built:   Oct 20 2011 17:00:12

# yum info httpd
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * base: mirror.example.com
Installed Packages
Name       : httpd
Arch       : i386
Version    : 2.2.3
Release    : 53.el5.centos.3
Size       : 3.1 M
Repo       : installed
Summary    : Apache HTTP Server
URL        : http://httpd.apache.org/
License    : Apache Software License
Description: The Apache HTTP Server is a powerful, efficient, and extensible
           : web server.

Available Packages
Name       : httpd
Arch       : i386
Version    : 2.2.3
Release    : 63.el5.centos
Size       : 1.2 M
Repo       : base
Summary    : Apache HTTP Server
URL        : http://httpd.apache.org/
License    : Apache Software License
Description: The Apache HTTP Server is a powerful, efficient, and extensible
           : web server.
 
Old 06-30-2012, 03:54 AM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,582
Blog Entries: 2

Rep: Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037Reputation: 4037
Quote:
Originally Posted by aceone View Post
whats the ideal way of upgrading apache on production server?
Make an exact copy of your production system on a testbox. Now test any action you take on the testbox first to see what happens and if it works like you intended. Run it some time to watch for potential bugs. Never do upgrades on a production system first, always test them on a testbox before doing anything on the production system.
 
Old 06-30-2012, 05:50 AM   #4
arun5002
Member
 
Registered: Aug 2011
Location: Chennai,India
Distribution: Redhat,Centos,Ubuntu,Dedian
Posts: 549
Blog Entries: 5

Rep: Reputation: Disabled
Hi ,
First of all i want to know the reason for your apache upgration on your production environment.If everything goes fine with your current version of apache, I would recommend not to upgrade.I had faced few php software pommo,osticket,frontaccounting stopped working after upgration of apache . If u have strong troubleshooting knowledge of php and apache then u can go for upgration . Befor trying on first on production first tried it on your test environmental with all the stuff which you had installed on production, on your test environment ,and try on test and go for production
 
Old 07-01-2012, 05:05 PM   #5
TB0ne
Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 14,488

Rep: Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543Reputation: 2543
Quote:
Originally Posted by arun5002 View Post
Hi ,
First of all i want to know the reason for your apache upgration on your production environment.If everything goes fine with your current version of apache, I would recommend not to upgrade.
That is bad advice. By that logic, someone would still be running old, unpatched/unupdated (and INSECURE) Apache, with plenty of vulnerabilities for others to exploit. Keeping outward-facing software current is a very basic security step, that you're suggesting not be taken. To extend that a bit; telnet will 'just work' too...so why bother upgrading to SSH? SSHv1 works...why go to SSHv2?
Quote:
I had faced few php software pommo,osticket,frontaccounting stopped working after upgration of apache . If u have strong troubleshooting knowledge of php and apache then u can go for upgration . Befor trying on first on production first tried it on your test environmental with all the stuff which you had installed on production, on your test environment ,and try on test and go for production
Again, spell out your words. The OP does not mention any of those packages, or even if they're using PHP, but asking for help only with Apache upgrade advice. PHP and other packages may not be used in the OP's environment, so introducing them as variables will only confuse the issue.

OP, as lithos and TobiGSD have said, make backups of your existing Apache config files (usually in /etc/apache2), and check what software/modules you're using.
 
Old 07-02-2012, 10:21 PM   #6
phr3ak
LQ Newbie
 
Registered: May 2010
Posts: 8

Rep: Reputation: 0
upgrading apache

Hi,
I have the same issue.On my production servers,we constantly scan server.The OS are Centos and Ubuntu;according to the scan
conducted by AlienVault: I.T Security Vulnerability Report:



Apache 'mod_proxy_ftp' Module Command Injection Vulnerability (Linux)
Risk:High
Application:http
Port:80
Protocol:tcp

Overview: The host is running Apache and is prone to Command Injection
vulnerability.
Vulnerability Insight:
The flaw is due to error in the mod_proxy_ftp module which can be exploited
via vectors related to the embedding of these commands in the Authorization
HTTP header.
Impact:
Successful exploitation could allow remote attackers to bypass intended access
restrictions in the context of the affected application, and can cause the
arbitrary command injection.
Impact Level: Application
Affected Software/OS:
Apache HTTP Server on Linux.
Fix: Upgrade to Apache HTTP Server version 2.2.15 or later

my point is instead of taking backup of files and then restoring them,isnt there a "standard method" of upgrading apache so that the files remains untouched or not being renamed to *.bak?
any help in this regard will be appreciated.

Thanks & regards

Last edited by phr3ak; 07-03-2012 at 12:42 AM. Reason: provided more info
 
Old 07-03-2012, 12:19 PM   #7
anomie
Senior Member
 
Registered: Nov 2004
Location: Texas
Distribution: RHEL, Scientific Linux, Debian, Fedora, Lubuntu, FreeBSD
Posts: 3,930
Blog Entries: 5

Rep: Reputation: Disabled
@phr3ak: IMO, you should have started a new thread for this. Your questions may be similar, but you've thrown in the additional wrinkle of a specific security report.

In your case, it's simple - if you're not using mod_proxy_ftp, then disable it.

When you "upgrade" Apache via your distro's package manager, what's normally really happening is you're updating a minor version or applying backported security/bug fixes. In most cases, it should not touch your existing configuration files. (But there can be exceptions. So you need to back those up.) In most cases, such an upgrade is replacing binary programs -- including Apache HTTP server itself, and any of its affected modules.

For this reason, and in a sea of cascading dependencies, it can be difficult to roll back to a previous version if things go wrong. There are two things I do:
  1. Apply the updates on a very similar test system first. Then regression test.
  2. Prior to applying updates in prod, do a complete dump(8) of the system's filesystems. Even though you've already tested in test, on the small chance you have to roll back to a previous state, this will save you a major headache / job / etc.

Last edited by anomie; 07-03-2012 at 12:21 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
upgrading to apache 2 linuxapprentise Linux - Software 3 08-04-2006 02:55 PM
upgrading to apache 1.34 ic_torres Linux - Networking 0 03-23-2006 05:39 AM
Upgrading (Apache) emptystrings Slackware 7 11-10-2004 11:32 PM
Upgrading Apache sveioen Slackware 3 05-20-2004 06:28 PM
Upgrading Apache ???? Virtualhate Linux - Newbie 1 05-18-2004 11:06 PM


All times are GMT -5. The time now is 09:35 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration