hi,

climateprediction
seti@home
predictor@home
LHC@home

since updating boinc manager to 5.2.13 i got no more
work units from seti, lhc and predictor... climateprediction is running fine

05.01.2006 10:48:53|climateprediction.net|Computer ID: 70753; location: home; project prefs: default
05.01.2006 10:48:53|LHC@home|Computer ID: 94421; location: home; project prefs: default
05.01.2006 10:48:53|Predictor @ Home|Computer ID: 38546; location: home; project prefs: default
05.01.2006 10:48:53|SETI@home|Computer ID: 1404042; location: home; project prefs: default
05.01.2006 10:48:53||General prefs: from climateprediction.net (last modified 2004-11-18 13:20:52)
05.01.2006 10:48:53||General prefs: no separate prefs for home; using your defaults
05.01.2006 10:48:54||Remote control not allowed; using loopback address
05.01.2006 10:49:06|climateprediction.net|Deferring computation for result 1du6_000085257_0
05.01.2006 10:49:06||Resuming computation and network activity
05.01.2006 10:49:06||request_reschedule_cpus: Resuming activities
05.01.2006 10:49:06||Suspending work fetch because computer is overcommitted.
05.01.2006 10:49:06||Using earliest-deadline-first scheduling because computer is overcommitted.
05.01.2006 10:49:06|climateprediction.net|Restarting result 1du6_000085257_0 using hadsm3 version 410
05.01.2006 14:07:39||request_reschedule_cpus: project op
05.01.2006 14:07:41|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
05.01.2006 14:07:41|LHC@home|Reason: Requested by user
05.01.2006 14:07:41|LHC@home|Note: not requesting new work or reporting results
05.01.2006 14:07:41||request_reschedule_cpus: project op
05.01.2006 14:07:42||request_reschedule_cpus: project op
05.01.2006 14:07:44||request_reschedule_cpus: project op
05.01.2006 14:07:45|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
05.01.2006 14:07:50|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
05.01.2006 14:07:50|Predictor @ Home|Reason: Requested by user
05.01.2006 14:07:50|Predictor @ Home|Note: not requesting new work or reporting results
05.01.2006 14:07:56|Predictor @ Home|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
05.01.2006 14:08:01|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
05.01.2006 14:08:01|SETI@home|Reason: Requested by user
05.01.2006 14:08:01|SETI@home|Note: not requesting new work or reporting results


does anyone know what's wrong?

thx, tom

---

snip
05.01.2006 10:49:06||Suspending work fetch because computer is overcommitted.
05.01.2006 10:49:06||Using earliest-deadline-first scheduling because computer is overcommitted
snip

does anyone know what's wrong?

You're overcommitted ;)

The computer thinks you won't finish the work already there in time.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Besides that, LHC has no work, Seti is down and is Preditcor out of their problems yet?

But yeah, you're running the CPDN unit in earliest deadline mode.

---

BOINC 5.2 isn't too good at calculating how long a CPDN unit will take, so it may well have gone into panic mode unnecessarily. But it will sort itself out in the end.

---

I had the same problem for a couple of hours a few days ago. I knew right away that it had gone into EDF mode, but I couldn't quite figure out why since its extimated completion time is months before the deadline.

Anyway, it sorted itself out shortly and all is well now. I assume you had the same issue. For some reason, even though the scheduler USUALLY knows it'll complete well before the deadline, and the scheduler even SAYS it'll complete before the deadline (before, during, and after the "problem") it decides that you won't get it done in time and panics...

That's what we get for running WUs that stretch what the system was designed for I suppose.

---