| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Message from Server: (won't finish in time) bugger |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello
I am a WCG member since at least two years and always enjoyed contributing. But since I run the latest client (6.6.36 on MacOSX 10.6) I am not receiving any WUs anymore. The message I get instead is Do 15 Okt 09:02:28 2009 World Community Grid Message from server: No work sent I am opted into all available projects. I hate this because the WUs DO FINISH IN TIME if I eventually get one. I am just sitting around idle due to this false assertion by Boinc.Do 15 Okt 09:02:28 2009 World Community Grid Message from server: No work is available for Influenza Antiviral Drug Search Do 15 Okt 09:02:28 2009 World Community Grid Message from server: (won't finish in time) Computer on 69.8% of time, BOINC on 98.8% of that Can you please fix this issue, it is really annoying. Thanks! |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Are you sure you're opted into all projects? FLU has no work so that message I'd understand.
----------------------------------------Then, how many hours in the day do you crunch and have you crunched in recent days as already 69.8% says, it's not full time. Since you have no work presently, exit BOINC, delete the ALL files starting with client_state....xml from the BOINC data dir (path in message log) and restart BOINC. That should restore all time keeping parms.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am sure I am opted into all projects. I am crunching far enough for finishing a WU in time, just as I did the years before (on avarage 8-12 hours a day). A WU finishes on average in 6 hours on my machine. So usually it takes no more than a maximum of three days to finish a WU. Sometimes it does 2 WUs a day.
----------------------------------------I refuse to mess around with client state files. I expect to recieive WUs as I did before. Once I tried to fix this issue by messing around with a client state file I lost 600 hours of CPU hours on climate prediction as it refused to upload then. Now on a new system with Boinc reinstalled the same issue comes up again. I feel locked out by Boinc for no real reason :( [Edit 1 times, last edit by Former Member at Oct 15, 2009 7:54:30 AM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Well that is then a Mexican stand off. I tell you how to fix things swiftly & messless and you wont. The deletes recreating these files with defaults upon restart. WCG can't override to force work to your client since your client is in charge which is how it should be. A project reset wont fix this either as it only changes 1 critical parm to default.
----------------------------------------So, it's your choice to follow my advise or not. Let us know.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you very much for your advice. But I think this is not a question of just solving my specific problem by deleting client state files, but of solving a general problem that was obviously being introduced with 6.6.36.
If you google this issue you will find that I am not the only one on this planet having this problem. And I think WCG and BOINC are depriving themselves of valuable CPU hours this way. It should be looked into this NEW problem by the people who are developing the future versions of BOINC. But thank you very much again. Still I will not touch the client state files due to my prior bad experiences. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
No, this is a frequent problem reported for any version when crunching habits changed or a job took much longer upsetting the time fraction parameters. No way to fix this unless you keep your computer running for the next few days, 24/7 and then let the next jobs finish in 1 run so BOINC learns things are getting better again.
----------------------------------------Your choice, the quick fix I've provided you.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, I guess you should know better than me. But I saw this behaviour the very first time with 6.6.36. I am running Boinc since the very first days on Win, Linux and Mac. I have not changed crunching habits significantly.
Just for the record: Another temporary remedy is also to disconnect from the WCG project within Boinc and then to connect again. But within a few days the same issue will come up again. I cannot be bothered to regularily fix an issue that shoudn't be there in the first place. It should just crunch away. My CPU cycles are at Boincs disposal... |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
If you have a bigger cache, suggest you reduce that to say 1.0 days. Also the "Connect Every... x days" effects work fetch. If you had late jobs and the client computes that the next connect will carry the completion time after deadline, then also work fetch is stalled. Therefor if you are always connected, set that value back to the WCG default of 0.2 days. This way completed work also gets reported regularly.
----------------------------------------Why you went to 6.6.36 I'm not going to ask, but when you did you should also have seen a message that 6.6.38 is out as the Berkeley "recommended", with other bugs, due to be fixed in 6.6.40 or later, which is why WCG is still on 6.2.28. Even then with that client you could have had the same happening, ... just a coincidental meeting of "I updated and ever since..." and making other changes at the same time.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Why you went to 6.6.36 I'm not going to ask, but when you did you should also have seen a message that 6.6.38 is out as the Berkeley "recommended", with other bugs, due to be fixed in 6.6.40 or later, which is why WCG is still on 6.2.28. Now that is interesting, I was not aware of that. If you go to boinc.berkeley.edu and hit the download button, what you will get at the moment is 6.6.36 (at least when on OSX).Thanks again  |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
Why you went to 6.6.36 I'm not going to ask, but when you did you should also have seen a message that 6.6.38 is out as the Berkeley "recommended", with other bugs, due to be fixed in 6.6.40 or later, which is why WCG is still on 6.2.28. Even then with that client you could have had the same happening, ... just a coincidental meeting of "I updated and ever since..." and making other changes at the same time. Well, for a couple obvious reasons he's running v6.6.36: 1: v6.2.18 doesn't work with the "Snow Leopard"-OS he's running. (atleast according to various messages on these WCG-forums...) 2: v6.6.36 is the last released version for Mac, so he shouldn't see any message about upgrading to a non-existing version...  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
|