Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2018-02-12 Thread David Jones 

On 02/12/2018 02:17 PM, root wrote:

Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY

http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)

http://www.sa-update.pccc.com/ (69.171.29.39): 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): DOWN



This was me doing a quick 2 minute reboot to add more cores and RAM to 
this VM.  Unlucky timing, I guess.  :)




http://sa-update.razx.cloud/ (104.27.152.42): UP (CURRENT)

http://sa-update.razx.cloud/ (104.27.153.42): UP (CURRENT)

http://sa-update.fossies.org/ (138.201.17.217): UP (CURRENT)

http://sa-update.verein-clean.net/ (148.251.212.58): UP (CURRENT)

http://sa-update.verein-clean.net/ (148.251.29.131): 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.bitwell.fi/ (138.201.119.25): UP (CURRENT)

http://sa-update.bitwell.fi/ (185.81.165.102): UP (CURRENT)

http://sa-update.spamassassin.org/ (64.142.56.146): UP (CURRENT)




--
David Jones

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2018-02-23 Thread Dave Warren 
On Fri, Feb 23, 2018, at 10:18, root wrote:
> http://sa-update.razx.cloud/ (104.27.153.42): DOWN

That's m!

Looking like it's resolved, although the service provider hasn't closed of the 
incident report yet: https://status.linode.com/incidents/2088k0rt4rb9

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-03-13 Thread Matthias Leisi 

> Am 14.03.2019 um 05:17 schrieb root :
> 
> Fetching sa-update URLs from 
> http://spamassassin.apache.org/updates/MIRRORED.BY
> 
> http://sa-update.dnswl.org/ (78.47.167.123): DOWN

Interesting, it seems this script is (sometimes?) picking up the A record which 
should have been gone from DNS cache: 

# dig +trace -t a sa-update.dnswl.org 
(…)
sa-update.dnswl.org.21600   IN  A   116.203.4.105

# dig +trace -t soa dnswl.org 
dnswl.org.  21600   IN  SOA zone-ns1.dnswl.org. 
admins.dnswl.org. 1903112142 3600 1200 302400 21600

„1903112142“ is 2019-03-11 21:42 (in CET), ie three days ago. 

I see that the old IP 78.47.167.123 only appeared every few hours (taken from 
the Date: headers in the past few mails):

Date: Thu, 14 Mar 2019 04:17:05 + (UTC)
Date: Wed, 13 Mar 2019 19:18:07 + (UTC)
Date: Wed, 13 Mar 2019 17:18:06 + (UTC)
Date: Wed, 13 Mar 2019 14:17:24 + (UTC)
Date: Wed, 13 Mar 2019 12:17:06 + (UTC)

Is it a DNS issue on sa-vm1, or is it something I overlooked on our end?

— Matthias

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-03-14 Thread Dave Jones 

On 3/14/19 12:40 AM, Matthias Leisi wrote:



Am 14.03.2019 um 05:17 schrieb root :

Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY

http://sa-update.dnswl.org/ (78.47.167.123): DOWN


Interesting, it seems this script is (sometimes?) picking up the A record which 
should have been gone from DNS cache:

# dig +trace -t a sa-update.dnswl.org 
(…)
sa-update.dnswl.org.21600   IN  A   116.203.4.105

# dig +trace -t soa dnswl.org 
dnswl.org.  21600   IN  SOA zone-ns1.dnswl.org. 
admins.dnswl.org. 1903112142 3600 1200 302400 21600

„1903112142“ is 2019-03-11 21:42 (in CET), ie three days ago.

I see that the old IP 78.47.167.123 only appeared every few hours (taken from 
the Date: headers in the past few mails):

Date: Thu, 14 Mar 2019 04:17:05 + (UTC)
Date: Wed, 13 Mar 2019 19:18:07 + (UTC)
Date: Wed, 13 Mar 2019 17:18:06 + (UTC)
Date: Wed, 13 Mar 2019 14:17:24 + (UTC)
Date: Wed, 13 Mar 2019 12:17:06 + (UTC)

Is it a DNS issue on sa-vm1, or is it something I overlooked on our end?

— Matthias




The DNS settings on sa-vm1 are managed by ASF Infra team via Puppet and 
have been set like this for years ever since the server was built new.


sa-vm1:/etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4


Interestingly, if I run digs from the server I see both the old and the 
new IP:


davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
116.203.4.105
davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
78.47.167.123
davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
116.203.4.105
davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
116.203.4.105
davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
116.203.4.105
davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
116.203.4.105
davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
78.47.167.123

But this site shows consistent DNS all around the globe:

https://dnschecker.org/#A/sa-update.dnswl.org

I am only seeing minor DNS hosting issues that shouldn't cause any problems:

https://intodns.com/dnswl.org

- zone-ns3.dnswl.org should be added at the registrar as a name server 
for consistency


- The SOA record values are a bit odd shouldn't cause any problem.

- I would recommend NS record TTLs be 86400 (1 day) and A record TTLs of 
3600 or 7200.  There's no real benefit of going higher on A records and 
it only causes slower propagation of changes.  I see the NS records at 
the .org level are 86400 TTL but the 8 NS records at the child level 
(your DNS servers) have a TTL of 3600.  NS records at this level 
shouldn't change a lot and there is a benefit gained for setting them to 
86400 TTL.  When you plan to change the NS records at the registrar, 
that normally has to replicate around the Internet so a TTL of 86400 is 
OK since you typically would have both the old and new sets of DNS 
servers up at the same time for 2 or 3 days with identical records 
before shutting down or removing the old NS records.


- Any particular reason why the serial isn't in the standard format of 
YYYMMDDnn?  What you have now should be fine.  Just curious.



Compare dnswl.org with these:

https://intodns.com/apache.org

https://intodns.com/spamassassin.org

This problem might clear up at Google's DNS servers in Europe soon. 
Google does some "special logic" to try to fix broken authoritative DNS 
servers that I have seen keep zones and previous records alive on the 
Internet when a bad change is made.  In this case, I am not seeing 
anything that bad wrong and the problem doesn't show up in the US like 
it is in France where sa-vm1 is hosted.


Hope this helps,
Dave

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-03-15 Thread Matthias Leisi 
> The DNS settings on sa-vm1 are managed by ASF Infra team via Puppet and have 
> been set like this for years ever since the server was built new.
> 
> sa-vm1:/etc/resolv.conf
> nameserver 8.8.8.8
> nameserver 8.8.4.4

A side note: if we are running any RBL tests on that machine, 8.8.8.8 & friends 
may not be the best choice.

> 
> Interestingly, if I run digs from the server I see both the old and the new 
> IP:
> 
> davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
> 116.203.4.105
> davej@sa-vm1:~$ dig @8.8.8.8 sa-update.dnswl.org +short
> 78.47.167.123

I flushed DNS cache at Google some 24 hours ago at 
https://developers.google.com/speed/public-dns/cache, and still it seems to 
show stale data. 

> But this site shows consistent DNS all around the globe:
> 
> https://dnschecker.org/#A/sa-update.dnswl.org 
> 

That IP is also not in the zone file any more.

> I am only seeing minor DNS hosting issues that shouldn't cause any problems:
> 
> https://intodns.com/dnswl.org
> 
> - zone-ns3.dnswl.org should be added at the registrar as a name server for 
> consistency

Only the glue was added to the parent, not the NS entry itself. Thanks, fixed.

> - I would recommend NS record TTLs be 86400 (1 day) and A record TTLs of 3600 
> or 7200.

Indeed, that makes sense. Fixed.

> (SOA) - Any particular reason why the serial isn't in the standard format of 
> YYYMMDDnn?  What you have now should be fine.  Just curious.

Yes :) We create the zone from source files and thus need to automatically 
create the SOA serial. And this being in a makefile, having a daily 
incrementing „nn“ is not trivial. That’s why we have

SOASERIAL=`date '+%y%m%d%H%M‘`

> This problem might clear up at Google's DNS servers in Europe soon. Google 
> does some "special logic" to try to fix broken authoritative DNS servers that 
> I have seen keep zones and previous records alive on the Internet when a bad 
> change is made.  In this case, I am not seeing anything that bad wrong and 
> the problem doesn't show up in the US like it is in France where sa-vm1 is 
> hosted.

8.8.8.8 & friends are handled differently for most DNSxL zones, because 
otherwise freeriders will hind behind those resolvers. In our case, they see a 
zone which is slightly different from the rest (basically without NS records 
for the list.dnswl.org  zone). 

# dig txt amiblocked.dnswl.org @8.8.8.8 +short
"yes"
"You are blocked from using list.dnswl.org through public nameservers“

I asked on  https://groups.google.com/group/public-dns-discuss 
 for any further hints.

