This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: FrontPage Extensions with 1.3.9 Apache? From: "Kevin Hemenway" <info@totalnetnh.net> Date: Wed, 10 Nov 1999 16:53:43 -0500 Ok, I'm sure this has been mentioned in the archives somewhere, but the Redhat List archives seem to be not there, and you can't easily search the ISP-Tech archives. Soo.... I'm attempting to install apache 1.3.9 with frontpage server extensions 2000 with suexec, php, and the raven ssl server. Someone on another list posted their little HOWTO on exactly how to do this, so I figured, hey, what the hell. Anyways, everything went along fine until I started the frontpage extensions install. The last thing I saw of the install program was that it had successfully binded to port 80 and then I got my command prompt. A little paranoid, I checked some pages that we host, and lo and behold, they were done. I discovered that the fp install program had shut it down. No big deal, really wish they had told, but I'll just restart the daemon and off we go. I restart the daemon and I get an error message about the modules being corrupted. Hmm. That's not good. So, I tried to use the old httpd.conf that I had saved. Same message about modules being corrupted. After farting and fuming for another 15 minutes, paranoid that some webhoster was going to call up in a second complaining, I went and uninstalled the apache rpm, reinstalled the rpm and copied the saved .conf files into place, restarting the server. Thankfully, that got the server up again. Now. The question is: what the hell happened? Why would the frontpage extensions cause an error in module loading? Even after commenting out the module that appeared on the command line, I still got error messages (simply with the next listed module, ad infinitum). I had applied the mod_frontpage patch to the apache source tree, and had enabled the frontpage module in the ./configure command line. But, simply, after running the fp_install.sh, it just didn't work, and caused a happy panic when I couldn't "undo" what it somehow did. Any suggestions or help? I'm using Redhat 6.0 with 2.25smp... === Subject: Re: FrontPage Extensions with 1.3.9 Apache? From: Charles Galpin <cgalpin@lighthouse-software.com> Date: Wed, 10 Nov 1999 17:08:19 -0500 (EST) I did this the other day, but didn't patch apache. I don't know what the raven ssl server is either. Not really sure if I can help, but thought I'd at least ask Can you tell us if apache worked with the patches before doing the fp install? I would try that first, you may just find your patched server wasn't built properly, or you need to rebuild the modules too. Also, exactly what error message where you getting, on which modules. As far as I could tell (and you can look at the install script) the install didn't modify any server binaries or modules. charles On Wed, 10 Nov 1999, Kevin Hemenway wrote: > Ok, I'm sure this has been mentioned in the archives somewhere, but the > Redhat List archives seem to be not there, and you can't easily search the > ISP-Tech archives. Soo.... > > I'm attempting to install apache 1.3.9 with frontpage server extensions 2000 > with suexec, php, and the raven ssl server. Someone on another list posted > their little HOWTO on exactly how to do this, so I figured, hey, what the > hell. > > Anyways, everything went along fine until I started the frontpage extensions > install. The last thing I saw of the install program was that it had > successfully binded to port 80 and then I got my command prompt. A little > paranoid, I checked some pages that we host, and lo and behold, they were > done. > > I discovered that the fp install program had shut it down. No big deal, > really wish they had told, but I'll just restart the daemon and off we go. > > I restart the daemon and I get an error message about the modules being > corrupted. Hmm. That's not good. So, I tried to use the old httpd.conf that > I had saved. Same message about modules being corrupted. > > After farting and fuming for another 15 minutes, paranoid that some > webhoster was going to call up in a second complaining, I went and > uninstalled the apache rpm, reinstalled the rpm and copied the saved .conf > files into place, restarting the server. > > Thankfully, that got the server up again. > > Now. The question is: what the hell happened? Why would the frontpage > extensions cause an error in module loading? Even after commenting out the > module that appeared on the command line, I still got error messages (simply > with the next listed module, ad infinitum). > > I had applied the mod_frontpage patch to the apache source tree, and had > enabled the frontpage module in the ./configure command line. But, simply, > after running the fp_install.sh, it just didn't work, and caused a happy > panic when I couldn't "undo" what it somehow did. > > Any suggestions or help? I'm using Redhat 6.0 with 2.25smp... === Subject: Re: FrontPage Extensions with 1.3.9 Apache? From: "Kevin Hemenway" <info@totalnetnh.net> Date: Wed, 10 Nov 1999 17:39:02 -0500 > I did this the other day, but didn't patch apache. I don't know what the > raven ssl server is either. Not really sure if I can help, but thought I'd > at least ask The Raven is simply another module which adds SSL support to the server. It duplicates (at least, the idea) of SSLeay and some of the other secure server solutions. > Can you tell us if apache worked with the patches before doing the fp > install? I would try that first, you may just find your patched server > wasn't built properly, or you need to rebuild the modules too. Yeah, we didn't try to see if it worked when we applied the patch and then installed. We'll be trying it again in another couple of days as we get more information and do our own research. > Also, exactly what error message where you getting, on which modules. "API module structure `vhost_alias_module' in file /usr/lib/apache/mod_vhost_alias.so is garbled - perhaps this is not an Apache module DSO?" This would happen on any module. If you commented out the vhost, it would move on to the second module with the same error message. If you commented that, it would err on the third one and so forth. > As far as I could tell (and you can look at the install script) the > install didn't modify any server binaries or modules. I noticed that as well. === Subject: Re: FrontPage Extensions with 1.3.9 Apache? From: Charles Galpin <cgalpin@lighthouse-software.com> Date: Wed, 10 Nov 1999 21:06:43 -0500 (EST) You have a version mismatch between your devel libs and the apache I assume. The module interfaces don't match. Make sure you are using the same version across the board when you recompile. hth charles On Wed, 10 Nov 1999, Kevin Hemenway wrote: > > "API module structure `vhost_alias_module' in file > /usr/lib/apache/mod_vhost_alias.so is garbled - perhaps this is not an > Apache module DSO?" > > This would happen on any module. If you commented out the vhost, it would > move on to the second module with the same error message. If you commented > that, it would err on the third one and so forth. === Subject: FP 2000 Extensions and Apache Virtual Domains From: "Kevin Hemenway" <info@totalnetnh.net> Date: Thu, 11 Nov 1999 09:56:48 -0500 Ok, this stupid frontpage thing is a trying experience for me. Following the instructions given from another email and another list, I attempted to install the frontpage 2000 extensions onto my apache 1.3.9 server on RH 6.0. To my happy surprise, I screwed up, it changed the permissions of my /home/httpd/html directory to nobody:nobody and added a _vti_cnf/ directory to every folder and subfolder. So, I decided to read instructions. Sigh. Ok. This is my question: I'm running virtual domains with apache 1.3.9. The frontpage extensions are successfully uncompressed into /usr/local/frontpage. Now, since I don't want my root web to be /home/httpd/html/ but rather a subdomain underneath it, should I totally SKIP the fp_install.sh that they have in there and simply add new virtdomains with a command line like: fpsrvadm -o install -t apache-fp -s /usr/local/apache/conf/httpd.conf -p 80 -m sample.microsoft.com -u adminaccount -p adminpassword -xu www -xg www ?? My concern is that since I've "undone" the nobody:nobody and the _vti_cnf underneath each of the folders and subfolders in /home/httpd/html that the extensions weren't really "installed" and thus, running the above command line will prove futile. Help is appreciated (else, I wouldn't post)... I don't want to do this stuff, but it's becoming a marketing ploy for people who "use Frontpage"... ===