It seems to work again now. No idea what happened. Giovanni On 8/28/21 5:31 PM, Kevin A. McGrail wrote: > Did this ever resolve? Perhaps something to ask users@infra about? > > On 8/27/2021 2:57 AM, Giovanni Bechis wrote: >> On Fri, Aug 27, 2021 at 06:18:07AM +0000, [email protected] wrote: >>> Fetching sa-update URLs from >>> http://spamassassin.apache.org/updates/MIRRORED.BY >>> >> [...] >>> http://sa-update-asf.snb.it/ (151.80.178.91): DOWN >>> >> I cannot ping nor connect to my vm from sa-vm but it works from >> somewhere else. >> >> Any idea what's going on ? >> >> root@sa-vm:/home/gbechis# ping sa-update-asf.snb.it >> PING sa-update.snb.it (151.80.178.91) 56(84) bytes of data. >> From 10.110.1.24 (10.110.1.24) icmp_seq=1 Time to live exceeded >> >> root@sa-vm:/home/gbechis# curl -v sa-update-asf.snb.it >> * Trying 151.80.178.91:80... >> * TCP_NODELAY set >> * connect to 151.80.178.91 port 80 failed: No route to host >> * Trying 2001:41d0:12a:d100::91:80... >> * TCP_NODELAY set >> * Immediate connect fail for 2001:41d0:12a:d100::91: Network is unreachable >> * Trying 2001:41d0:12a:d100::91:80... >> * TCP_NODELAY set >> * Immediate connect fail for 2001:41d0:12a:d100::91: Network is unreachable >> * Failed to connect to sa-update-asf.snb.it port 80: No route to host >> * Closing connection 0 >> curl: (7) Failed to connect to sa-update-asf.snb.it port 80: No route to host >
OpenPGP_signature
Description: OpenPGP digital signature
