ip 194.183.146.189 blocked

hi,

is it possible that our outgoing proxy server is beeing blocked by  
cheeseshop? it's ip address is 194.183.146.189
no, it was no attack to cheeseshop :) we're simply running buildout  
over and over and probably generating some load.

thanks

jodok

--
"Explicit is better than implicit."
   -- The Zen of Python, by Tim Peters

Jodok Batlogg, Lovely Systems
Schmelzhütterstraße 26a, 6850 Dornbirn, Austria
phone: +43 5572 908060, fax: +43 5572 908060-77

_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig

Re: ip 194.183.146.189 blocked

On 7/2/07, Jodok Batlogg <jodok <at> lovelysystems.com> wrote:
> is it possible that our outgoing proxy server is beeing blocked by
> cheeseshop? it's ip address is 194.183.146.189
> no, it was no attack to cheeseshop :) we're simply running buildout
> over and over and probably generating some load.

Hey Jodok,

I've taken to only using an internal repository for project buildouts;
if I need/want a new release from PyPI, I load that into the internal
repository.  That avoids depending on PyPI being accessible at all
times, and I can always get what I've used again.  No need to worry
about someone hiding old releases, or whatever.

It in incurs a little overhead on adding or updating a package used in
my projects, but avoids depending on a highly-variable service.  An
internal repository can still have problems, but at least it's easier
to make changes if needed.

  -Fred

--

-- 
Fred L. Drake, Jr.    <fdrake at gmail.com>
"Chaos is the score upon which reality is written." --Henry Miller

Re: ip 194.183.146.189 blocked

On 02.07.2007, at 23:21, Fred Drake wrote:

> On 7/2/07, Jodok Batlogg <jodok <at> lovelysystems.com> wrote:
>> is it possible that our outgoing proxy server is beeing blocked by
>> cheeseshop? it's ip address is 194.183.146.189
>> no, it was no attack to cheeseshop :) we're simply running buildout
>> over and over and probably generating some load.
>
> Hey Jodok,
>
> I've taken to only using an internal repository for project buildouts;
> if I need/want a new release from PyPI, I load that into the internal
> repository.  That avoids depending on PyPI being accessible at all
> times, and I can always get what I've used again.  No need to worry
> about someone hiding old releases, or whatever.
>
> It in incurs a little overhead on adding or updating a package used in
> my projects, but avoids depending on a highly-variable service.  An
> internal repository can still have problems, but at least it's easier
> to make changes if needed.

already done after pypi beeing flakey :)
unfortunately now the outgoing ip of this repo is beeing blocked and  
it sucks to scp downloaded files :)

thanks fred,

jodok

Re: ip 194.183.146.189 blocked

On Jul 2, 2007, at 3:33 PM, Jodok Batlogg wrote:

> hi,
>
> is it possible that our outgoing proxy server is beeing blocked by  
> cheeseshop? it's ip address is 194.183.146.189
> no, it was no attack to cheeseshop :) we're simply running buildout  
> over and over and probably generating some load.

It's hard to believe that buildout could be generating enough load to  
trigger being blocked.

Jim

--
Jim Fulton			mailto:jim <at> zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org

Re: ip 194.183.146.189 blocked

Could it be that you are simply out of apache's?  i recall that
Sean set the number of simultaneous ones at some very tiny number.

Laura

Re: ip 194.183.146.189 blocked

Laura Creighton schrieb:
> Could it be that you are simply out of apache's?  i recall that
> Sean set the number of simultaneous ones at some very tiny number.

I think you misunderstood. He set MaxRequestsPerChild to 10, which
means that each process will be replaced by a different one after
10 requests. MaxClients is 60, which should be more than enough.

Regards,
Martin

Re: ip 194.183.146.189 blocked

In a message of Tue, 03 Jul 2007 00:29:21 +0200, "Martin v. Löwis" writes:
>Laura Creighton schrieb:
>> Could it be that you are simply out of apache's?  i recall that
>> Sean set the number of simultaneous ones at some very tiny number.
>
>I think you misunderstood. He set MaxRequestsPerChild to 10, which
>means that each process will be replaced by a different one after
>10 requests. MaxClients is 60, which should be more than enough.
>
>Regards,
>Martin

yes, I thought it was 10.  Sorry about that, and thank you.

Laura

Re: ip 194.183.146.189 blocked

> is it possible that our outgoing proxy server is beeing blocked by
> cheeseshop? it's ip address is 194.183.146.189

I can't see anything like that in the configuration of ximinez.

Furthermore, I cannot see that this IP addresses made any attempt
to contact ximinez. I got several accesses from 194.183.146.178,
for various versions of zc.buildout, through setuptools, and
I got requests from 194.183.146.185 through Firefox, but none
from the IP address that you mention. Going back until December
2006 (if I can trust the logs), that machine never made any
access to the Cheeseshop.

Regards,
Martin

Re: ip 194.183.146.189 blocked

On 03.07.2007, at 09:22, Martin v. Löwis wrote:

>> is it possible that our outgoing proxy server is beeing blocked by
>> cheeseshop? it's ip address is 194.183.146.189
>
> I can't see anything like that in the configuration of ximinez.
>
> Furthermore, I cannot see that this IP addresses made any attempt
> to contact ximinez. I got several accesses from 194.183.146.178,
> for various versions of zc.buildout, through setuptools, and
> I got requests from 194.183.146.185 through Firefox, but none
> from the IP address that you mention. Going back until December
> 2006 (if I can trust the logs), that machine never made any
> access to the Cheeseshop.

it seems to happen on the network level. i can't ping the machine  
from this ip address :)

coming from  194.183.146.189:

traceroute to ximinez.python.org (82.94.237.219), 64 hops max, 60  
byte packets
  1  lsfw01 (192.168.34.254)  0.727 ms  0.406 ms  0.345 ms
  2  194-183-146-177.tele.net (194.183.146.177)  1.212 ms  1.061 ms   
3.801 ms
  3  cr4-swz1.net.tele.net (194.183.134.8)  6.733 ms  5.034 ms  4.472 ms
  4  fas0-1-70-cr3-swz1.net.tele.net (194.183.133.188)  4.550 ms   
4.581 ms  4.627 ms
  5  atm0-0-r1-hoe1.net.tele.net (194.183.135.34)  5.743 ms  5.471  
ms  5.362 ms

Cheeseshop login problems?

I can't seem to log in to the Cheeseshop, from any platform or 
machine, whether via script or browser (Firefox or Lynx).  I haven't 
changed my password, but just in case there was an issue with my 
password, I asked for a password reset.

The passwords I received in email don't work either, however, which 
seems to suggest that there is a server problem involved.  :(