Hi Tobi, have you possibly blocked the ASF box that checks it? Dave, cc'd and bcc'd at his work address might have more insight!
Regards, KAM On 9/1/2020 9:52 AM, [email protected] wrote: > Has anyone an idea why one of my servers is considered down? > >> http://sa-update.verein-clean.net/ (148.251.29.131): DOWN > if I login to that box and tail the nginx access log I can see normal > GET requests which are all answered by 200 HTTP codes. In nginx error > log I can only see the normal bots that try all kind of requests, but > nothing legit so far. > > -- > Cheers > > tobi > > > Am 30.08.20 um 12:18 schrieb [email protected]: >> Fetching sa-update URLs from >> http://spamassassin.apache.org/updates/MIRRORED.BY >> >> http://sa-update.dnswl.org/ (116.203.4.105): UP (CURRENT) >> >> http://www.sa-update.pccc.com/ (69.171.29.42): UP (CURRENT) >> >> http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT) >> >> http://sa-update.space-pro.be/ (176.28.55.20): UP (CURRENT) >> >> http://sa-update.ena.com/ (96.4.1.5): UP (CURRENT) >> >> http://sa-update.ena.com/ (96.5.1.5): UP (CURRENT) >> >> http://sa-update.razx.cloud/ (172.67.74.101): UP (CURRENT) >> >> http://sa-update.razx.cloud/ (104.26.2.18): UP (CURRENT) >> >> http://sa-update.razx.cloud/ (104.26.3.18): UP (CURRENT) >> >> http://sa-update.fossies.org/ (144.76.163.196): UP (CURRENT) >> >> http://sa-update.verein-clean.net/ (148.251.212.58): UP (CURRENT) >> >> http://sa-update.verein-clean.net/ (37.252.120.157): UP (CURRENT) >> >> http://sa-update.verein-clean.net/ (37.252.124.130): UP (CURRENT) >> >> http://sa-update.verein-clean.net/ (148.251.29.131): DOWN >> >> http://sa-update.spamassassin.org/ (64.142.56.146): UP (CURRENT) >> -- Kevin A. McGrail [email protected] Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
