Message from server: No work available (there was work but your computer would not finish it before it is due Review preferences for this project's Resource Share
> What does the above message mean? I signed up for testing and this is waht I
> got. What can I do to fix it?
>
> Thanks
>
> Len
FRONT PAGE NEWS
Feb 13, 2005
We have enabled the BOINC configuration option 'enforce_delay_bound'. This prevents work from being sent to your machine if BOINC determines that your machine could not finish the work before the deadline. This may affect users with very slow machines, or users attached to multiple BOINC projects, whose Einstein@Home resource share is small.
There's a fine line between fishing and standing on the shore looking like an idiot -- Steven Wright
I have got the same problem. I im running Einstein, LHC and Pirates with a resource share of 100 for each project. On my P4m 1.7 GHz it takes about 14 hours to finish an Einstein WU. With a reporting deadline of 7 days i should receive work. But i do not.
> I have got the same problem. On my P4m 1.7 GHz it takes about 14
> hours to finish an Einstein WU. With a reporting deadline of 7 days i should
> receive work. But i do not.
I've the same problem. I had share E@H and LHC 100:100 ..
now i switch Einstein to 900 (90%)... But it show the same error.
I send back every unit in 20-24h, with the same reporting-deadline..
I think this i a new funny feature to let my cpu do NOTHING .. :-(
It's very bad that now run 30 PC idle, if they don't correct the problem.
I really think this is a serious problem, than i don't see that my pc does not do the work in the right time. And they aren't really slow, just not the fastest.
I'm working to fix these problems now. I think there is a bug in the BOINC scheduling code, where it is incorrectly calculating the 'on-time' and 'active-time' fractions for host machines. I've just stuck in a workaround that doesn't really fix this problem but should at least ensure that your machines get some work. Could you try 'update project' and see if you get some work now? Or just wait until your machine contacts the scheduler again?
At the Moment it say .. "failed" and try in 1 minuted ..
Grr ... Now the GUI was to fast :-) ...
** Einstein@Home - 2005-02-14 19:34:31 - Message from server: Not sending work - last RPC too recent: 3 sec
** Einstein@Home - 2005-02-14 19:34:31 - Deferring communication with project for 10 minutes and 0 seconds
I haven't run into this message trying to get WUs before, but I have noticed that the other BOINC projects over-estimate how long it would take me to complete a WU by quite a bit. BOINC for instance assumes that it will take 5 hours 17 minutes, and 42 seconds to complete a SETI WU. I don't think it has ever taken over 4 hours in enough WUs to have amassed over 10,000 credits with them (not sure off the top of my head how many WUs, but could probably check).
Looking for a margin of error here, we'd be looking at over-estimating how long it takes my comp to complete by about 32% (assuming I did the math right).
Predictor sees the same over-estimation, where BOINC thinks it will take 3 hours and 47 minutes to complete. However, it usually takes 1 hour and 20 minutes (give or take). The most I ever saw was about 1 hour 45 minutes. Guesstimating that, it looks about 1.5 to 2 times an over-estimation on time to completion.
Einstein@home predicts about 7 hours 35 minutes according to BOINC (4.20 right now...) but takes more like 8 hours and 15 minutes or so. (The WUs I've got from here, are probably the closest to the estimated time, though under.)
I'm not exactly sure what CPU benches BOINC runs, but the results do tend to leave a rather sizeable variation between prediction and reality, at least on my Athlon XP 1900+ here. I've noticed this accross practically all core clients I've tried. But to be specific CC 4.13, 4.14, 4.16, 4.18, 4.19, 4.62, 4.66, and 4.20...
> I'm working to fix these problems now. I think there is a bug in the BOINC
> scheduling code, where it is incorrectly calculating the 'on-time' and
> 'active-time' fractions for host machines. I've just stuck in a workaround
> that doesn't really fix this problem but should at least ensure that your
> machines get some work. Could you try 'update project' and see if you get
> some work now? Or just wait until your machine contacts the scheduler again?
>
> Cheers,
> Bruce
>
Good, glad to see that my 'work-around' fixed. The bug is in a part of the BOINC scheduler that I don't understand well enough to fix easily myself. I've written to the person responsible and hopefully this will be fixed 'properly' fairly soon. For the moment I'll leave my 'work-around' in place.
What would be really nice would be if the scheduler used the actual work on hand on the client rather than a resource share to determine whether and how much work to download. Slower machines that could finish one WU on time for one project are now going to be limited to one project with no backup. This means that if that project goes down for any reason, those machines will be sitting idle.
Message from server: No work available (there was work but your
)
> What does the above message mean? I signed up for testing and this is waht I
> got. What can I do to fix it?
>
> Thanks
>
> Len
FRONT PAGE NEWS
Feb 13, 2005
We have enabled the BOINC configuration option 'enforce_delay_bound'. This prevents work from being sent to your machine if BOINC determines that your machine could not finish the work before the deadline. This may affect users with very slow machines, or users attached to multiple BOINC projects, whose Einstein@Home resource share is small.
There's a fine line between fishing and standing on the shore looking like an idiot -- Steven Wright
I have got the same problem.
)
I have got the same problem. I im running Einstein, LHC and Pirates with a resource share of 100 for each project. On my P4m 1.7 GHz it takes about 14 hours to finish an Einstein WU. With a reporting deadline of 7 days i should receive work. But i do not.
> I have got the same
)
> I have got the same problem. On my P4m 1.7 GHz it takes about 14
> hours to finish an Einstein WU. With a reporting deadline of 7 days i should
> receive work. But i do not.
I've the same problem. I had share E@H and LHC 100:100 ..
now i switch Einstein to 900 (90%)... But it show the same error.
I send back every unit in 20-24h, with the same reporting-deadline..
I think this i a new funny feature to let my cpu do NOTHING .. :-(
It's very bad that now run 30 PC idle, if they don't correct the problem.
I really think this is a serious problem, than i don't see that my pc does not do the work in the right time. And they aren't really slow, just not the fastest.
I'm working to fix these
)
I'm working to fix these problems now. I think there is a bug in the BOINC scheduling code, where it is incorrectly calculating the 'on-time' and 'active-time' fractions for host machines. I've just stuck in a workaround that doesn't really fix this problem but should at least ensure that your machines get some work. Could you try 'update project' and see if you get some work now? Or just wait until your machine contacts the scheduler again?
Cheers,
Bruce
Director, Einstein@Home
At the Moment it say ..
)
At the Moment it say .. "failed" and try in 1 minuted ..
Grr ... Now the GUI was to fast :-) ...
** Einstein@Home - 2005-02-14 19:34:31 - Message from server: Not sending work - last RPC too recent: 3 sec
** Einstein@Home - 2005-02-14 19:34:31 - Deferring communication with project for 10 minutes and 0 seconds
i'll wait some time :-)
I haven't run into this
)
I haven't run into this message trying to get WUs before, but I have noticed that the other BOINC projects over-estimate how long it would take me to complete a WU by quite a bit. BOINC for instance assumes that it will take 5 hours 17 minutes, and 42 seconds to complete a SETI WU. I don't think it has ever taken over 4 hours in enough WUs to have amassed over 10,000 credits with them (not sure off the top of my head how many WUs, but could probably check).
Looking for a margin of error here, we'd be looking at over-estimating how long it takes my comp to complete by about 32% (assuming I did the math right).
Predictor sees the same over-estimation, where BOINC thinks it will take 3 hours and 47 minutes to complete. However, it usually takes 1 hour and 20 minutes (give or take). The most I ever saw was about 1 hour 45 minutes. Guesstimating that, it looks about 1.5 to 2 times an over-estimation on time to completion.
Einstein@home predicts about 7 hours 35 minutes according to BOINC (4.20 right now...) but takes more like 8 hours and 15 minutes or so. (The WUs I've got from here, are probably the closest to the estimated time, though under.)
I'm not exactly sure what CPU benches BOINC runs, but the results do tend to leave a rather sizeable variation between prediction and reality, at least on my Athlon XP 1900+ here. I've noticed this accross practically all core clients I've tried. But to be specific CC 4.13, 4.14, 4.16, 4.18, 4.19, 4.62, 4.66, and 4.20...
It seems to work now. Just
)
It seems to work now. Just got one WU.
Thank You.
> I'm working to fix these problems now. I think there is a bug in the BOINC
> scheduling code, where it is incorrectly calculating the 'on-time' and
> 'active-time' fractions for host machines. I've just stuck in a workaround
> that doesn't really fix this problem but should at least ensure that your
> machines get some work. Could you try 'update project' and see if you get
> some work now? Or just wait until your machine contacts the scheduler again?
>
> Cheers,
> Bruce
>
> It seems to work now. Just
)
> It seems to work now. Just got one WU.
> Thank You.
Mee Toooo
Bruce, a very happy 'thank you very much for fast support' 2 you
:-)
Good, glad to see that my
)
Good, glad to see that my 'work-around' fixed. The bug is in a part of the BOINC scheduler that I don't understand well enough to fix easily myself. I've written to the person responsible and hopefully this will be fixed 'properly' fairly soon. For the moment I'll leave my 'work-around' in place.
Cheers,
Bruce
Director, Einstein@Home
What would be really nice
)
What would be really nice would be if the scheduler used the actual work on hand on the client rather than a resource share to determine whether and how much work to download. Slower machines that could finish one WU on time for one project are now going to be limited to one project with no backup. This means that if that project goes down for any reason, those machines will be sitting idle.
BOINC WIKI