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.
Hello,
Yesterday, I was trying to work out why a web application we developed had stopped working on a client's RHEL4 box. As well as our app being broken, apache wouldn't start up on reboot as it had done previously.
The problem was that a recent httpd rpm update had corrupted the system.
running /usr/local/apache2/bin/apachectl start
allowed apache to start. Our app started ok aswell but some of its functionality is still not working.
It looked like the httpd init script in /etc/init.d/ had references to
/usr/sbin/apachectl and /usr/sbin/httpd, so I changed them to point to
/usr/local/apache2/bin/apachectl and /usr/local/apache2/bin/httpd. Now apache is starting on reboot, but some of the apps functionality is still broken. (Its a java app, running on tomcat. Does anyone have any clue as to what might have been corrupted after an update that would cause problems?)
The person who installed the apache on the server didn't remove the httpd rpm before doing so.
Whenever I've installed apache in the past, I've always removed the pre-installed httpd rpm and its dependencies without really knowing why except that I imagined that conflicts could happen. Could someone explain the how and why conflicts do potentially occur?
Also, after an automatic update, is a there a quick way of seeing which files have been modified as a result of the update, other than using 'find' to locate files that have been modified within a certain timeframe?
Thanks.
Unfortunately I don't have access to the server today.
Also, I ended up removing the httpd package and its dependencies to see if that would help, and I noticed that /etc/httpd/conf/httpd.conf .rpmsave was created, so I imagine that any other .rpmsave files that are knocking about are a result of the package removal, rather than the package update. Am I right in thinking that?
No, they are from the update of the package, and they won't be removed or moved back on an rpm -e. You should be able to just move them back in place manually.
Ok, good stuff. I'll have a look when I get the chance.
Incidentally, why when installing a LAMP type server are you generally told to remove the preinstalled packages and then compile from source? What's 'wrong' with the preinstalled packages?
I don't know. I've always used the preinstalled packages unless there is a specific thing I need to run. Perhaps the preinstalled packages don't support something you want or RHEL4 is apache 1.3.x and you need something in 2.0.x?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.