Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New to Apache

Status
Not open for further replies.

bobbydale81

IS-IT--Management
Dec 9, 2005
33
US
I recently inherited the job of upgrading from Apache 1.3 to a 2.2 version on a Suse Linux server. I have no prior experience with Apache, so hopefully I won't get flamed for this post. ;-D

After reading over the documenation, it appears that I would have to upgrade grom 1.3 to 2.0, then from 2.0 to 2.2. Can anyone confirm or reject this?

Also, does anyone know where I could obtain some basic beginer's documenation to this? Our sysadmin recently quit and I am just the lowly technician trying to pick up the pieces. Any help is much appreciated!!!
 
I can think of no possible reason why you would have to ride any particular upgrade path. In fact, "upgrade" really isn't correct, as this implies making iterative changes on a file-by-file basis. A new installation of Apache tends to completely overwrite the old one.


And I'm not sure that there is a basic beginner's documentation. I recommend that you start wandering the halls of the Apache site:


Want the best answers? Ask the best questions! TANSTAAFL!
 
If you are running an enterprise version of a distribution, you may want to holdup a bit on any upgrade. It may nullify any service contract you have with the vendor.

 
I checked with the vendor and it will only nullify any support we receive regarding the new version of Apache on the system. So I'm on my own learning it...

Anyhow, I was getting conflicts after I "installed" 2.2 using the install instructions from httpd.apache.org. Specifically, the server was still running version 1.3 and refused to use v2.2, even up reboot. I could not figure out why, so I have tried uninstalling 1.3 in the YaST GUI control center(I was unsure how to uninstall from a command line).

Now, I have gone through the instructions for installation of v2.2 again, and now it doesn't load at all upon reboot. Also, the apachectl command does not work. I am thinking that something is not right in the startup scripts for this Suse Linux, but now I am having problems locating those and understanding how I would refer them to start Apache upon bootstrapping.

Any ideas?

Thanks!
Dale
 
I am not a SUSE guy, but the startup is probably in /etc/rc.d or some related directory.

Look at your log files in APACHEROOT/logs or what is specified in httpd.conf.

Run "./apachectl configtest"

Does the upgrade change httpd.conf? There are several
significant changes between 1.X and 2.X, but if you
capture the changes that are required for your httpd.conf
(compared from the base version) it is usually easily
integrated.

gene
 
In SUSE, the startup files are in /etc/init.d - I am not sure why SUSE did this, but they were at least kind enough to put a little note in /etc/rc.d letting me know about this.

We were able to get v2.2 running... I appreciate the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top