— Matthias

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-12 Thread Bill Cole 
I've commented out sa-update.verein-clean.net in 
/site/updates/MIRRORED.BY to quiet the notices.


Tobi: Please inform sysadmins@spamassassin.apache.org when/if 
148.251.212.58 is working or no longer in DNS for 
sa-update.verein-clean.net



On 12 Jun 2019, at 11:18, root wrote:

[...]


http://sa-update.verein-clean.net/ (148.251.212.58): DOWN


[...]

--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-12 Thread Kevin A. McGrail 
Should we do that when just 1 of their sub-A records is down?
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Wed, Jun 12, 2019 at 11:59 AM Bill Cole <
sa-bugz-20080...@billmail.scconsult.com> wrote:

> I've commented out sa-update.verein-clean.net in
> /site/updates/MIRRORED.BY to quiet the notices.
>
> Tobi: Please inform sysadmins@spamassassin.apache.org when/if
> 148.251.212.58 is working or no longer in DNS for
> sa-update.verein-clean.net
>
>
> On 12 Jun 2019, at 11:18, root wrote:
>
> [...]
> >
> > http://sa-update.verein-clean.net/ (148.251.212.58): DOWN
> >
> [...]
>
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire
>

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-12 Thread Henrik K 


The embarassing truth is that mirror retry doesn't work in 3.4.2.  So any of
the mirrors not working might delay updates for some people by a day or so. 
Atleast I cron once a night..

I always wondered if we actually need this many mirrors?  10(!!) is quite a
lot.  Anyone can easily churn 5 TB of data with 5 eur/month kimsufi server
or similar, but it would seem more practical maintenance wise to have only
few very well maintained ones (and I mean this also security wise).


