Please Matt read my mssage!

Pending credit lookups are particularly bad - that's why they have been "temporarily" disabled.
Going through pages and pages of HTML to parse any information about credit is called stats scraping and is considered much worse than having a dynamic page give you the info directly...

Not only this project but most projects will eventually ban or rate-level your IP if you continuously do stats scraping at your maximum bandwidth. You are seriously bringing the limited resources available to the projects to the very limit of their capacity.

Pending credit lookups are particularly bad - that's why they have been "temporarily" disabled.
Going through pages and pages of HTML to parse any information about credit is called stats scraping and is considered much worse than having a dynamic page give you the info directly...

Not only this project but most projects will eventually ban or rate-level your IP if you continuously do stats scraping at your maximum bandwidth. You are seriously bringing the limited resources available to the projects to the very limit of their capacity.

Janus, I understand very well this.
But, for my problem posted above, now we switch off the script and we need to access the site from that IP.
However, that script was used only from members of our team, and run only 10/20 times a day. Not many brandwith was used and not much resources are used from the server. But the IP was banned. Now can you unblock it?
There are some scripts (posted HERE) for pending credits used from many members that generate a lot of traffic and they are running! Why?

---

GHz
BOINC.Italy

UP!

Matt are you alive? :|

:(

Last up to this topic....next time I will start a nwe one :|

---

GHz
BOINC.Italy

Hey Matt, not positive but i think he is saying the system you blocked is actually a cruncher that was, repeat was, serving stats to some friends. He has now shut down the stats and would like to continue crunching again with this system.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.

adding junk to this thread doesn't help either, just to get it to the "top" of the list, which is dependant on the forum prefs of each user anyway

also pending credit shouldn't be polled that often, it's not going to change that quickly, other puters have got to process and return the work, then the validator had gotta do it's stuff, THEN you might get credit

not much is gonna change in 96 minutes ((24hrs*(60mins/hour)=)1440 minutes per day/(10+20/2=) average of 15 times the site is polled each day)

the reason pending credit was disabled on the site was because it put too much load on the database, and by requesting a php generated page (which relies on the DB) you're just adding to that excessive load again

adding junk to this thread doesn't help either, just to get it to the "top" of the list, which is dependant on the forum prefs of each user anyway

Uhmmm true, I have not think about this...anyway I need to solve this problem :|

also pending credit shouldn't be polled that often, it's not going to change that quickly, other puters have got to process and return the work, then the validator had gotta do it's stuff, THEN you might get credit

not much is gonna change in 96 minutes ((24hrs*(60mins/hour)=)1440 minutes per day/(10+20/2=) average of 15 times the site is polled each day)

the reason pending credit was disabled on the site was because it put too much load on the database, and by requesting a php generated page (which relies on the DB) you're just adding to that excessive load again

I know this, but who polled many time the page to know the pending credits? Not our script! 15/20 times but for different users only of our team, than no to much load on the webserver. Read the post above please! There are other scripts that are used from many members and are working!

But now the problem is, like Steve have writed, it's that one member can't run BOINC because its IP is blocked! I hope that Matt read here and unblock that IP.

Bye,
GHz

But now the problem is, like Steve have writed, it's that one member can't run BOINC because its IP is blocked! I hope that Matt read here and unblock that IP.

Bye,
GHz

Are you sure that Berkeley is blocking the IP?

Have you tried going through a proxy?

What other diagnostics have you tried?

Is there a really good reason that this machine can't be moved to a new IP?

---

Ned, above/below, matt says, "we blocked it, it was hitting our stuff hard" or something to that effect. They stopped the heavy hitting and now that machine can't crunch, or that's how i'm reading this.

Ned, above/below, matt says, "we blocked it, it was hitting our stuff hard" or something to that effect. They stopped the heavy hitting and now that machine can't crunch, or that's how i'm reading this.

There are two "players" here.

The thread was originally about 24.75.104.100.

GHz and Co. is interested in 217.133.4.201.

Matt answered the original question, because 24.75.104.100 was blocked for good reason -- it was hammering the SETI servers.

Blocking an IP is going to be a pretty dramatic step, they're only going to do it under extreme circumstances.

Chances are good that the other problem is elsewhere.

---

But now the problem is, like Steve have writed, it's that one member can't run BOINC because its IP is blocked! I hope that Matt read here and unblock that IP.

Bye,
GHz

Are you sure that Berkeley is blocking the IP?

Have you tried going through a proxy?

What other diagnostics have you tried?

Is there a really good reason that this machine can't be moved to a new IP?

We are not shure 100%, but all is ok in the newtork and only seti is not aviable.

Ping to setiathome.berkeley.edu fail!
Ping to setiboinc.ssl.berkeley.edu it's OK!
Ping to setiboincdata.ssl.berkeley.edu it's OK!

I don't know why he have some problems to contact the scheduler with boinc client, but the webserver is not aviable.

There are two "players" here.

The thread was originally about 24.75.104.100.

GHz and Co. is interested in 217.133.4.201.

Matt answered the original question, because 24.75.104.100 was blocked for good reason -- it was hammering the SETI servers.

Blocking an IP is going to be a pretty dramatic step, they're only going to do it under extreme circumstances.

Chances are good that the other problem is elsewhere.

We want to know if his IP it's in the list of blocked IP (and than unblock it), if not we will investigate elsewhere.

Please Matt...give us some information!

Bye,
GHz

UP :/

UP :/

Hi!

Have you tried using a proxy?

If you dig through the old posts you should find some addresses.
They were posted during the cogent debacle.


Regards Hans

---

Not to hijack his thread, but the cut off date between Cogent and L3 was November 9 wasn't it? what happened? It's still working?

Not to hijack his thread, but the cut off date between Cogent and L3 was November 9 wasn't it? what happened? It's still working?

They had a last second agreement made that kept the link. (I believe it was within 48 hours of the deadline, but I am not quite certain about this).

---

BOINC WIKI

Not to hijack his thread, but the cut off date between Cogent and L3 was November 9 wasn't it? what happened? It's still working?

They had a last second agreement made that kept the link. (I believe it was within 48 hours of the deadline, but I am not quite certain about this).

According to this story from a couple weeks ago they were all happy at the end of October, but I've come across sporadic messages well into November that hinted that there still were a few technical glitches that hadn't ironed themselves out.

UP :/

Hi!

Have you tried using a proxy?

If you dig through the old posts you should find some addresses.
They were posted during the cogent debacle.


Regards Hans

Hi,
yes, using a proxy he can access the website and crunch, but it's not very fast and not always works well.

It's possible to know if it's IP is blocked by berkeley?