2010/6/1 Juti Noppornpitak <[email protected]>:
> The server is still online. Is the http service down?
>

Yes, it seems the problem is http "only":

steph...@degtyarov:~ $ ping -c4 times.debian.net
PING times.debian.net (82.195.75.85) 56(84) bytes of data.
64 bytes from thallo.turmzimmer.net (82.195.75.85): icmp_req=1 ttl=51
time=53.7 ms
64 bytes from thallo.turmzimmer.net (82.195.75.85): icmp_req=2 ttl=51
time=52.3 ms
64 bytes from thallo.turmzimmer.net (82.195.75.85): icmp_req=3 ttl=51
time=52.1 ms
64 bytes from thallo.turmzimmer.net (82.195.75.85): icmp_req=4 ttl=51
time=52.9 ms

--- times.debian.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 52.125/52.791/53.749/0.691 ms
steph...@degtyarov:~ $ LANG=C; wget http://times.debian.net/
--2010-06-01 00:37:38--  http://times.debian.net/
Resolving times.debian.net... 82.195.75.85
Connecting to times.debian.net|82.195.75.85|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset
by peer) in headers.
Retrying.

--2010-06-01 00:41:51--  (try: 2)  http://times.debian.net/
Connecting to times.debian.net|82.195.75.85|:80... failed: Connection timed out.
Resolving times.debian.net... 82.195.75.85
Connecting to times.debian.net|82.195.75.85|:80... ^C
steph...@degtyarov:~ $ LANG=C; wget http://times.debian.net/?format=rss20.xml
--2010-06-01 00:41:54--  http://times.debian.net/?format=rss20.xml
Resolving times.debian.net... 82.195.75.85
Connecting to times.debian.net|82.195.75.85|:80... failed: Connection timed out.
Retrying.

--2010-06-01 00:42:16--  (try: 2)  http://times.debian.net/?format=rss20.xml
Connecting to times.debian.net|82.195.75.85|:80... failed: Connection timed out.
Retrying.

--2010-06-01 00:42:39--  (try: 3)  http://times.debian.net/?format=rss20.xml
Connecting to times.debian.net|82.195.75.85|:80... connected.
HTTP request sent, awaiting response... ^C


-- 
Stéphane



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to