Sounds like a file permissions problem to me. Probably on a directory that it
accesses. What user is it running as? and does that user have access to all
the necessary file?
On Mon, 12 Apr 1999, Robert Giles wrote:
>I have mod_ssl working great on another of my Linux machines - a slack
>3.4-3.6 based system running 2.2.5 kernel, Apache 1.3.6/mod_ssl-2.2.7-1.3.6,
>openssl-0.9.2b. gcc 2.7.2.3. P55C 166MHz CPU.
>
>I can't seem to get the damn thing to work on another box, though. All
>software is identical except the base distribution, slack 4.0. CPU is a
>Celeron 400A. If I use a Thawte-signed certificate, it sigsegvs on startup.
>I can get it to stay in memory with a self-signed cert generated on-system,
>but when connecting to the daemon the child processes all die off with
>each https request - this is recorded in the error_log and quite evident with
>a ps aux.
>
>I've even tried copying the openssl libs and httpsd binary from the
>machine that works without luck.
>
>I've been all over dejanews and Engelschall's site looking for answers -
>have even e-mailed the guy, and he doesn't know what to say.
>
>Was thinking that perhaps it was a problem with the main memory... but
>all other software works fine on the machine (ie: bind-8.2, apache/fp,
>etc.).
>
>The openssl "make test" also reports no problems with the SSL stuff.
>
>Anyone?
>
>TIA
>
> . .... _ _ _
> / / / Robert Giles
>/_/ / [EMAIL PROTECTED]
>_____________________________________________ _ _ _ _ _ ____
>. . . . The University of Texas at Austin . . . . . . . . .
>---------------------------------------------------------------------------
>Send administrative requests to [EMAIL PROTECTED]
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
