since i have boinc 4.45 i often just am not getting work.

i run seti and lhc.
does this have to do with the seti problems? nothing uploads and stays on my software.

i have my systems set to a 7 day network access. which should not be that strange.

i was under the impression boinc was ment to keep our cpu's crunching. not keep waiting until the last moment before getting some work.

i monitor maybe once a day what boinc is doing. i want to see work for my cpu's or i am out.

I have been having this problem also, but i just tried something that allowed the others to continue crunching.
suspend seti and then update the other projects, it worked for me.

---

I have been having this problem also, but i just tried something that allowed the others to continue crunching.
suspend seti and then update the other projects, it worked for me.

thank you for your answer, i will try this.

this is not the way boinc should work however.

client software should be able to see more work is needed from the participating projects.

and in the meantime i tried it. this does not work for me.

i think boinc is not respecting the choices of its donators of cpu time.

the boinc persons will tell us it is up to the projects. and the projects will tell us as less as possible.

boinc should keep our cpu's running.
boinc should do that according to our prefs.
there are allways problems in different projects.
that is why we went to boinc, problems in one project makes no difference.
there is allways work from an other project.
therefore, if seti has problems and lhc has lots of work i might expect work from lhc. but this does not happen in time.

since i have boinc 4.45 i often just am not getting work.

i run seti and lhc.
does this have to do with the seti problems? nothing uploads and stays on my software.

I believe this is related to a bug in the BOINC Manager that is fixed in an upcoming version. BOINC counts the work waiting to upload as being in process, so thinks it doesn't need to download more. Version 4.72 is in beta testing, and many of us are eagerly awaiting its release, for this and other fixes.
(And if I'm incorrect, somebody will be along soon with the right info!)

MJ

---

Well, aside from SETI@Home being off-line while they fix hardware and software problems, and LHC@Home during the last week was off-line with no work because we were in-between expiriments...

So, yes, this *IS* related to the problems currently being worked on at SETI@Home.

---

In that case, what's the problem with Einstein@home? I also run SETI & LHC, and I haven't even been able to UPLOAD any of my results for over a week, let alone get any more work.

Come on guys, there's SCIENCE to be done!:o)

---

Well, aside from SETI@Home being off-line while they fix hardware and software problems, and LHC@Home during the last week was off-line with no work because we were in-between expiriments...

So, yes, this *IS* related to the problems currently being worked on at SETI@Home.

but this is not the complete answer. lhc has plenty of work now. i lowered my network connection time to 2 days. my linux machine now get more work from lhc then any other cpu. and this while my linux system is the slowest cpu by far. the rest of my systems run windows.

---

WooHoo!
I found the solution to all my problems on the Einstein@home site. Well, all my BOINC-related problems anyway, but let's not go there;o)

Under the "Projects" tab, I clicked "No new work" for all but 1 of my projects, then I clicked "Update" for the remaining project, and I started uploading, and soon had more work to do.
Repeat this process for all of my projects, and Einstein, SETI & LCH are all now happily crunching away.
Hmm, I'm feeling peckish...

---

I've been updating my setiathome clients to the boinc version, with decidedly mixed results. My two macs are happily crunching away, and if I remember right, my win2k at work is also. My three FreeBSD machines, with a fresh build from the ports tree all show registered in "View computers", but show no contact time. My Win2K at home shows registered and contacted, but isn't getting any work. I tried updating it. I tried suspending, updating, resuming, all to no avail:

9/2/2005 12:10:22 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/2/2005 12:10:22 AM|SETI@home|Requesting 172800 seconds of work, returning 0 results
9/2/2005 12:10:25 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
9/2/2005 12:10:25 AM|SETI@home|No work from project
9/2/2005 12:10:26 AM|SETI@home|Deferring communication with project for 59 seconds
9/2/2005 12:11:26 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/2/2005 12:11:26 AM|SETI@home|Requesting 172800 seconds of work, returning 0 results
9/2/2005 12:11:38 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
9/2/2005 12:11:38 AM|SETI@home|Message from server: Not sending work - last RPC too recent: 72 sec
9/2/2005 12:11:38 AM|SETI@home|No work from project
9/2/2005 12:11:39 AM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds
9/2/2005 12:12:06 AM||request_reschedule_cpus: project op
9/2/2005 12:12:07 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/2/2005 12:12:07 AM|SETI@home|Requesting 172800 seconds of work, returning 0 results
9/2/2005 12:12:21 AM|SETI@home|Resetting project
9/2/2005 12:12:21 AM||request_reschedule_cpus: exit_tasks
9/2/2005 12:12:21 AM||request_reschedule_cpus: project op
9/2/2005 12:12:22 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/2/2005 12:12:22 AM|SETI@home|Requesting 172800 seconds of work, returning 0 results
9/2/2005 12:12:26 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
9/2/2005 12:12:26 AM|SETI@home|No work from project
9/2/2005 12:12:27 AM|SETI@home|Deferring communication with project for 6 minutes and 21 seconds
9/2/2005 12:18:10 AM||request_reschedule_cpus: project op
9/2/2005 12:18:12 AM||request_reschedule_cpus: project op
9/2/2005 12:18:15 AM||request_reschedule_cpus: project op
9/2/2005 12:18:16 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/2/2005 12:18:16 AM|SETI@home|Requesting 172800 seconds of work, returning 0 results
9/2/2005 12:18:24 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
9/2/2005 12:18:24 AM|SETI@home|No work from project
9/2/2005 12:18:25 AM|SETI@home|Deferring communication with project for 14 minutes and 56 seconds

---

If you look at the server status site you see the ready to send amount is around 10. That is an approximation and not a real time number. The system is incapable of keeping up demand. So if you just let Boinc do its thing, it will give you new work once it can.

---