No new workunits after Client Error
20 Sep 2007 12:40:57 UTC
Topic 193156
(moderation:
We had a short power outage yesterday and when the computer restarted the Einstein work unit which probably was not complete was sent back with a outcome of “Client Error� and Client state “Computer Error� That was my last work unit at the time. I did not and have not received any additional Einstein work units. I still am computing and receiving work units from SETI. I have restarted my computer and used “Update� , “Suspend-Resume� and “Reset Project� on Einstein but to no avail. When I use “Update� the messages on my computer are
9/20/2007 8:34:29 AM|Einstein@Home|Sending scheduler request: Requested by user
9/20/2007 8:34:29 AM|Einstein@Home|(not requesting new work or reporting completed tasks)
9/20/2007 8:34:35 AM|Einstein@Home|Scheduler RPC succeeded [server version 601]
9/20/2007 8:34:35 AM|Einstein@Home|Deferring communication for 1 min 0 sec
9/20/2007 8:34:35 AM|Einstein@Home|Reason: requested by project
I do not receive any new workunits. What can I do fix the problem?
No new workunits after Client Error
)
Read this.
I had already read the areas
)
I had already read the areas that you sent me to. That is why I waited overnight with the computer on before posting the message. The outage was about 2:00 yesterday afternoon so that I definitely waited overnight (even with GMT). Also I have a core2 Duo processor and the computer is left on all the time. Einstein is supposed to get about 20% of the time with SETI getting the rest. It is obvious to me that my computer is not asking for work and that is the problem. This is the first Einstein work unit of mine that I know of having received a Client error so I think that I should still be able to get at least one work unit per day. I will repeat that is looks like I am not asking for work from Einstein even though I do not have any work units showing on my Tasks page.
(not requesting new work or
)
(not requesting new work or reporting completed tasks) is an informational message, not an error. It is BOINC telling you that you have enough work in your queue to keep itself busy.
BOINC works by way of debts, long term and short term debts. You can read up about them here.
By running a long
You've got 80% of your resource shares set to Seti, 20% to Einstein.
The last result you ran for Einstein took 46,600+ seconds (rounding it off) before it crashed, which means you have to pay back that time to Seti, before you get new work.
This can take up to 2.5 days before it does so (5x 46,600 seconds or 0.5 days).
Just wait it out, don't force things, nothing is broken, it's all working as it should.
RE: ... nothing is broken,
)
Ah, but in all fora at all projects there are posts replete with statements from virtually everyone (experienced or not) telling us that boinc is not working as it should. Anyway, the same old questions get asked, ad nauseum. I mentioned in a post somewhere that I believe BOINC should force people to review a short tutorial on the basics of how boinc works, scheduling and the debt system, plus a few other ad nauseum topics, before they are given an account. I know my idea won't be adopted but why give someone keys to a car before they learn how to drive it? We let them have an accident first and then tutor them after the fact.
RE: Ah, but in all fora at
)
Ssssshhhh. ;-)
It does have problems with multi-core machines and that, but as far as I know that's fixed in the new code. Or hopefully fixed. Until that time, we don't go to Ravenholm. :-)
RE: RE: ... nothing is
)
I thing a much better solution would be if boinc would explan, using plain language, why it it doing what. E.g. instead of just saying "not asking for new work", it could state something like:
Not asking for more work from project (X) BECAUSE
project Z needs to catch up to reduce debt
or
project Z gets priority as the current task for project Z is in danger of missing it's deadline
or
project X indicated it has no work at the moment
or
youhave reached your quota of downloads for today
or
whatever.
If you are designing software for the masses, don't try to force them to get a diploma in BOINCology first, but make BOINC more intuitive :-).
I bet that by making the messages of BOINC more verbose, the number of questions and the level of frustration in the Problems forums of BOINC projects could be cut in half.
It would be quite a simple change which would make a great software even better.
CU
H-BE
RE: or whatever.
)
That's the best one. :-D
No work from project.
Reason: Whateveh! I can do what I want!
Seriously though, go to Trac and make it an enhancement ticket. You've got my vote.
RE: I bet that by making
)
Verbose has a bad connotation for me as it implies using more words than necessary to convey a message, but if messages were informative and precise without being verbose then your solution is most practical.