Ping Fails (ns.ripe.net)
In reviewing My Probe stats, it appears that (ns.ripe.net) was once able to ping the server, but now it appears to be failing. All my other ping stats under My Probe show successful pings to other servers, but for some reason ns.ripe.net is failing. Does anybody have a suggestion of what might be going on, since ping is working to all the other servers. -Alby
Hello, This measurement has been discontinued since 2013-07-04, since the machine (and the name) is no longer operational. This message should also show up on the "built-in measurements" section on your probe status page. Regards, Robert On 2013.07.23. 16:11, AlbyVA wrote:
In reviewing My Probe stats, it appears that (ns.ripe.net <http://ns.ripe.net>) was once able to ping the server, but now it appears to be failing. All my other ping stats under My Probe show successful pings to other servers, but for some reason ns.ripe.net <http://ns.ripe.net> is failing. Does anybody have a suggestion of what might be going on, since ping is working to all the other servers.
-Alby
On Tue, Jul 23, 2013 at 04:21:08PM +0200, Robert Kisteleki <robert@ripe.net> wrote a message of 27 lines which said:
the machine (and the name) is no longer operational.
But something still replies: % ping -c3 ns.ripe.net PING ns.ripe.net (193.0.9.6) 56(84) bytes of data. 64 bytes from ns.ripe.net (193.0.9.6): icmp_seq=1 ttl=51 time=45.5 ms 64 bytes from ns.ripe.net (193.0.9.6): icmp_seq=2 ttl=51 time=42.8 ms 64 bytes from ns.ripe.net (193.0.9.6): icmp_seq=3 ttl=51 time=42.1 ms --- ns.ripe.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 42.198/43.541/45.538/1.439 ms % ping6 -c3 ns.ripe.net PING ns.ripe.net(ns.ripe.net) 56 data bytes 64 bytes from ns.ripe.net: icmp_seq=1 ttl=57 time=46.5 ms 64 bytes from ns.ripe.net: icmp_seq=2 ttl=57 time=42.7 ms 64 bytes from ns.ripe.net: icmp_seq=3 ttl=57 time=44.6 ms --- ns.ripe.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 42.793/44.654/46.553/1.535 ms
the probes were pining it using the old ip address 193.0.0.193 which is stopped now. -antony On Tue, Jul 23, 2013 at 04:26:42PM +0200, Stephane Bortzmeyer wrote:
On Tue, Jul 23, 2013 at 04:21:08PM +0200, Robert Kisteleki <robert@ripe.net> wrote a message of 27 lines which said:
the machine (and the name) is no longer operational.
But something still replies:
% ping -c3 ns.ripe.net PING ns.ripe.net (193.0.9.6) 56(84) bytes of data. 64 bytes from ns.ripe.net (193.0.9.6): icmp_seq=1 ttl=51 time=45.5 ms 64 bytes from ns.ripe.net (193.0.9.6): icmp_seq=2 ttl=51 time=42.8 ms 64 bytes from ns.ripe.net (193.0.9.6): icmp_seq=3 ttl=51 time=42.1 ms
--- ns.ripe.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 42.198/43.541/45.538/1.439 ms
% ping6 -c3 ns.ripe.net PING ns.ripe.net(ns.ripe.net) 56 data bytes 64 bytes from ns.ripe.net: icmp_seq=1 ttl=57 time=46.5 ms 64 bytes from ns.ripe.net: icmp_seq=2 ttl=57 time=42.7 ms 64 bytes from ns.ripe.net: icmp_seq=3 ttl=57 time=44.6 ms
--- ns.ripe.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 42.793/44.654/46.553/1.535 ms
Okay. I do see the discontinued note, thanks. I assume just the reporting of pings is no longer being displayed, since a command line ping appears to still work. -Alby On Tue, Jul 23, 2013 at 10:21 AM, Robert Kisteleki <robert@ripe.net> wrote:
Hello,
This measurement has been discontinued since 2013-07-04, since the machine (and the name) is no longer operational. This message should also show up on the "built-in measurements" section on your probe status page.
Regards, Robert
On 2013.07.23. 16:11, AlbyVA wrote:
In reviewing My Probe stats, it appears that (ns.ripe.net <http://ns.ripe.net>) was once able to ping the server, but now it appears to be failing. All my other ping stats under My Probe show successful pings to other servers, but for some reason ns.ripe.net <http://ns.ripe.net> is
failing.
Does anybody have a suggestion of what might be going on, since ping is working to all the other servers.
-Alby
On 2013.07.23. 16:36, AlbyVA wrote:
Okay. I do see the discontinued note, thanks. I assume just the reporting of pings is no longer being displayed, since a command line ping appears to still work.
-Alby
Yes, I should have been a bit more precise. The name (and the service it provides) still exists, but it changed IPs and deployment model (unicast->anycast), so it was better to stop this "built-in" measurement. Regards, Robert
On Tue, Jul 23, 2013 at 10:11:46AM -0400, AlbyVA <albyva@empire.org> wrote a message of 1511 lines which said:
All my other ping stats under My Probe show successful pings to other servers, but for some reason ns.ripe.net is failing. Does anybody have a suggestion of what might be going on, since ping is working to all the other servers.
IPv4 or IPv6 ? May be a wrong ACL in a firewall somewhere? traceroute from the probe may help. I tested with IPv4 on 664 probes and the success rate is 99.4 % which seems to indicate that the problem is on your side.
participants (4)
-
AlbyVA -
Antony Antony -
Robert Kisteleki -
Stephane Bortzmeyer