FYI, this is why there have been no new postings today: ----- Forwarded message from Greg Newby <gbnewby@pglaf.org> ----- Date: Mon, 21 Dec 2020 21:01:55 -0800 From: Greg Newby <gbnewby@pglaf.org> To: pgww@lists.pglaf.org Subject: Re: Please defer 'pushes' Update: I'm sorry to say that aleph.pglaf.org still isn't recovered. If it's not back by morning (Pacific time, where the system is located), I'll remove aleph from the quorum so we can begin pushing again. Until then, pushed files *will* go to ibiblio and hence to www.gutenberg.org, but they will also generate hourly "pushed failure" messages in your inbox (as long as they are in the ../push/ folder). Sorry for this trouble. I think the colo center fixed the problem that took all our systems off the network, and didn't realize aleph had a separate issue. I've emailed them about it again (fourth time today, and four phone calls). - Greg On Mon, Dec 21, 2020 at 01:56:55PM -0800, Greg Newby wrote:
Update: Please continue to defer pushes. The aleph system is still not online.
Coincidentally, perhaps, there was a network outage for all the pglaf.org servers. It lasted around 4 hours, mid-day today (Pacific time). The main pglaf.org server is back, and so is our big mirror and backup server, dante.pglaf.org
But aleph.pglaf.org is still offline... - Greg
On Mon, Dec 21, 2020 at 09:11:41AM -0800, Greg Newby wrote:
Hi, folks. I did an upgrade to aleph.pglaf.org, which is one of our three "master" servers. Unfortunately it did not return from the upgrade properly, and I cannot access it to fix it.
I've asked our hosting company in San Diego to fix things.
Until it's fixed, pushes will fail (files will go to ibiblio, though, so will get posted as usual).
Any files you push will re-try every hour until aleph is back. You'll get a push failure error for every file in the queue, indicating the file did not go to aleph.pglaf.org.
So, you might want to hold onto your pushes files until aleph is fixed. I'll keep you informed of status. - Greg
----- End forwarded message -----