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...
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
