I am running 5 BOINC projects using 6.6.36 on my Linux box. For a few days after installing it Einstein refused to send me work because "won't finish in time" and I had to suspend the other projects in order to obtain Einstein work. Then it straightened itself and is giving me work, Just let it run a few days.
Tullio
My Einstein@Home project saying "Won't get new tasks". BOINC has been idle for more than 2 days now. What could be the problem?
As Gundolf notes, you have really given us very little to work with.
I assume you are talking about the P4 machine since your Core 2 machine does have work. The completed results on your P4 machine do show your BOINC version to be 6.6.36 and this may well be the problem since many people report strange scheduling behaviour when using that particular version. I have no experience since I prefer not to be on the bleeding edge of BOINC development and have deliberately chosen to use more reliable but somewhat older versions. I can say that 6.4.7 seems to be devoid of such scheduling problems and if you continue to have issues you might consider reverting to something like this.
You don't seem to be supporting other projects so it is quite surprising that BOINC refuses to get any work at all. Sometimes the problem can be that other projects need to run urgently and BOINC can hold off until that has played out. Obviously that can't be the reason here.
It's also possible that you may have some screwy values in your state file. In your BOINC data folder there will be a file called client_state.xml. You can browse this file with a text editor like Windows notepad. If you do that and look for the values of the following tags, it should help with the diagnosis:-
keep geting this message after a lot of work was completed ....
And therein maybe lies your answer ...
You seem to be supporting 3 projects, CPDN, SAH and EAH.
Your current RACs (recent average credit) are 1,713, 297 and 101 respectively. At a guess, this translates to a strong bias towards CPDN, perhaps as a result of difficulty getting SAH work. Perhaps you added EAH quite recently out of frustration with difficulty of supply from SAH. If you have completed a lot of EAH work recently, perhaps BOINC is now going to favour other projects until they have caught up. For us to know if this is really happening, you need to tell us exactly what your resource share settings are for each project. If you have a really low share for EAH, it might help to explain things.
You wouldn't normally expect to see the message you quoted if it was just a debt problem. It looks very much like your DCF (duration correction factor) for EAH may be abnormally large for some reason. Have you by any chance made any major adjustments to your computer's clock recently? This can disrupt the value of DCF. If BOINC thinks EAH tasks are now going to take considerably longer than they really are and if you have a low resource share, BOINC could be quite easily fooled into thinking that tasks wont finish in time. Also I notice that you are using version 6.6.36. There have been quite a few reports that this version has problems with proper scheduling of tasks and this too might be a factor. Unfortunately the BOINC Devs seem to be preoccupied with other priorities and don't seem inclined to fix and release a better 6.6.x version. If it were my machine, I'd be going back to something like 6.4.x or whatever suitable version exists for your OS.
I am using BOINC 6.6.36 on my Linux box. For a few days after installation it gave me no Einstein tasks, saying 'won't finish in time". I fooled it by suspending my other 4 projects and resuming them after obtaining Einstein work. Now it works like clockwork.
Tullio
I am using BOINC 6.6.36 on my Linux box. For a few days after installation it gave me no Einstein tasks, saying 'won't finish in time". I fooled it by suspending my other 4 projects and resuming them after obtaining Einstein work. Now it works like clockwork.
Tullio
6.6.36 has a bunch of errors. Try 6.6.38 or 6.6.76 from "ageless" instead. Nobody knows why this buggy version was released to the boinc community.
PS: Some crunchers had no problems so far reported with 6.10.1 or the older 6.6.20.
I found the client_state.xml under C:\Documents and Settings\All Users\Application Data\BOINC.
0.999004
1.000000
0.999891
1.987305
Thanks.
Quote:
Quote:
My Einstein@Home project saying "Won't get new tasks". BOINC has been idle for more than 2 days now. What could be the problem?
As Gundolf notes, you have really given us very little to work with.
I assume you are talking about the P4 machine since your Core 2 machine does have work. The completed results on your P4 machine do show your BOINC version to be 6.6.36 and this may well be the problem since many people report strange scheduling behaviour when using that particular version. I have no experience since I prefer not to be on the bleeding edge of BOINC development and have deliberately chosen to use more reliable but somewhat older versions. I can say that 6.4.7 seems to be devoid of such scheduling problems and if you continue to have issues you might consider reverting to something like this.
You don't seem to be supporting other projects so it is quite surprising that BOINC refuses to get any work at all. Sometimes the problem can be that other projects need to run urgently and BOINC can hold off until that has played out. Obviously that can't be the reason here.
It's also possible that you may have some screwy values in your state file. In your BOINC data folder there will be a file called client_state.xml. You can browse this file with a text editor like Windows notepad. If you do that and look for the values of the following tags, it should help with the diagnosis:-
Won't get new tasks
)
We need a little bit more info. At least the reason BOINC tells you why it won't get new tasks.
Then you could have told us that you are running BOINC 6.6.36 on windows XP :-)
Are you connected to any other projects?
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
I am running 5 BOINC projects
)
I am running 5 BOINC projects using 6.6.36 on my Linux box. For a few days after installing it Einstein refused to send me work because "won't finish in time" and I had to suspend the other projects in order to obtain Einstein work. Then it straightened itself and is giving me work, Just let it run a few days.
Tullio
RE: My Einstein@Home
)
As Gundolf notes, you have really given us very little to work with.
I assume you are talking about the P4 machine since your Core 2 machine does have work. The completed results on your P4 machine do show your BOINC version to be 6.6.36 and this may well be the problem since many people report strange scheduling behaviour when using that particular version. I have no experience since I prefer not to be on the bleeding edge of BOINC development and have deliberately chosen to use more reliable but somewhat older versions. I can say that 6.4.7 seems to be devoid of such scheduling problems and if you continue to have issues you might consider reverting to something like this.
You don't seem to be supporting other projects so it is quite surprising that BOINC refuses to get any work at all. Sometimes the problem can be that other projects need to run urgently and BOINC can hold off until that has played out. Obviously that can't be the reason here.
It's also possible that you may have some screwy values in your state file. In your BOINC data folder there will be a file called client_state.xml. You can browse this file with a text editor like Windows notepad. If you do that and look for the values of the following tags, it should help with the diagnosis:-
*
*
*
Cheers,
Gary.
baffled keep geting this
)
baffled
keep geting this message after a lot of work was completed:
Fri Sep 11 21:48:32 2009 Einstein@Home Message from server: (won't finish in time) BOINC runs 66.9% of time, computation enabled 100.0% of that
mac g-5 2.266 dual intel xeon. 6 gig ram.
RE: baffled keep geting
)
Did you upgrade BOINC recently?
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: keep geting this
)
And therein maybe lies your answer ...
You seem to be supporting 3 projects, CPDN, SAH and EAH.
Your current RACs (recent average credit) are 1,713, 297 and 101 respectively. At a guess, this translates to a strong bias towards CPDN, perhaps as a result of difficulty getting SAH work. Perhaps you added EAH quite recently out of frustration with difficulty of supply from SAH. If you have completed a lot of EAH work recently, perhaps BOINC is now going to favour other projects until they have caught up. For us to know if this is really happening, you need to tell us exactly what your resource share settings are for each project. If you have a really low share for EAH, it might help to explain things.
You wouldn't normally expect to see the message you quoted if it was just a debt problem. It looks very much like your DCF (duration correction factor) for EAH may be abnormally large for some reason. Have you by any chance made any major adjustments to your computer's clock recently? This can disrupt the value of DCF. If BOINC thinks EAH tasks are now going to take considerably longer than they really are and if you have a low resource share, BOINC could be quite easily fooled into thinking that tasks wont finish in time. Also I notice that you are using version 6.6.36. There have been quite a few reports that this version has problems with proper scheduling of tasks and this too might be a factor. Unfortunately the BOINC Devs seem to be preoccupied with other priorities and don't seem inclined to fix and release a better 6.6.x version. If it were my machine, I'd be going back to something like 6.4.x or whatever suitable version exists for your OS.
Cheers,
Gary.
I am using BOINC 6.6.36 on my
)
I am using BOINC 6.6.36 on my Linux box. For a few days after installation it gave me no Einstein tasks, saying 'won't finish in time". I fooled it by suspending my other 4 projects and resuming them after obtaining Einstein work. Now it works like clockwork.
Tullio
RE: I am using BOINC 6.6.36
)
6.6.36 has a bunch of errors. Try 6.6.38 or 6.6.76 from "ageless" instead. Nobody knows why this buggy version was released to the boinc community.
PS: Some crunchers had no problems so far reported with 6.10.1 or the older 6.6.20.
But 6.6.36 is working on my
)
But 6.6.36 is working on my Linux box. If it ain't broke don't fix it.
Tullio
Gary, I found the
)
Gary,
I found the client_state.xml under C:\Documents and Settings\All Users\Application Data\BOINC.
0.999004
1.000000
0.999891
1.987305
Thanks.