Menu
▾
▴
Re: TimeOuts remain even after transfer of server?
|
From: Tom A. <to...@ar...> - 2010-06-02 20:22:34
|
I am seeing some timeouts. Here is a sample from a couple of hours ago; Wed Jun 2 10:00:00 CDT 2010 Learned from 24 message(s) (24 message(s) examined). public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 TimeoutError: Wed Jun 2 12:30:07 CDT 2010 Learned from 14 message(s) (15 message(s) examined). public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 TimeoutError: public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') public.pyzor.org:24441 (200, 'OK') Ping times to public.pyzor.org are generally pretty good. Coming from a 1.5meg SDSL line in the US; [root@server root]# pyzor ping public.pyzor.org:24441 (200, 'OK') [root@server root]# ping public.pyzor.org PING public.pyzor.org (79.99.133.40) from 192.168.0.10 : 56(84) bytes of data. 64 bytes from public.pyzor.org (79.99.133.40): icmp_seq=1 ttl=46 time=149 ms 64 bytes from public.pyzor.org (79.99.133.40): icmp_seq=2 ttl=46 time=211 ms 64 bytes from public.pyzor.org (79.99.133.40): icmp_seq=3 ttl=46 time=140 ms 64 bytes from public.pyzor.org (79.99.133.40): icmp_seq=4 ttl=46 time=125 ms --- public.pyzor.org ping statistics --- 4 packets transmitted, 4 received, 0% loss, time 3034ms rtt min/avg/max/mdev = 125.410/156.710/211.353/32.732 ms [root@server root]# traceroute public.pyzor.org traceroute to public.pyzor.org (79.99.133.40), 30 hops max, 38 byte packets 1 fw3 (192.168.0.3) 0.577 ms 0.243 ms 0.275 ms 2 dsl001-128-161.dfw1.dsl.speakeasy.net (72.1.128.161) 1.489 ms 1.278 ms 1.174 ms 3 dsl081-117-001.dfw1.dsl.speakeasy.net (64.81.117.1) 10.893 ms 10.031 ms 13.457 ms 4 220.ge-1-0-0.cr2.dfw1.speakeasy.net (69.17.82.237) 7.949 ms 7.787 ms 8.381 ms 5 ge-6-5-440.car2.Dallas1.Level3.net (4.78.224.1) 9.027 ms 8.324 ms 8.147 ms 6 ae-4-90.edge4.Dallas3.Level3.net (4.69.145.205) 8.767 ms 8.076 ms 8.097 ms 7 te2-2-10G.ar5.dal2.gblx.net (64.208.27.9) 9.313 ms 8.669 ms 16.844 ms 8 tengig-1-2-0.bcr1.ams02.nl.reasonnet.com (64.208.17.206) 123.735 ms 124.897 ms 124.245 ms 9 10ge-1-4-115.bb1-ams.reasonnet.com (213.247.40.6) 123.306 ms 123.867 ms 123.984 ms 10 10ge-1-1-919.edge2-ams.reasonnet.com (89.30.133.58) 123.819 ms 124.112 ms 123.839 ms 11 89-18-191-30.pcextreme.nl (89.18.191.30) 124.741 ms 148.641 ms 132.763 ms 12 public.pyzor.org (79.99.133.40) 127.611 ms 148.694 ms 131.730 ms --- 82.94.255.100 ping statistics --- 5 packets transmitted, 5 received, 0% loss, time 4048ms rtt min/avg/max/mdev = 129.654/132.080/137.294/2.882 ms Andreas Schamanek wrote: > Hi Marc, > > On Wed, 2 Jun 2010, at 15:42, Marc G. Fournier wrote: > > >> What does ping show from both locations? >> > > >From a server in Germany: > > 105 packets transmitted, 105 received, 0% packet loss, time 104414ms > rtt min/avg/max/mdev = 11.779/25.420/168.963/25.277 ms > > >From our Austrian network: > > 100 packets transmitted, 100 received, 0% packet loss, ... > rtt min/avg/max/mdev = 19.947/38.843/155.793/32.543 ms > > >> traceroute? >> > > 6 vlan70.wien1.aco.net (193.171.23.33) 1.684 ms 0.733 ms 1.004 ms > 7 ge-1-49.bb1.vie.reasonnet.com (193.203.0.142) 0.979 ms 1.678 ms 1.655 ms > 8 ge-2-19-556.bb2-ams.reasonnet.com (89.30.133.245) 19.603 ms 19.600 ms 19.683 ms > 9 10ge-1-4-115.bb1-ams.reasonnet.com (213.247.40.6) 30.726 ms 30.715 ms 31.449 ms > 10 10ge-1-1-919.edge2-ams.reasonnet.com (89.30.133.58) 20.722 ms 20.710 ms 20.212 ms > 11 89-18-191-30.pcextreme.nl (89.18.191.30) 20.183 ms 21.222 ms 21.203 ms > > 4 hetzner-gw.noris.net (213.239.242.254) 22.126 ms 3.557 ms 3.492 ms > 5 ge-1-3-0.de-cix.as25525.net (80.81.192.205) 18.593 ms 13.933 ms 12.344 ms > 6 10ge-1-1-919.edge2-ams.reasonnet.com (89.30.133.58) 11.885 ms 11.860 ms 11.789 ms > 7 89-18-191-30.pcextreme.nl (89.18.191.30) 12.466 ms 12.384 ms 12.244 ms > 8 public.pyzor.org (79.99.133.40) [closed] 61.362 ms 12.629 ms 12.498 ms > > >> What sort of command line test(s) did you run aginst the server itself >> > > Basically, I just look at the log for spam reports. This is where I > see the TimeOuts. Then, to verify I just run a bunch of > > $ pyzor ping > > or I feed a spam folder to pyzor report. Don't know if this is of any > any value but here is the core of my bash script which I use to report > if I want some more information (but want to avoid the verbosity > of -d debug): > > #!/bin/bash > # > # Report messages to pyzor > > LOGFILE=~/mypyzorreport.log > echo -n "$(date +%Y%m%dT%H%M%S): " >>$LOGFILE # write a timestamp > > MSG=$(cat -) # put message in a variable > LINES=$(echo "$MSG" | formail -I "" | wc -l) # number of lines of body > echo -n "[$LINES] " >>$LOGFILE > echo "$MSG" | pyzor digest >>$LOGFILE > > TIMEFORMAT=%1R # change format of _time_ > OUTPUT=$( { time echo "$MSG" | pyzor -d report ; } 2>&1 ) > > echo $OUTPUT >>$LOGFILE > > sleep 1 > ### EOF > > > HTH, > > -- Tom Armistead to...@ar... 214-233-5167 http://tom.armisteads.com/ ---- Like my email address? Get one like it at http://hover.com/TArmistead |
