why are both of my crunchers not requesting more work even after sending results back?
anyone else seeing this behaveure and is a problem with the schedueler

---

what other messages
computer over committed?
other project with ltd?
need more info

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

7/2/2005 7:59:22 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
7/2/2005 7:59:22 AM|SETI@home|Requesting 0 seconds of work, returning 0 results
7/2/2005 7:59:28 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
7/2/2005 8:00:52 AM||May run out of work in 5.00 days; requesting more

havent gotten new work sence yesterday

---

We still need more info, James.
Like:
- Do you share with other projects, if so which ones?
- Which version of Boinc are you using and since when?

---

How much work in is your queue? What's the estimated time to completion for each. What's the LTD numbers for each project. would help also.

was sharing with climate pridictor but now detached because it was behaving badly the time keeps running even while prempted, now that I've detached the project my machines are getting new work as they should.
I'm running BOINC 4.45 with SAH 4.18 sence june 25 on a PII 500 laptop with win ME,and PII 400 with win 98 both were fine till after climate pridictor loaded and cycled once.
now all is well once more.
which other projects behave well sharing?

---

WinME and Win 98 use a Wall clock. Einstien will behave exactly the same as CPDN. If you go to your 'General' preference and say "no" to the question "leave application in memeory while preempted" that should fix it.

tony

[edit] you will also need to have your client contact the site you used to change the preference for it be be accepted by your client. It might take some time, but it will change. Watch your message for an "updated preference" message.

tried it both ways and same results the time kept running, and yes after changing the setting I updated the project so the setting would go into effect.

---

Advice to the helpers, for those who first ask around here, don't throw Boinc acronyms at them without explaining what they are or where exactly to find them.

LTD is nothing to people, if you don't explain what it is.
Long Term Debt is nothing to people, if you don't explain where to find it.

Before everyone starts of with the STD, LTD, XML, EDF, etc.
I know, it's not easy. But it helps if we explain to people with less than 200 posts what they are looking at.

---

tried it both ways and same results the time kept running, and yes after changing the setting I updated the project so the setting would go into effect.

did you see the lines in the "messages" page that indicated that the new prefs were in effect? Sometimes an updated alone (or just once) doesn't do it.

After looking through this post I feel the need to express one idea and that is, because he is running rather low end boxes he will always have problems with CPDN and Einstein.
If I remember CPDN does not support ME 98 or NT and MHz is the lowest they recommend for CPDN.
Einstein seems like it will always be in a panic mode and it will be hard for it to download any other project, especially if the connect to, is set over 3, I could wrong but I do not think so.....

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Thanks for the advise I might try CPDN again when I bring my AMD 2800+ online it's got XP on it and with the faster CPU should be able to handle it.
hopefully it will behave better on XP than ME, or 98.

---

turns out Head Troll is right CPDN inn't compatable with 98 or ME.
maybe someday they will fix that

---

Got same problem with SETI@Home, only sharing with orbit@home(none WU yet)

7/2/2005 11:41:29 PM||request_reschedule_cpus: project op
7/2/2005 11:41:30 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
7/2/2005 11:41:30 PM|SETI@home|Requesting 0 seconds of work, returning 2 results
7/2/2005 11:41:31 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
7/2/2005 11:42:07 PM||request_reschedule_cpus: project op
7/2/2005 11:42:08 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
7/2/2005 11:42:08 PM|SETI@home|Requesting 0 seconds of work, returning 0 results
7/2/2005 11:42:09 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

help! I only got 2 WU!!!

---

help! I only got 2 WU!!!

Suspend Orbit@home, they won't be issuing WUs until late this month (linux) or August (windows) at the earliest. report what happens. Also give "connect to setting".

tony

why are both of my crunchers not requesting more work even after sending results back?
anyone else seeing this behaveure and is a problem with the schedueler

Same started for me around 17:00 CDT.... low end machine, only Seti, no other projects.
Usually has one WU running, one ready to run. Same messges have repeated each time it tries an update. Current WU seems to be progessing normally, just not any on deck for when this one finishes.

Sun Jul 3 07:55:33 request_reschedule_cpus: project op
Sun Jul 3 07:55:33 Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
Sun Jul 3 07:55:33 Requesting 0 seconds of work, returning 0 results
Sun Jul 3 07:55:34 Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

turns out Head Troll is right CPDN inn't compatable with 98 or ME.
maybe someday they will fix that

They probably won't fix that, being as Windows 9x is no longer supported by Microsoft or commercial developers, and as such people have stopped coding for Win9x.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=567" />
<a href="http://boinc-doc.net/boinc-wiki/index.php?title=Main_Page">BOINC Wiki</a>
<a href="http://www.tamaness.hostrocket.com/BOINC_team.html">Gideontech BOINC team!</a>

help! I only got 2 WU!!!

Suspend Orbit@home, they won't be issuing WUs until late this month (linux) or August (windows) at the earliest. report what happens. Also give "connect to setting".

tony

Ddint work it said that the RPC (or something like that) too recent - X sec.

So i just added the LHC@Home, to get My PC busy last night, and it the morning it worked out... weird huh?

---

Anyone else seeing this problem? Since last night I have been crunching and uploading as normal, but as yet no new work has been downloaded.

Running Seti and Seti Beta (was 5%, now suspended)

Log shows "May run out of work in 10 days, requesting more", followed by "requesting 0 seconds of work, returning x units) x has been 1 or 0 today. I'm down to only 2 WU's to process, which should take about 3 hours.

Nothing has changed at my end regards firewall/proxy/network etc, and apart from not getting any work everything else seems to be running fine.

Occasionally getting "computer is overcommitted" message, but it's not really (the 10 days cache is usually about 30 hours worth of work)

---

Anyone else seeing this problem? Since last night I have been crunching and ploading as normal, but as yet no new work has been downloaded.

To update my post above, the single remaining workunit finished and uploaded normally.
As it was running the 'requesting 0 hours of work" message repeated with each update.
After the in-progress wu uploaded, the next update message was "Requesting 5636 seconds of work" then "No work from Project, Defering communication with project for
10 minutes 4 seconds." This repeated 4 times, the defered time increasing to 58 minutes
on the 4th time. The fifth update requested 888 seconds of work, and a wu was downloaded successfully and started running. Ten minutes later, the next update messages requested 2 seconds of work, and another wu was downloaded and queued with a "ready to run" status. Since then it's been business as usual. Both of those wu's were done and uploaded succesfully. The 'ready to run' unit going to 'running' status, and a new wu downloaded taking the 'ready to run' place. Instead of stopping/restarting/rebooting/etc, I just let it continue on as it pleased and whatever real or percieved problems there were worked themselves out. Perhaps the computer is like my dog and was temporarily scared spitless by all the fireworks noise.