pyzor-users

Getting timeouts when running report.

[Robert H. L. <la...@la...>]

For the last few days I have been getting timeouts. (pyzor 0.5.0-r1)

public.pyzor.org:24441  TimeoutError:

$ pyzor ping
public.pyzor.org:24441  TimeoutError:

$ traceroute public.pyzor.org
traceroute to public.pyzor.org (188.40.77.236), 30 hops max, 40 byte packets
  1  gatekeeper.monsoonwind.com (192.168.0.1)  0.219 ms  0.117 ms  1.431 ms
  2  * * *
  3  te-3-3-ur10.sanjose.ca.sfba.comcast.net (68.85.190.157)  15.795 ms 
  15.743 ms  15.676 ms
  4  l-99-ur01.pasadena.tx.houston.comcast.net (68.85.154.141)  18.012 
ms  17.949 ms  17.879 ms
  5  pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.90.141) 
19.656 ms  19.595 ms  19.526 ms
  6  pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.181) 
22.388 ms  23.681 ms  23.594 ms
  7  pos-0-0-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.86.50) 
27.044 ms  20.502 ms  20.399 ms
  8  xe-9-3-0-0.sjc10.ip4.tinet.net (213.200.80.165)  20.151 ms  24.423 
ms  24.352 ms
  9  xe-11-2-0.fra21.ip4.tinet.net (89.149.184.77)  200.830 ms  193.583 
ms xe-10-0-0.fra21.ip4.tinet.net (89.149.184.85)  217.023 ms
10  hetzner-gw.ip4.tinet.net (77.67.64.18)  193.475 ms  198.743 ms 
196.221 ms
11  hos-bb1.juniper2.rz10.hetzner.de (213.239.240.243)  252.173 ms 
255.240 ms  256.551 ms
12  hos-tr3.ex3k5.rz10.hetzner.de (213.239.227.198)  250.604 ms  250.536 
ms  256.263 ms
13  pyzor.spamexperts.com (188.40.77.236)  203.595 ms  191.417 ms 
196.914 ms

-- 
END OF LINE
       --MCP

Re: Getting timeouts when running report.

[Andreas S. <sch...@fa...>]

On Sun, 8 Nov 2009, at 12:39, Robert Hajime Lanning wrote:

> For the last few days I have been getting timeouts. (pyzor 0.5.0-r1)
[...]
> $ pyzor ping
> public.pyzor.org:24441  TimeoutError:

I have to confirm this for my location (128.130.51.99).

Uhm are there issues with DNS?

schamane@doob:~$ cat .pyzor/servers
public.pyzor.org:24441
schamane@doob:~$ host public.pyzor.org
public.pyzor.org has address 188.40.77.236
schamane@doob:~$ host 188.40.77.236
236.77.40.188.in-addr.arpa domain name pointer pyzor.spamexperts.com.
schamane@doob:~$ host pyzor.spamexperts.com.
Host pyzor.spamexperts.com not found: 3(NXDOMAIN)

-- 
-- Andreas

Re: Getting timeouts when running report.

[Dreas v. D. <dr...@sp...>]

Hi guys,

Andreas Schamanek wrote:
> On Sun, 8 Nov 2009, at 12:39, Robert Hajime Lanning wrote:
>
>   
>> For the last few days I have been getting timeouts. (pyzor 0.5.0-r1)
>>     
> [...]
>   
>> $ pyzor ping
>> public.pyzor.org:24441  TimeoutError:
>>     
>
> I have to confirm this for my location (128.130.51.99).
>   
Can you please test again to see if this is resolved now?
> Uhm are there issues with DNS?
>
> schamane@doob:~$ cat .pyzor/servers
> public.pyzor.org:24441
> schamane@doob:~$ host public.pyzor.org
> public.pyzor.org has address 188.40.77.236
> schamane@doob:~$ host 188.40.77.236
> 236.77.40.188.in-addr.arpa domain name pointer pyzor.spamexperts.com.
> schamane@doob:~$ host pyzor.spamexperts.com.
> Host pyzor.spamexperts.com not found: 3(NXDOMAIN)
>   
The A record should be working now. This won't have affected the reporting.

Regards,

Dreas

Re: Getting timeouts when running report.

[Robert H. L. <la...@la...>]

Dreas van Donselaar wrote:
> Hi guys,
> 
> Andreas Schamanek wrote:
>> On Sun, 8 Nov 2009, at 12:39, Robert Hajime Lanning wrote:
>>
>>   
>>> For the last few days I have been getting timeouts. (pyzor 0.5.0-r1)
>>>     
>> [...]
>>   
>>> $ pyzor ping
>>> public.pyzor.org:24441  TimeoutError:
>>>     
>> I have to confirm this for my location (128.130.51.99).
>>   
> Can you please test again to see if this is resolved now?

It now works for me.

Thanks

-- 
END OF LINE
       --MCP

Re: Getting timeouts when running report.

[Andreas S. <sch...@fa...>]

On Sun, 8 Nov 2009, at 22:38, Dreas van Donselaar wrote:

> >> $ pyzor ping
> >> public.pyzor.org:24441  TimeoutError:
> Can you please test again to see if this is resolved now?

Yep. Looks all good.

> > $ host pyzor.spamexperts.com.
> > Host pyzor.spamexperts.com not found: 3(NXDOMAIN)
> The A record should be working now.

It does for me.

Thanks for the prompt fix!

-- 
-- Andreas