Re: Server out?

[John E H. <jh...@ti...>]

Ring, John C wrote at 13:03 -0400 on Oct 24, 2006:
 > I'm seeing the UPD packets going out to 66.250.40.33, but I'm not seeing
 > any replies reaching us.  I can ping the server, however.
 > 
 > Running pyzor version 0.4.0.  A sample run:
 > 
 > # pyzor -d check < sample-nonspam.txt
 > calculated digest: 08e7eb05ffb2518788344d88b3b5baa0d23869fa
 > sending: 'User: anonymous\nTime: 1161709316\nSig:
 > 01b23a5a63413759666f8d34d02ea6e327878ab0\n\nOp: check\nOp-Digest:
 > 08e7eb05ffb2518788344d88b3b5baa0d23869fa\nThread: 53149\nPV: 2.0\n\n'
 > 66.250.40.33:24441      TimeoutError:
 > 
 > and I see:
 > 
 > 12:59:22.483447 192.168.5.9.44836 > clapton.quatro.com.pyzor: udp 165
 > (DF)
 > 
 > on the firewall's external interface, but no reply packet is ever
 > received.

I have two servers in my pyzor servers file (see a patch from an
earlier email to this list for running SpamAssassin with multiple
pyzor servers).

82.94.255.100:24441     (200, 'OK')
66.250.40.33:24441      (200, 'OK')

Yes, 66.* mostly times out these days.  82.* mostly works.  However,
it may be loaded less than 66.*.  It definitely appears to be more
loaded recently than earlier this year when Milton unveiled it...
http://www.i-block.com/php/stats.php?host=&span=yearly&refresh=300


pyzor ping ; pyzor ping
82.94.255.100:24441     (200, 'OK')
66.250.40.33:24441      (200, 'OK')
82.94.255.100:24441     (200, 'OK')
66.250.40.33:24441      TimeoutError: