For months now I have been running ok, but the last 2-3 days all my projects (seti, einstein, predictor) have been getting no new modules. All I get is message:

request_reschedule_cpus: exit_tasks
request_reschedule_cpus: project op
schedule_cpus: must schedule
earliest deadline: 1115817561.000000h0005A_1_70763.3

What does this all mean & how do I start getting modules again?

I'm useing WinXP, on a 2.4g, pent-IV.
I am useing BOINC V4.35. Same things happen when I used V4.32

---

I have had the same problem with version 4.37 & the newly released 4.38. Apparently, the scheduling program designed to help us all meet the deadlines given per work unit doesn't work as well for some projects (in my case Protein Predictor) - in fact in got to the point that my machine was requesting the scheduler every second (literally)! The problem got to the point that I wasn't getting any new work units from any project.

As a temporary fix, I unloaded 4.38 and reloaded 4.25 but had the same result. Apparently 4.25 is aware of the scheduler and the cache loaded in 4.37 was still active - and causing the same message and lack of work units!

I finally unloaded 4.25 and installed 4.19 (still available on all sites) - this cured the problem and allowed me to download work units and update all projects (I am running CPDN, SETI, Protein and Einstein). After an hour or so I unloaded 4.19 and reloaded 4.25 - all seems to be working OK at this point with NO scheduler errors / lockups.

I definately prefer v 4.25 to 4.19 due to the features and really liked the added features in 4.38 - but I think I will wait until a little more R&D is done on the development versions before trying them again.

Hope this helps,

Tim Ranch
ID: Farscape

---

Hi Tim
It tends to confirm what others have said about the dev versions on the other boards.

And I have a suspicion that, while 4.25 is OK, (I'm using it without problems), once you upgrade, which takes you to a dev version, if you downgrade again because of problems, something remains which causes 4.25 to 'play up'.

I think that you may be the first to post with a success story.
Hope that others with a similar tale of woe read your post and get their problem cured.

Les

There was a bug that crept in to the dev builds that caused the scheduler to go into a continuous loop. This is due to the new scheduler that is being developped to improve the intelligence of the clients scheduling.

Jamie

> Hi Tim
> It tends to confirm what others have said about the dev versions on the other
> boards.
>
> And I have a suspicion that, while 4.25 is OK, (I'm using it without
> problems), once you upgrade, which takes you to a dev version, if you
> downgrade again because of problems, something remains which causes 4.25 to
> 'play up'.
>
> I think that you may be the first to post with a success story.
> Hope that others with a similar tale of woe read your post and get their
> problem cured.
>
> Les
>
>

---

> There was a bug that crept in to the dev builds that caused the scheduler to
> go into a continuous loop. This is due to the new scheduler that is being
> developped to improve the intelligence of the clients scheduling.
>
Also noticed, on this Version 4.37 My system no longer stops one project & starts another every 2 hours per my account setup. It now takes a project one line at a time til its finished, then moves down one line & starts the next project, no matter if it takes an hour or 24 hours to complete a line. It just don't stop every 2 hours.

---