I tried without mod_ssl, and it works.

Logfile:

caught SIGTERM, shutting down

======

The problem is that it does not kill all the children, so httpd does not
restart, - I have to use /...../htppd start to get the server up
running.

I have read allot about this on the mailing lists and what I have seen
is that mod_ssl does not kill all children and on the rereading
httpd.conf it does not terminate.

To be honest - I don't know "where to go today" - nobody want to be
responsible :=(

RH does not even reply

Hoping one day to understand this freedom from OPen Source,

I sign Best Regards,

Aage J. Skjolingstad

 

"Ralf S. Engelschall" wrote:
> 
> On Fri, Mar 30, 2001, Aage J. Skjolingstad wrote:
> 
> > When crond is log rotating (crond.weekly) - httpd feil to start up
> > again. I'm running RH 7.0 with Apache/1.3.14 (Unix) (Red-Hat/Linux)
> > mod_ssl/2.7.1 OpenSSL/0.9.5a mod_perl/1.24
> >
> > The kill HUP does not restart the server since some of the childs does
> > not die
> >
> > The /�../httpd restart command works, and I have done no changes to any
> > of the crond services or conf files.
> >
> > Is this a problem with mod_ssl ??
> 
> Hmmm... I don't think is is mod_ssl related. At least
> I've never heard that mod_ssl caused such problems.
> What does the error logfile say?
>                                        Ralf S. Engelschall
>                                        [EMAIL PROTECTED]
>                                        www.engelschall.com
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
> User Support Mailing List                      [EMAIL PROTECTED]
> Automated List Manager                            [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [EMAIL PROTECTED]
Automated List Manager                            [EMAIL PROTECTED]

Reply via email to