upgrading apache 2.0.40 (RH8 included) to 2.0.43 help needed
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
upgrading apache 2.0.40 (RH8 included) to 2.0.43 help needed
RH8 comes with apache 2.0.40, i wanted to update to the latest one, 2.0.43. i had no content on the server and only a couple changes in the httpd.conf file so i didnt care about losing it.
so downloaded the file from apache.org, did the whole gzip and tar thing. i used # /.configure --prefix=/etc/httpd where RH8 has it installed thinking itd just install over it. after, my httpd.conf file was still the same (not overwritten). i did a #rpm -qa httpd and #rpm -qa | grep httpd and it returned httpd-2.0.40-8.
so i thought id try installing into a new location, i went with the default /usr/local/apache2 and it seemed to install fine, all the files where present, i could start the server with apachectl. but strangely, server ID tags say "apache 2.0.40" and when i do a #rpm -qa | grep httpd again it still returns only 2.0.40.
did i do something wrong? which apache am i actually running?
Well, uninstall apache rpm
rpm -e apache
then edit the startup files
/etc/init.d/httpd, it's been a long time sinse I used RH setup, so you might thinker with it for a while.
couldnt uninstall, too many dependencies. i guess ill just keep looking at the config files. i mean, if it installed into a new dir with all files present, and im starting it from apachectl in the new bin dir, im pretty sure its 2.0.43, theres probaly some config someplace pointing everything to the old one. but rpm -qa should still find the 2.0.43 package.
Well probably there are a lot of depencies like PHP, etc. post the depencies errors here ... Apache v2.0.44 is out by the way ... and if you want a working configuration (incl. PHP) why not check out this thread. Ignore the chrooting part and just read the configure part and the httpd.conf. After installing that you have a secured PHP able server ... probably you will need to customize the modules ... the Apache v2.0 Documentation is just excellent :-)
You've done a GREAT job on the documentation on that!!
Thank you so much!!!
Now how would I remove/uninstall the prior install of apache 2.0.40? I would want to do this right? Since I wont have the same locations for DocRoot, and the other apache files, it would be wise to remove them?
thank you!
*side note* Your doing this all from the tar.gz file correct?
Yes of course from the .tar.gz files ... well for removing it I am not sure what RPM's have been installed. Honestly I never installed Apache or PHP via RPM. But first of all try rpm -a apache if that fails then post the error message here :-)
Basically I want to uninstall the current version of Apache 2.0.40 and then install Apache 2.0.44. I would think it would be simple, but it looks like it is not.
I want to get ride of ALL traces of apache 2.0.40 on my current box. (i.e folders, conf files, dir root, doc root etc) And then install Apache 2.0.44. I'm not sure if I can just "rm -r" or what?
This can't be that hard. Maybe this is just the wrong forum to ask? Wrong section?
i have found using rpms is a real pain in the rear sometimes...especially when u want to uninstall something, i usually stick to the command line options but i have found sometimes a stubborn package can be removed using the gui's.
for example:
trying to install snort or whatever! i found it required me to update some packages but when i try to install them i get errors of "already installed" or if trying to remove "this package is not installed" (that is very frustrating when u just installed it 5 mins ago!)
so i often pull out "GnoRPM+ (gnomes gui for rpm management) and also "Kpackage" (KDES RPM manager) and try to remove or install stubborn rpms, sometimes ignoring deps if u are going to install a newer version later.
while these guis do not always work and they crash sometimes, i find it to be an additional tool that may help when removing or installing packages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.