On Wed, Jun 12, 2019 at 12:00:23PM -0400, Kevin A. McGrail wrote:
> Should we do that when just 1 of their sub-A records is down?
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> 
> 
> On Wed, Jun 12, 2019 at 11:59 AM Bill Cole <
> sa-bugz-20080...@billmail.scconsult.com> wrote:
> 
> > I've commented out sa-update.verein-clean.net in
> > /site/updates/MIRRORED.BY to quiet the notices.
> >
> > Tobi: Please inform sysadmins@spamassassin.apache.org when/if
> > 148.251.212.58 is working or no longer in DNS for
> > sa-update.verein-clean.net
> >
> >
> > On 12 Jun 2019, at 11:18, root wrote:
> >
> > [...]
> > >
> > > http://sa-update.verein-clean.net/ (148.251.212.58): DOWN
> > >
> > [...]
> >
> > --
> > Bill Cole
> > b...@scconsult.com or billc...@apache.org
> > (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> > Not Currently Available For Hire
> >

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-12 Thread Kevin A. McGrail 
I like having a dozen or so and there is really zero security issue since
the rules are crytographically signed.

I would definitely open a bug if that retry doesn't work.  I didn't know
that.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Wed, Jun 12, 2019 at 12:13 PM Henrik K  wrote:

>
> The embarassing truth is that mirror retry doesn't work in 3.4.2.  So any
> of
> the mirrors not working might delay updates for some people by a day or
> so.
> Atleast I cron once a night..
>
> I always wondered if we actually need this many mirrors?  10(!!) is quite a
> lot.  Anyone can easily churn 5 TB of data with 5 eur/month kimsufi server
> or similar, but it would seem more practical maintenance wise to have only
> few very well maintained ones (and I mean this also security wise).
>
>
> On Wed, Jun 12, 2019 at 12:00:23PM -0400, Kevin A. McGrail wrote:
> > Should we do that when just 1 of their sub-A records is down?
> > --
> > Kevin A. McGrail
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > On Wed, Jun 12, 2019 at 11:59 AM Bill Cole <
> > sa-bugz-20080...@billmail.scconsult.com> wrote:
> >
> > > I've commented out sa-update.verein-clean.net in
> > > /site/updates/MIRRORED.BY to quiet the notices.
> > >
> > > Tobi: Please inform sysadmins@spamassassin.apache.org when/if
> > > 148.251.212.58 is working or no longer in DNS for
> > > sa-update.verein-clean.net
> > >
> > >
> > > On 12 Jun 2019, at 11:18, root wrote:
> > >
> > > [...]
> > > >
> > > > http://sa-update.verein-clean.net/ (148.251.212.58): DOWN
> > > >
> > > [...]
> > >
> > > --
> > > Bill Cole
> > > b...@scconsult.com or billc...@apache.org
> > > (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> > > Not Currently Available For Hire
> > >
>

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-12 Thread Henrik K 


Of course it's fixed already
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7418#c7

PS. I think many do have bad habit of using --no-gpg..

On Wed, Jun 12, 2019 at 12:29:44PM -0400, Kevin A. McGrail wrote:
> I like having a dozen or so and there is really zero security issue since
> the rules are crytographically signed.
> 
> I would definitely open a bug if that retry doesn't work.  I didn't know
> that.
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> 
> 
> On Wed, Jun 12, 2019 at 12:13 PM Henrik K  wrote:
> 
> >
> > The embarassing truth is that mirror retry doesn't work in 3.4.2.  So any
> > of
> > the mirrors not working might delay updates for some people by a day or
> > so.
> > Atleast I cron once a night..
> >
> > I always wondered if we actually need this many mirrors?  10(!!) is quite a
> > lot.  Anyone can easily churn 5 TB of data with 5 eur/month kimsufi server
> > or similar, but it would seem more practical maintenance wise to have only
> > few very well maintained ones (and I mean this also security wise).
> >
> >
> > On Wed, Jun 12, 2019 at 12:00:23PM -0400, Kevin A. McGrail wrote:
> > > Should we do that when just 1 of their sub-A records is down?
> > > --
> > > Kevin A. McGrail
> > > Member, Apache Software Foundation
> > > Chair Emeritus Apache SpamAssassin Project
> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > >
> > >
> > > On Wed, Jun 12, 2019 at 11:59 AM Bill Cole <
> > > sa-bugz-20080...@billmail.scconsult.com> wrote:
> > >
> > > > I've commented out sa-update.verein-clean.net in
> > > > /site/updates/MIRRORED.BY to quiet the notices.
> > > >
> > > > Tobi: Please inform sysadmins@spamassassin.apache.org when/if
> > > > 148.251.212.58 is working or no longer in DNS for
> > > > sa-update.verein-clean.net
> > > >
> > > >
> > > > On 12 Jun 2019, at 11:18, root wrote:
> > > >
> > > > [...]
> > > > >
> > > > > http://sa-update.verein-clean.net/ (148.251.212.58): DOWN
> > > > >
> > > > [...]
> > > >
> > > > --
> > > > Bill Cole
> > > > b...@scconsult.com or billc...@apache.org
> > > > (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> > > > Not Currently Available For Hire
> > > >
> >

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-13 Thread Tobi 
Bill,

148.251.212.58 is up again. httpd did not start after last update
(reboot). Sorry for the noise :-)

tobi

Am 12.06.19 um 17:58 schrieb Bill Cole:
> I've commented out sa-update.verein-clean.net in
> /site/updates/MIRRORED.BY to quiet the notices.
> 
> Tobi: Please inform sysadmins@spamassassin.apache.org when/if
> 148.251.212.58 is working or no longer in DNS for
> sa-update.verein-clean.net
> 
> 
> On 12 Jun 2019, at 11:18, root wrote:
> 
> [...]
>>
>> http://sa-update.verein-clean.net/ (148.251.212.58): DOWN
>>
> [...]
>

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-13 Thread Bill Cole 
On 13 Jun 2019, at 4:12, Tobi wrote:

> Bill,
>
> 148.251.212.58 is up again. httpd did not start after last update
> (reboot). Sorry for the noise :-)

List restored in SVN commit r1861252




>
> tobi
>
> Am 12.06.19 um 17:58 schrieb Bill Cole:
>> I've commented out sa-update.verein-clean.net in
>> /site/updates/MIRRORED.BY to quiet the notices.
>>
>> Tobi: Please inform sysadmins@spamassassin.apache.org when/if
>> 148.251.212.58 is working or no longer in DNS for
>> sa-update.verein-clean.net
>>
>>
>> On 12 Jun 2019, at 11:18, root wrote:
>>
>> [...]
>>>
>>> http://sa-update.verein-clean.net/ (148.251.212.58): DOWN
>>>
>> [...]
>>


-- 
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-17 Thread Kevin A. McGrail 
I did a restart on sa-vm1 but about to hop on a plane.  It was running not
sure why our own mirror is down.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Jun 17, 2019 at 8:17 PM root  wrote:

> 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/ (104.27.153.42): UP (CURRENT)
>
> http://sa-update.razx.cloud/ (104.27.152.42): UP (CURRENT)
>
> http://sa-update.fossies.org/ (138.201.17.217): UP (CURRENT)
>
> http://sa-update.verein-clean.net/ (37.252.124.130): UP (CURRENT)
>
> http://sa-update.verein-clean.net/ (148.251.29.131): UP (CURRENT)
>
> http://sa-update.verein-clean.net/ (37.252.120.157): UP (CURRENT)
>
> http://sa-update.verein-clean.net/ (148.251.212.58): UP (CURRENT)
>
> http://sa-update.bitwell.fi/ (104.31.74.190): UP (CURRENT)
>
> http://sa-update.bitwell.fi/ (104.31.75.190): UP (CURRENT)
>
> http://sa-update.spamassassin.org/ (64.142.56.146): DOWN
>

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-17 Thread Kevin A. McGrail 
CLARIFY: I did a systemctl restart apache2 on sa-vm1.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Jun 17, 2019 at 8:31 PM Kevin A. McGrail 
wrote:

> I did a restart on sa-vm1 but about to hop on a plane.  It was running not
> sure why our own mirror is down.
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
> On Mon, Jun 17, 2019 at 8:17 PM root  wrote:
>
>> 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/ (104.27.153.42): UP (CURRENT)
>>
>> http://sa-update.razx.cloud/ (104.27.152.42): UP (CURRENT)
>>
>> http://sa-update.fossies.org/ (138.201.17.217): UP (CURRENT)
>>
>> http://sa-update.verein-clean.net/ (37.252.124.130): UP (CURRENT)
>>
>> http://sa-update.verein-clean.net/ (148.251.29.131): UP (CURRENT)
>>
>> http://sa-update.verein-clean.net/ (37.252.120.157): UP (CURRENT)
>>
>> http://sa-update.verein-clean.net/ (148.251.212.58): UP (CURRENT)
>>
>> http://sa-update.bitwell.fi/ (104.31.74.190): UP (CURRENT)
>>
>> http://sa-update.bitwell.fi/ (104.31.75.190): UP (CURRENT)
>>
>> http://sa-update.spamassassin.org/ (64.142.56.146): DOWN
>>
>

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-06-18 Thread Bill Cole 

On 17 Jun 2019, at 20:32, Kevin A. McGrail wrote:


CLARIFY: I did a systemctl restart apache2 on sa-vm1.


Yeah, so did I... no effect...

Because:


http://sa-update.spamassassin.org/ (64.142.56.146): DOWN


That's not sa-vm1. That's a machine at Sonic. Not clear who to contact, 
since MIRRORED.BY says:


#CONTACT: sysadmins@spamassassin.apache.org
http://sa-update.spamassassin.org/ weight=10


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)

Re: checkSAupdateMirrors.sh on sa-vm1.apache.org - 1 mirror DOWN, 0 mirrors STALE

2019-11-01 Thread Matthias Leisi 
I sent a heads-up to tobi who runs verein-clean.net servers, but he is 
travelling at the moment.

— Matthias

Von meinem iPhone gesendet

> Am 01.11.2019 um 15:18 schrieb aut...@sa-vm1.apache.org:
> 
> 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.5.1.5): UP (CURRENT)
> 
> http://sa-update.ena.com/ (96.4.1.5): UP (CURRENT)
> 
> http://sa-update.razx.cloud/ (104.27.153.42): UP (CURRENT)
> 
> http://sa-update.razx.cloud/ (104.27.152.42): UP (CURRENT)
> 
> http://sa-update.fossies.org/ (144.76.163.196): UP (CURRENT)
> 
> http://sa-update.verein-clean.net/ (37.252.124.130): UP (CURRENT)
> 
> http://sa-update.verein-clean.net/ (37.252.120.157): UP (CURRENT)
> 
> http://sa-update.verein-clean.net/ (148.251.29.131): UP (CURRENT)
> 
> http://sa-update.verein-clean.net/ (148.251.212.58): DOWN
> 
> http://sa-update.bitwell.fi/ (104.31.75.190): UP (STALE) curl: (22) The 
> requested URL returned error: 503 Service Unavailable
> 
> http://sa-update.bitwell.fi/ (104.31.74.190): UP (STALE) curl: (22) The 
> requested URL returned error: 503 Service Unavailable
> 
> http://sa-update.spamassassin.org/ (64.142.56.146): UP (CURRENT)