Re: Service restored (was Re: common-lisp.net http stopped running)

Apache itself is rather robust in my experience. I'm suspecting any of the
backend services that could be tying Apache resources as part of the proxy
process.

Are we sure all the backends are timely serving the requested responses?
And that nobody is flooding Apache with requests causing backend contention?

On Wed, Nov 15, 2023, 09:32 Mark Evenson <[email protected]> wrote:

>
>
> > On Nov 15, 2023, at 09:06, Mark Evenson <[email protected]> wrote:
> >
> > The apache2 instance seems to have stopped at 0010 this evening.
>
> Web services for common-lisp.net <http://common-lisp.net/> have been
> restored.
>
>
> > Seems to be something about a bad SSL configuration due to a package
> containing empty certs being deleted
>
> This was a bogus diagnosis.
>
> From what I could make of the logs, the apache2 instance which runs
> all of our user-facing HTTP(S) traffic quit serving shortly after
> midnight UTC.  The cause is unclear.
>
> I had to start/restart apache2 a couple times to clear out resources.
>
>
> --
> "A screaming comes across the sky.  It has happened before but there is
> nothing
> to compare to it now."
>
>
>
>
>
>