Re: common-lisp.net http stopped running

Erik Huelsmann <[email protected]> Wed, 15 Nov 2023 13:55:25 +0100
Newsgroups gmane.lisp.common-lisp-net.devel
Message-ID <CACOoB6iny3rFdN02e4co9+qxCrMoS_wEU+T==jUXa7VJmcgXsQ@mail.gmail.com>
On Wed, Nov 15, 2023, 13:39 Mark Evenson <[email protected]> wrote:

>
>
> > On Nov 15, 2023, at 12:29, Erik Huelsmann <[email protected]> wrote:
> >
> > Unfortunately, this is nothing new and has happened on several occasions
> over the past weeks. I have no idea what could be causing this issue, but
> could it be related to reverse proxying paste.lisp.org which is no longer
> serving pages?
>
> I missed the retirement of paste.lisp.org <http://paste.lisp.org/>:  it
> was running read-only for quite a while.  Was a decision made to shut it
> down permanently?
>

No, that decision made itself: the ever since the bots have been kicked off
Libera, the server has been failing to serve lisppaste as well. The only
thing I did after months of failure (which I did note only in arrears; I
wasn't actively looking at these failures happening), I took the sbcl out
of its misery and just shut it down.


> If paste.lisp.org <http://paste.lisp.org/> will not be running, we should
> return a proper HTTP response.
>

I/we did not get a single reaction over it failing for months. I understand
your point but given the limited availability to work on the maintenance of
the server as it is in combination with the lack of complaints, even on the
regular libera channels *and* nobody to step up even to fix the situation
with the bots, I'm not sure there is enough priority and capacity anywhere
to work on it... So then there is no point?

Things do get lost on the web... Ideally since it was serving read-only
anyway, we transform the content to their read-only pages and host just the
static content. But even that takes time...


> --
> "A screaming comes across the sky.  It has happened before but there is
> nothing
> to compare to it now."
>
>
>
>
>
>