date: June 1st 2021 at 14:55 GMT+2

Is there any particular reason for https://mirrors.slackware.com/ refuse connections?

finish with an error:
Ping works.

Can confirm. I see this as well.

Maybe rworkman can provide more info

Same here.
Feels like the world has stopped.

perhaps you mean June 1st

I know, the years going damn fast

ftp works, looks like someone broke apache

/pub directory

Current directory is /pub

Up to /
Mar 9 2013 Directory alien
Jan 11 2011 Directory archive.xfce.org
Nov 26 2017 Directory mirrorbrain
May 23 02:40 Directory misc
May 15 2017 Directory rworkman
Sep 1 2016 Directory sbopkg
Sep 18 2017 Directory slackbuilds.org
May 23 02:41 Directory slackpkg
Mar 11 2018 Directory slackware
Apr 8 22:50 Directory slackwarearm

Thanks, corrected.


even faster.

Until the mirrorbrain service comes back up, you're welcome to use my slack-mirror-speedtest.sh script. It will help you determine the fastest mirror. It does default to the US mirrors, so if you reside in another part of the world, you can replace that list with one from /etc/slackpkg/mirrors to test servers closer to your.

There's also slackware.uk

Robby and rob0 fixed it! \o/

https://mirrors.slackware.com/

thanks for reporting it!

1 members found this post helpful.

So it was down at least 3.5 hours :/

For anyone curious, here's what happened:
httpd-2.4.47 had been reverted in /patches back to 2.4.46, and I'd applied that patch the night before. I *always* give a complete restart to httpd any time I upgrade it (as I've been bitten by similar issues in the past), but well, I guess something distracted me and I did *not* do what I *always* do on this particular occasion. When the logrotate from cron finished, it did "/etc/rc.d/rc.httpd graceful" which failed *hard* due to the running version of httpd not matching the "let's graceful restart this httpd binary" version on the filesystem.

I was notified of this problem at approximately 0930 local time (roughly 1.5 hours after the OP posted here), but all I had was my cell phone (and I don't do "computing" from it). ssh access to mirrors.slackware.com is restricted to only a few known IP addresses and via key only (no passwords accepted at all), and Pat's known IP addresses had changed since we last updated them, so... yeah, fun times. rob0's exact method of access will remain undisclosed, but his services are appreciated :-)

As an aside, I didn't miss the httpd restart on just mirrors.slackware.com though - I missed it on numerous other machines. They don't all do the log rotation at the same time, so the only one that I noticed was harrier.slackbuilds.org when it stopped responding to httpd the night before. At the time, I (incorrectly) assumed that I'd just forgotten that one machine, kicked rc.httpd, and all was (as we would learn later, NOT) well.

Sorry for the trouble...

3 members found this post helpful.