There's something going on with routing between our server and that mirror.
# curl -m 10 -s -S http://sa-update.secnap.net/
curl: (28) Connection timed out after 10001 milliseconds
I can run the same command from my home Internet and it works fine.
From home:
$ telnet sa-update.secnap.net 80
Trying 204.89.241.6...
Connected to sa-update.secnap.net.
Escape character is '^]'.
^]
Then from the server:
davej@sa-vm1:/tmp# telnet sa-update.secnap.net 80
Trying 204.89.241.6...
telnet: Unable to connect to remote host: Connection timed out
The interesting thing is the /var/log/rsyncd.log shows this sever able
to connect into our server fine.
I guess we are going to have to get a traceroute from the other site and
do some comparisons. We may have a routing problem in one direction.
From my experience, we will need to get some networking gurus involved
to get the right people together to figure this out.
Shall I open a Jira ticket with the Infra team on this?
Dave
On 05/15/2017 11:52 AM, Kevin A. McGrail wrote:
Dave, is sec nap actually down? Checking manually it is answering and the
other script is still running and not flagging either.
Regards,
KAM
On May 15, 2017 12:17:31 PM EDT, [email protected] wrote:
Fetching sa-update URLs from
http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/: UP
http://www.sa-update.pccc.com/: UP
http://sa-update.secnap.net/: DOWN
http://sa-update.space-pro.be/: UP
