You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Justin Mason (JIRA)" <ji...@apache.org> on 2005/09/26 20:17:47 UTC
[jira] Resolved: (INFRA-565) helios appears to be down/borked; no SSH
[ http://issues.apache.org/jira/browse/INFRA-565?page=all ]
Justin Mason resolved INFRA-565:
--------------------------------
Resolution: Fixed
From: Mads Toftum <ma...@toftum.dk>
Date: Mon, 26 Sep 2005 19:59:26 +0200
Yes, this is planned maintenance as announced on the infra list
previously - when complaining about zones, please start by checking
helios.apache.org ...
The single user mode patching takes forever with zones, so I'm
suspecting it could go on for another 30 - 60 minutes, running a bit
over the original planned time.
> helios appears to be down/borked; no SSH
> ----------------------------------------
>
> Key: INFRA-565
> URL: http://issues.apache.org/jira/browse/INFRA-565
> Project: Infrastructure
> Type: Bug
> Components: Zones
> Reporter: Justin Mason
>
> : jm 3...; ping spamassassin.zones.apache.org
> PING spamassassin.zones.apache.org (207.7.158.200) 56(84) bytes of data.
> 64 bytes from 207.7.158.200: icmp_seq=47 ttl=238 time=19.8 ms
> 64 bytes from 207.7.158.200: icmp_seq=48 ttl=238 time=20.9 ms
> 64 bytes from 207.7.158.200: icmp_seq=49 ttl=238 time=21.6 ms
> 64 bytes from 207.7.158.200: icmp_seq=50 ttl=238 time=22.2 ms
> 64 bytes from 207.7.158.200: icmp_seq=240 ttl=238 time=24.1 ms
> 64 bytes from 207.7.158.200: icmp_seq=241 ttl=238 time=21.3 ms
> 64 bytes from 207.7.158.200: icmp_seq=242 ttl=238 time=20.6 ms
> 64 bytes from 207.7.158.200: icmp_seq=243 ttl=238 time=22.7 ms
> 64 bytes from 207.7.158.200: icmp_seq=244 ttl=238 time=20.1 ms
> 64 bytes from 207.7.158.200: icmp_seq=245 ttl=238 time=25.8 ms
> 64 bytes from 207.7.158.200: icmp_seq=246 ttl=238 time=20.4 ms
> 64 bytes from 207.7.158.200: icmp_seq=247 ttl=238 time=36.7 ms
> 64 bytes from 207.7.158.200: icmp_seq=248 ttl=238 time=25.3 ms
> 64 bytes from 207.7.158.200: icmp_seq=249 ttl=238 time=22.3 ms
> 64 bytes from 207.7.158.200: icmp_seq=250 ttl=238 time=36.3 ms
> 64 bytes from 207.7.158.200: icmp_seq=251 ttl=238 time=20.3 ms
> 64 bytes from 207.7.158.200: icmp_seq=252 ttl=238 time=22.7 ms
> 64 bytes from 207.7.158.200: icmp_seq=253 ttl=238 time=26.6 ms
> 64 bytes from 207.7.158.200: icmp_seq=254 ttl=238 time=19.9 ms
> 64 bytes from 207.7.158.200: icmp_seq=255 ttl=238 time=21.2 ms
> --- spamassassin.zones.apache.org ping statistics ---
> 424 packets transmitted, 20 received, 95% packet loss, time 423506ms
> rtt min/avg/max/mdev = 19.892/23.604/36.724/4.729 ms
> similar results from minotaur and my home machine, so it's not a local network issue. it's un-SSH-able, too.
> aha -- looking at http://monitoring.apache.org/status/ , I see helios is marked as CRITICAL / down. that could be it ;)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira