Lately here have been some posts about AOO "Check for Updates..." showing an error (Checking for an update failed). Normally the second attempt is successful. (Indeed it is *every* second attempt for me)
This reminds me of the recent situation when our homepage was unreachable every second try due to a mis-configured DNS server. Pinging "ooo-updates.apache.org" gives following result for me: First attempt: $ ping ooo-updates.apache.org PING ooo-updates.apache.org (195.154.151.36) 56(84) bytes of data. 64 bytes from tlp-eu-west.apache.org (195.154.151.36): icmp_seq=1 ttl=50 time=28.1 ms 64 bytes from tlp-eu-west.apache.org (195.154.151.36): icmp_seq=2 ttl=50 time=26.4 ms 64 bytes from tlp-eu-west.apache.org (195.154.151.36): icmp_seq=3 ttl=50 time=27.1 ms Second attempt: $ ping ooo-updates.apache.org PING ooo-updates.apache.org (140.211.11.105) 56(84) bytes of data. 64 bytes from themis.apache.org (140.211.11.105): icmp_seq=1 ttl=44 time=184 ms 64 bytes from themis.apache.org (140.211.11.105): icmp_seq=2 ttl=44 time=188 ms 64 bytes from themis.apache.org (140.211.11.105): icmp_seq=3 ttl=44 time=180 ms themis.apache.org has a significant higher response time. AOO seems to time out. Can someone confirm this? If yes, would it be something for Infra? Regards, Matthias
smime.p7s
Description: S/MIME Cryptographic Signature
