http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

I can't connect at all.

---

My computer has been trying to send results since 01:14 UTC with no luck. tracert 66.28.250.125 is OK so assume it must be Berkeley.

Andy

Seems there is some problem. 2 uploads waiting to retry, 1 download.
Neither will 'resume'.
According to http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html , traffic has dropped to a fraction over past 2-3 hours.

Well, it's a week-end, what did we expect?

At least I have a 7 day cache ;)

---

Seems there is some problem. 2 uploads waiting to retry, 1 download.
Neither will 'resume'.
According to http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html , traffic has dropped to a fraction over past 2-3 hours.

Well, it's a week-end, what did we expect?

At least I have a 7 day cache ;)

Shoot! This is not good. All my units are processed and I have nothing to process.

Just in case this happens again how do I increase my SETI's cache? I hate to see all this unused CPU power going to waste.

---

Seems there is some problem. 2 uploads waiting to retry, 1 download.
Neither will 'resume'.
According to http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html , traffic has dropped to a fraction over past 2-3 hours.

Well, it's a week-end, what did we expect?

At least I have a 7 day cache ;)

SNAFU

Am I right in assuming times on inr-668 are local times in berkeley and that equates to 01:00 here in the UK

Andy

Seems there is some problem. 2 uploads waiting to retry, 1 download.
Neither will 'resume'.
According to http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html , traffic has dropped to a fraction over past 2-3 hours.

Well, it's a week-end, what did we expect?

At least I have a 7 day cache ;)

SNAFU

Am I right in assuming times on inr-668 are local times in berkeley and that equates to 01:00 here in the UK

Andy

I believe that they are in local time, and there is an 8 hour difference between California and England (except right around the time change as they change on different days).

---

BOINC WIKI

Even in California we can't connect.

6/3/2005 7:33:29 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/3/2005 7:33:29 PM|SETI@home|No schedulers responded

---

me@rescam.org

Well I can 'ping' setiboinc.ssl.berkeley.edu , so it isn't Cogent's problem.

Must be a router internal to SSL.


Oophs, senior moment, not a router, but the server program is probabily spinning its wheels.

---

Seems there is some problem. 2 uploads waiting to retry, 1 download.
Neither will 'resume'.
According to http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html , traffic has dropped to a fraction over past 2-3 hours.

Well, it's a week-end, what did we expect?

At least I have a 7 day cache ;)

Shoot! This is not good. All my units are processed and I have nothing to process.

Just in case this happens again how do I increase my SETI's cache? I hate to see all this unused CPU power going to waste.

Too bad you can't increase your cache without the scheduler screwing things up. It'll probably run any project dry before its over and ban you from downloading anything else.

---

Well I can 'ping' setiboinc.ssl.berkeley.edu , so it isn't Cogent's problem.

Must be a router internal to SSL.


Oophs, senior moment, not a router, but the server program is probabily spinning its wheels.

Well, it IS the weekend....

---

Thats Right, This Is The Weekend. People Wonder Why I Like To Keep A 9 Day Cache (Which I Crunch In 6 Days).

---

Weekend or not, it is frustrating.

My Windoze boxes have enough work to get thru the down times (5 day cache), but I just got one of my IRIX machines all configured, and now it can't get any work.

well i burned thru my cache and thanks to debt issues i have nothing to do, can not download work from any other project attached to... if this keeps up to long i will uninstall and go back to a previous version of BOINC.

---

Wiki de BOINC

<img src="http://www.boincstats.com/stats/banner.php?cpid=51a3eaaef8df276544f56140a8a65413">

well i burned thru my cache and thanks to debt issues i have nothing to do, can not download work from any other project attached to... if this keeps up to long i will uninstall and go back to a previous version of BOINC.

You must have bought into the "0.1 day cache is the only choice for the new scheduler" advise... too bad.

---

if i set it higher (1 day, 2 day,3 day, 5 day, 10 day, anything but .1) it will go into panic mode and not download anything from SETI at all.

well i burned thru my cache and thanks to debt issues i have nothing to do, can not download work from any other project attached to... if this keeps up to long i will uninstall and go back to a previous version of BOINC.

You must have bought into the "0.1 day cache is the only choice for the new scheduler" advise... too bad.

if i set it higher (1 day, 2 day,3 day, 5 day, 10 day, anything but .1) it will go into panic mode and not download anything from SETI at all.

well i burned thru my cache and thanks to debt issues i have nothing to do, can not download work from any other project attached to... if this keeps up to long i will uninstall and go back to a previous version of BOINC.

You must have bought into the "0.1 day cache is the only choice for the new scheduler" advise... too bad.

Well, I guess you have experienced the drawbacks of the new scheduler, first-hand.

---

if i set it higher (1 day, 2 day,3 day, 5 day, 10 day, anything but .1) it will go into panic mode and not download anything from SETI at all.

well i burned thru my cache and thanks to debt issues i have nothing to do, can not download work from any other project attached to... if this keeps up to long i will uninstall and go back to a previous version of BOINC.

You must have bought into the "0.1 day cache is the only choice for the new scheduler" advise... too bad.

Well, I guess you have experienced the drawbacks of the new scheduler, first-hand.

I am using 4.43 and with Seti and CPDN on the same machine (P4 HT), with them at 50/50 and network connect time of 5 days. It usually is running one seti unit and one CPDN unit at the same time.

If you are not on CPDN, it is a good one to have as a backup as the expiry date on units is a year.

www.climateprediction.net

will run out of work in 2 hours...
Those guys wont fix it until Monday,will they?

---

http://www.cyclistlog.com/

The same situation in Malaysia. Could report and download some this morning but now it looks like the line is cut again!

---

Happy crunching

Thank god, LHC and ProteinPredictor are giving out WU's again ;)
Enjoy the weekend!

---

Aloha, Uli