https://bugzilla.novell.com/show_bug.cgi?id=228690 poeml@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |uli.2001@gmx.de ------- Comment #5 from poeml@novell.com 2007-01-09 03:01 MST ------- The presence of the module "access" in the 'a2enmod -l' output is a definite sign that the list of modules has _not_ been adapted during update (but update from 10.0 or earlier). The thing is, apache 2.2.x needs a different list of modules than apache 2.0.x. Products up to and including 10.0 shipped 2.0.x, and 10.1 onwards came with 2.2.x. Now, if you installed 10.1 (or 10.2) from scratch you can't hit this problem at all, because the list of modules in /etc/sysconfig/apache2 will fit the package. If the apache2 package is updated, it _always_ makes sure that the list of modules is adapted per %post script (by running /usr/share/apache2/apache-20-22-upgrade). There are few situations where this script is not run, like if you update with rpm -U --noscripts, or maybe if something else than rpm is used for the update. Or if the sysconfig file is backed up and later replaced the change could be reversed. But that's about what I can conceive. No other cases of a "failed update" have become known to me so far. Anyhow, running /usr/share/apache2/apache-20-22-upgrade would fix the installation -- -- unless the sysconfig file has some unique and special feature which prevents the script from successfully doing its job. There is always the chance of a bug, you know. If you still have the file, please attach it here, thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.