...
There is a script at ~cottrell/bin/tulip-analyze-log.pl to aggregate analyse the errorslogs. Typical output appears as:
Code Block |
---|
28cottrell@wanmon:~>bin/tulip-log-analyze.pl tulip-log-analyze.pl: Mon Sep 3 22:16:47 2007=1188883007 100%_loss,128.111.52.61=1 100%_loss,128.227.56.81=4 100%_loss,129.22.150.90=4 100%_loss,129.24.211.25=5 100%_loss,131.247.2.242=1 100%_loss,141.149.218.208=3 100%_loss,152.14.92.58=1 100%_loss,155.225.2.72=4 100%_loss,205.189.33.178=1 100%_loss,206.207.248.34=2 100%_loss,208.117.131.115=2 100%_loss,63.64.153.84=1 100%_loss,65.241.38.58=3 100%_loss,75.130.96.12=4 failed_to_connect,128.192.101.217=5 failed_to_connect,128.238.88.64=5 failed_to_connect,128.6.192.158=5 failed_to_connect,129.105.44.252=5 failed_to_connect,141.149.218.208=2 failed_to_connect,143.215.129.115=5 failed_to_connect,169.229.50.16=5 failed_to_connect,192.197.121.3=5 failed_to_connect,208.216.119.19=2 failed_to_connect,216.165.109.81=1 not_sent,128.4.36.11=1 timeout,128.143.137.250=1 timeout,128.4.36.11=1 timeout,129.130.252.138=1 timeout,155.225.2.72=1 timeout,64.151.112.20=1 timeout,65.241.38.58=1 Mon Sep 3 22:16:47===============Failure types by landmark ======================= Landmark, Success, 100%_loss,connect_fail, not_sent, timeout, refused, in_use, no_name, transit_exc, Totals, 143.225.229.236, 100.0%, 0.0%, 0.0%, 0.0%, 0.0%, 0.0%, 0.0%, 0.0%, 0.0% 1, 149.48.230.20, 40.0%, 37.8%, 2.2%, 0.0%, 11.1%, 0.0%, 0.0%, 8.9%, 0.0% 45,... itchy.cs.uga.edu_PL, 0.0%, 15.4%, 84.6%, 0.0%, 0.0%, 0.0%, 0.0%, 0.0%, 0.0% 26, Landmark, Success, 100%_loss,connect_fail, not_sent, timeout, refused, in_use, no_name, transit_exc, Totals, Totals, 2258, 422, 457, 11, 401, 0, 52, 287, 0, 3888 Wed Oct 3 14:58:38 2007 tulip-log-analyze.pl: took 0 seconds38 seconds to analyze 4378 records for 323 requests. Successful hosts=111, Failing hosts=108, PlanetLabs=128(100% success=26), SLACs=16(100% success=10) |
As we review the logs we will determine whether probing from some landmarks is reliable enough to warrant their use.
...