Due to child intervention, my computer date was set to Dec 20, 2011. After correcting, BOINC is saying its over committed. I am running Einstein and CPDN. Einstein will not get any new work and CPDN has 1,614 hour to completion. Can i do anything to "reset" BOINC? have tried the stop/start/reboot options. do I need to wait out the 67 days of CPDN?

Thanks

---

CPDn models are very long. And, it is possible that you are over-comitted. I don't know if it is related to the CPDN model alone or not.

What work DO you have on your computer?

What speed ... we need more information to be able to help ...

And, I also have one computer that is over-committed on one CPDN model, but I am just letting BOINC do its thing ...

---

My machine was not overcommitted before the date change, only after. The machine has CPDN and Einstein running with .5 day work buffer prefrence both with resource share 100. so they each run 12 hours per day on average. As I understand. my CPDN is due 11/18/2006. BOINC is stating 1614 hours to completion. That should allow plenty of time.

---

CPDN is due 11/18/2006. BOINC is stating 1614 hours to completion.

I _think_ I may know the problem, but I can't get to the info... Would you go to the CPDN site, your account, view computers, and copy the info from the bottom of the page and paste it in here? What I am looking for is:

Last time contacted server 20 Dec 2005 14:54:39 UTC
% of time BOINC client is running 88.245 %
While BOINC running, % of time host has an Internet connection 99.989 %
While BOINC running, % of time work is allowed 99.978 %
Average CPU efficiency 0.986883
Result duration correction factor 1

(This is from my computer from CPDN.) I suspect that the date mix-up, or some other issue, has caused your "% time" or efficiency numbers to be extremely low. If so, we can help you edit the xml file to get these fixed, or, they _should_ start to recover "on their own" after two or three trickles are sent up.

You can also "force" _some_ Einstein work through, simply by hitting Suspend on the CPDN project for just a few minutes. It will download Einstein to "fill" your idle CPU, then because you are overcommitted, will run the Einstein to completion before it will go back to CPDN, as Einstein has the earliest deadline. I don't think this is _necessary_, I think we can resolve the basic problem, but it is another way you can get some Einstein done without waiting 67 days.

---

If the work was downloaded while the date was wrong you will most likely have to wait out the entire model before things get back to normal. Otherwise Bill's post is most likely correct.

---

BOINC WIKI

BOINCing since 2002/12/8

This CPDN was download in 2 weeks ago (before error occurred on Monday). you are correct about the einstein processing. that is what happened when the date was corrected. Einstein took over until depleted and no more are fetched.

Here you go:
Created 5 Nov 2005 22:15:12 UTC
Total Credit 2,249.52
Recent average credit 67.39
CPU type GenuineIntel
Intel(R) Pentium(R) M processor 1600MHz
Number of CPUs 1
Operating System Microsoft Windows XP
Professional Edition, Service Pack 2, (05.01.2600.00)
Memory 1534.9 MB
Cache 976.56 KB
Swap space 1884.9 MB
Total disk space 74.53 GB
Free Disk Space 25.33 GB
Measured floating point speed 1292.8 million ops/sec
Measured integer speed 2500.7 million ops/sec
Average upload rate Unknown
Average download rate Unknown
Average turnaround time 0 days
Maximum daily WU quota per CPU 3/day
Results 4
Number of times client has contacted server 346
Last time contacted server 22 Dec 2005 12:37:03 UTC
% of time BOINC client is running 100 %
While BOINC running, % of time host has an Internet connection 100 %
While BOINC running, % of time work is allowed 0 %
Average CPU efficiency 0.825107
Result duration correction factor 1

---

While BOINC running, % of time work is allowed 0 %

Bingo.

Not sure if this is from the date mixup or not, but until fixed, you're going to be overcommitted even if you have 3 SECONDS worth of work left...

First, quit BOINC completely; file/exit, then verify _all_ boinc-related components have stopped, using Task Manager. Locate the following file: C:\\Program Files\\BOINC\\client_state.xml. Make a copy of this file somewhere outside the BOINC folder, as a backup. Open the 'real' file with NotePad. About 30 lines down from the top, you will see "active_frac". Change the 0 there to a 1. Make _no_ other changes to this file... Save it and close. Relaunch BOINC and see if all is well now. If anything totally strange happens, stop BOINC again immediately, and put back the copy you made as a backup.

---

While BOINC running, % of time work is allowed 0 %

Bingo.

Not sure if this is from the date mixup or not, but until fixed, you're going to be overcommitted even if you have 3 SECONDS worth of work left...

First, quit BOINC completely; file/exit, then verify _all_ boinc-related components have stopped, using Task Manager. Locate the following file: C:\\Program Files\\BOINC\\client_state.xml. Make a copy of this file somewhere outside the BOINC folder, as a backup. Open the 'real' file with NotePad. About 30 lines down from the top, you will see "active_frac". Change the 0 there to a 1. Make _no_ other changes to this file... Save it and close. Relaunch BOINC and see if all is well now. If anything totally strange happens, stop BOINC again immediately, and put back the copy you made as a backup.

Thank you. That worked. As soon as it started up, BOINC downloaded and Einstein and started processing it. Would have hated to wait 1630 hours for CPDN to complete before sharing another project. Much appreciated.

---