Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Epiphany/1.0.4 Description of problem: Cannot integrate subversion into Apache because of an apparent error in the mod_dav_svn-0.32.1-1 package. Starting Apache with mod_dav_svn installed leads to the following errors: Feb 1 16:27:44 gateway httpd: Cannot load /etc/httpd/modules/mod_dav_svn.so into server: /etc/httpd/modules/mod_dav_svn.so: undefined symbol: dav_xml_get_cdata Feb 1 16:27:44 gateway httpd: httpd startup failed Version-Release number of selected component (if applicable): mod_dav_svn-0.32.1-1 How reproducible: Always Steps to Reproduce: 1. yum install mod_dav_svn 2. service httpd start 3. tail /var/log/messages to view errors Actual Results: Apache fails to start because of errors. Expected Results: Apache should run, and include support for subversion. Additional info: httpd-2.0.48-1.2 subversion-0.32.1-1 /etc/httpd/conf/httpd.conf includes: LoadModule dav_module modules/mod_dav.so LoadModule dav_fs_module modules/mod_dav_fs.so /etc/httpd/conf.d/subversion.conf includes: LoadModule dav_svn_module modules/mod_dav_svn.so LoadModule authz_svn_module modules/mod_authz_svn.so
This error should only occur when mod_dav_svn is loaded before mod_dav.so. Can you attach your complete httpd.conf, and check that the Include conf.d/*.conf appears *after* the LoadModule lines?
That fixed the problem. It appears the problem is caused when you upgrade from Red Hat 8.0 to Fedora Core 1, because the Red Hat 8.0 httpd.conf file has the Include directives BEFORE the Loadodule lines.
*** Bug 126191 has been marked as a duplicate of this bug. ***
The same problem when upgrade from RH 9 to FC1.
I got bitten by this one too at some point, but really can't think of an easy way of fixing it without going messing with the existing flat file httpd.conf... which doesn't sound like a bright idea. Or would it be possible to add a few lines to the subversion httpd/conf.d/ file in order to do something like "if the dav module isn't loaded, load it now"? That is, of course, if trying to load it again later doesn't produce an error.
Per Matthias' comment it's really not easy to fix this without automatic munging of httpd.conf, which is not really desirable. It's simply the case that after an upgrade sometimes the config files will need some manual tweaking, unfortunately.