From: dale's l. a. <li...@be...> - 2002-08-04 22:28:50
|
Hi Joe, On Sunday, August 4, 2002, at 10:27 PM, Joe Cooper wrote: > Whoah, hold on, Dale! You're piling up symptoms and problems and getting > a lot of them jumbled up, I think. Relax, and think things through before > creating more problems for yourself. This is why I stepped away from the computer :) > Proceed with caution when you begin to see signs of problems on your > system, particularly when it comes to dependencies, perl module mismatches, > etc. If this is a production machine, you should follow the doctors rule > of "First, do no harm." It is a production machine, and I was trying to not do any harm. > The latest Red Hat Apache package is secure--as is their custom, when > possible, they patch the same version to fix known issues rather than jump > to an untested version. This is a very nice thing for them to do for > those of us who have production systems to maintain. Leave it be! Forget > about upgrading Apache to 1.3.26. So far everything I had heard was that to get the fix I needed to get the 1.3.26 version of apache. I was not however trying to upgrade apache at all. When I ran the up2date (after registering via their setup) it downloaded and installed apache 1.3.22. And then sometime later - about 1 hour after it showed that it finished downloading tons of stuff, somehow apache stopped running. > Though the fact that it wasn't running after the upgrade might be a > concern, if you have the latest Red Hat package you are not subject to the > security bug you're worrying about. If it is running now, and you have no > other reason for concern with your Apache, leave it be! The original install was via a clean 7.2 system install. From March of this year. No patches or anything else was done to apache - other than changes to httpd.conf. > Ok, so you say Webmin is working again? If that's so, let's forget about > it for now too. Webmin is almost as important on this machine as apache :) > Finally, you're down to MySQL. You haven't told us what dependency > problems you're getting. basically the mysql php stuff (which I do not even use php on this machine - at least at present). And mod_auth_mysql was another. That and the development headers and some libraries. > You showed us some perl errors you got when running Webmin (this could > indicate you've upgraded perl in an incomplete manner--i.e., several of > the modules you had installed were not installed in the new perl > path...Probably perl modules that weren't installed from RPMs...this can > be fixed in a few ways, but again, if you aren't seeing these problems > anymore, leave it be!). These errors only occurred after up2date. The original install worked fine. Maybe up2dtae hadn't finished moving everything around when I tried getting back into webmin. > But you've said nothing about a MySQL installation until this message > Again, the question arises, do you need to upgrade? Is there some feature > or bug-fix that you must have that the Red Hat package doesn't supply? If > it is a known security issue, the Red Hat package will address > that--regardless of whether the version appears to be the same...if Red > Hat has issued and errata about the problem, they have patched the latest > package with the security fix. I need to install unixodbc and the mysql driver. I was trying to follow the instructions on the unixodbc website which stated I needed to compile it in and point to the mysql source directory while installing the mysql drivers. This was the only reason. Mysql is not currently in use on this machine, however, over the weekend I uploaded a couple of databases that I need to start coding with (via odbc) for a major upgrade to the site. Hence trying to install unixodbc and the mysql odbc drivers. At this point, Webmin doesn't see mysql, and it appears I have the latest version installed, but, not running properly. The version that came with RH 7.2 as far as I know should be fine for my uses. If only I could get the rpm manager to give me some real info. When running up2date, it showed that it was downloading the previous version of mysql and claimed to install it. But, I can't find it and neither can webmin. Any suggestions? 3.2.3-51 is "installed" and claims to be running, but the admin tool can't connect to it. > Anyway, up2date is a /great/ thing. If you run it whenever there are > updates available, you'll be way ahead of the pack in keeping your box > secured. The only problems that can result are when you've installed > packages from different sources than Red Hat. Things can get weird in > such a case--so add those to your excluded packages list immediately > before they can cause you any trouble. And if possible, avoid using > non-Red Hat packages...this means, if you don't need a feature present > only in a newer version, stick with the Red Hat package. I've learned > this from years of experience--I have the ability to build my own RPMs > from scratch, but I never do so if the package Red Hat provides is > suitable. And I won't even discuss installing a bunch of stuff from > tarball for a production machine, if it can be avoided. I even package my > perl modules using cpanflute, rather than install them the old-fashioned > way. It makes life a lot easier down the road... Sounds good, but also on another machine I tried to get the patched version of php using up2date and from what I could tell, it wouldn't install it. On the only reply I got form redhat, I was told up2date would only install the versions of the software that cmae with that version of the distribution, anything newer I would have to pay them for - which on one hand makes sense, but on the other would seem to make up2date useless. Then again, my past experience with both redhat and suse support is well, they both make Microsoft look like the worlds most considerate support organization. So I guess the question is, how do I get rid of the version of mysql that seems to be onmy server and stick with the "normal" one that webmin can see and work with (in an attempt to keep this at least a little bit related!). Thanks again for the replies and any additional suggestions on how to deal with this mysql issue would be greatly appreciated. Dale > dale's list account wrote: >> Hi Jim, >> Unfortunately I did. However, not sure what happened, but I left the >> computer for a bit (the frustration level was getting too high) and just >> received an email from my co-loc host that apache had stopped. The damn >> up2date killed the existing apache (after it installed a newer, but still >> security problem version) and didn't launch the newer version it >> installed. >> However, at least now webmin does work again. >> If anyone has any suggestions on how to update mysql 3.23- 41 to the >> latest as well as apache to the latest 1.3.26 (with the security bug >> fixed) using RPM I would greatly appreciate it. >> I always get these dependency warnings with no way around it. >> Thanks again, >> Dale > > > -- Joe Cooper <jo...@sw...> > Web caching appliances and support. > http://www.swelltech.com > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list |