On Mon, Jul 01, 2002 at 10:12:21PM -0000, matthew zonderop wrote:
my apache broke after the patch...had to reinstall the perl modules and uninstall the SSL module which i dont use anyway. but only took 5 mins..rcapache restart no problem...
If you tell us what exactly broke we might be able to work out if anything was wrong and what!
Peter
Peter, the problem with the apache upgrade seems to be that the stock apache from SuSE 7.0 was 1.3.12 (IIRC, it was definately <1.3.19). Then, on 28.April 2001, SuSe seems to have issued a apache 1.3.19 for suse linux 7.0, at least that is what I figure out from the fact that http://www.suse.de/de/support/download/updates/70_i386.html contains links to mod_contrib.rpm, mod_perl.rpm and other modules for apache 1.3.19. Irritatingly, there's no link to an apache 1.3.19 upgrade from that time, maybe you people deleted that when the new apache came out. Now came the new upgrade, and only mod_ssl and apache itself were published. People like me upgraded, got no rpm dependency problems (yes, without using --nodeps), but apache segfaulted on every request. It took me some time to figure out that my apache modules were the culprits, because I _had_ checked for a previous apache upgrade which I might have omitted for some reason - and, as I said, rpm didn't complain. It would have been helpful if the advisory contained a hint about updating the apache modules, because the described update strategy _must_ fail on a stock 7.0. Mind you, I'm not complaining, just trying to give a hint where these problems might come from. cheers, oliver