On Tue, Nov 28, 2000 at 03:12:43PM -0200, Marcus Andree wrote:
> >
> > On Tue, Nov 28, 2000 at 01:31:45PM -0200, Marcus Andree wrote:
> > >
> > > I'm with this odd problem on a Redhat 6.2 Linux system:
> > > after booting the computer, a init script is used to fire up
> > > httpd, but the process starts and then suddenly dies. I've tried a lot
> > > of things to address this issue, but with no success.
> > > It's weird because, after the boot, on a normal bash prompt, I
> > > can type, as root,
> > > path/to/init/script/httpd start
> > > and the server starts with no problem. I've configured the certificate
> > > to hold a private key, so it, on the best of my knowledge, should start
> > > automatically.
> > > I even wrote a small script to start apache, wait 2 seconds, test
> > > if apache is running, and, if not, re-start it again. The result: it was
> > > restarting apache forever.
> > > So, now I'm stuck and, in case of a boot, our www server won't be
> > > online until someone starts it manually.
> > > Any help is welcome.
> >
> >
> > Did you check your /var/log/apache/err* - ?
> >
> Yes. There's nothing abnormal on it. /var/log/messages also
> shows apache starting and nothing when it dies.
>
> > Did you try redirecting stderr and stdout to a file?
> >
> Hmmm. Good idea. I'm using Redhat's normal configuration: starting
> apache with the provided shel function `daemon`. It shown nothing except
> the green "OK" then it loads.
>
> > Did you verify that the path at that init stage matches the path
> > you're using when manually starting?
>
> Yes. I'm 100% sure. Here's another puzzling situation. On a shell,
> I used the `at` programa to schedule a /etc/rc.d/init.d/httpd stop and
> a /etc/rc.d/init.d/httpd start Guess what... it works! This problem is
> driving me crazy... Maybe a workaround (if Murphy is not listening to
> me, of course) would be to schedule a start a couple seconds after the
> boot...
I don't know Redhat very well, so I can only suggest theory here - you
may want to ensure that apache is being started late enough that named
and all relevant network interfaces have been brought up (including
dhcp initialization, if applicable).
Given that you can start apache as different users -
Ensure you haven't edited /etc/apache/* as a user for whom apache may
not have access rights to. If memory serves, this is a silent failure
condition. Also, if memory serves, apache is run as a non-root user
with Redhat.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
