I\'m kinda confused & kinda irritated. I\'ve been letting my Dual Core AMD cook away for awhile running Climate 50%, Seti 25% and Rosetta 25%

I just went to look at my Sulphur progress as it was around 20 some % completed and I remember the date was up to 1825 but I see no Sulphur running at all in Boinc or Task manager. A Windows Explorer search shows it\'s not on my computer. The wu was sulphur_eqcb_000687323_0 and a search for this shows nothing yet under disk in BOINC it shows Climate has 1012.01 meg taken.

Looks like the WU disinegrated itself.

What would cause this? I\'ve been letting this WU have the lions share for over a week now.

Any way I can have BOINC find it\'s tail & start finishing the job it started?

Thanks,

Gary

---

what version of BOINC are you using, there is a known bug in the earlier versions where it may not restart crunching after running benchmarks.........

---

I think it\'s the newest; 5.2.7

---

I think it\'s the newest; 5.2.7

the latest is actually 5.2.13, this may solve your problem



Boinc DL page

---

This begs the question why they don\'t notify users of updates. Most every program I use notifies me if there is an update. It\'s apparently not unusual for the authors of software to implement this feature.

Also, I haven\'t run a bench mark since my first day of using BOINC. Unless BOINC does this by default, this loss did not come after running a benchmark.

Thank you for informing me of a new platform.

---

Hi Dr. Gary,

Are you overclocking your PC? Just wondering as the speed on your account page shows 2.15 sec/TS. This is extremely fast for a standard clocked processor of any kind. While overclocking and climateprediction can mix alright, it would be one of the first places I would look if a problem crops up. The climateprediction science app is more sensitive to any small errors than most other distributed computing projects.

The error on your result page for result ID 1363690 is this

{core_client_version}5.2.7{/core_client_version}
{message}Incorrect function. (0x1) - exit code 1 (0x1)
{/message}

There is a description of this error code in the BOINC Wiki here and possible causes, although I don\'t know if that will help in this case.

This begs the question why they don\'t notify users of updates. Most every program I use notifies me if there is an update. It\'s apparently not unusual for the authors of software to implement this feature.

It can be problematic as new versions of BOINC may be released primarily to fix problems with an individual science client, but sometimes the other science projects have to update their software to handle the new version, and this can take awhile. Additionally, an updated client that fixes things for one or more projects, or adds project specific enhancements, can also introduce bugs for other projects. Not an ideal situation.

Also, I haven\'t run a bench mark since my first day of using BOINC. Unless BOINC does this by default, this loss did not come after running a benchmark.

BOINC runs benchmarks every 5 days automatically. It should list it in the Messages tab of the BOINC GUI when it occurs.

Hi Geophi,

Yes, I\'m using a nF4 based board with a dual core Opteron. I\'ve been running this configuration for some time now with all benchmark trials showing no errors. I have no problems with any programs that I have seen thus far. and this loss of the climateprediction WU is my first unexpected experience so I don\'t know what to attribute it to.

BOINC has set aside 6 megs of disc space to seti, 17 megs to Rosetta and 1 Gig to Climate but Climate is not present in the work tab. It is present in the Projects tab.

Should I reset the project?

---

Boinc does not process so it is not the cause of this error, plus this is the third WU that has errored this month, check your view results for more info....

---

BOINC Wiki

Boinc does not process so it is not the cause of this error, plus this is the third WU that has errored this month, check your view results for more info....

But the other two errors were because they were aborted via GUI RPC, so not a machine error.

BOINC has set aside 6 megs of disc space to seti, 17 megs to Rosetta and 1 Gig to Climate but Climate is not present in the work tab. It is present in the Projects tab.

It should be now. Another was sent to your PC at 0436 GMT.

Should I reset the project?

That\'s probably not going to help at this point. You should have another WU to crunch now. Let\'s see how that goes. If that errors out, then more drastic measures are called for. When errors occur, they should be listed in the scrollable Messages tab of the BOINC GUI. Knowing when exactly the WU errored out and whether the PC was doing anything else at the time (virus scan, viewing graphics, etc.) can be halpful in the troubleshooting process.

Just lost another one

core_client_version>5.2.13</core_client_version>
message>WU download error: couldn\'t get input files:
file_xfer_error>
file_name>sulphur_f7ai_000709290.zip</file_name>
error_code>-163</error_code>
error_message>file was not found on server</error_message>
file_xfer_error>

message>

---

BOINC Wiki

Yes, in the early period when I was getting accustomed to the BOINC methodology, several climate WU\'s were downloaded and were getting most of the processing time between them. As I wanted Seti & Rosetta to have a fair go I elected to abort the extra Climate WUs so there was only one climate running 24/7 and the other processor would be splitting the time between Rosetta & Seti.

Later I learned how to suspend a project indefinitely and could have done that initally with Climate but since it showed that it allowed a year to complete, I didn\'t know how long it would really take and I took the abort method figuring that aborted wu would be recycled to another person in queue. That is where the early failures came from.

I\'m suspecting the failure today came when I wanted to convert a DVD from PAL to NTSC and I shut down BOINC to allow no conflicts while that software was running. I then saw Climate & Rosetta were running in the task manager & that shutting off the BOINC manager does not actually stop the WUs from processing so I used the \"end process\" option to stop them. This is about the time I see the error message was received yesterday.

Funny... I was thinking about RARing BOINC so if this happened I would be able to restore it to a pre-failure state. Had I done so I might have been able to complete the climate WU which was well over 20% done. On the other hand completed WU\'s from seti & Rosetta would have ended up being submitted twice had I done that and that would have been a problem so I decided not to RAR the BOINC folder and just assumed all would be OK.

So far the new climate WU has been running for 3Hr 36 min & it\'s at .45% completion. Guess it\'s back to the long haul...

Thank you for your replies & your input.

Gary

---

\"When errors occur, they should be listed in the scrollable Messages tab of the BOINC GUI. \"

As I shut down the computer every so often, it looks like those message tabs are deleted and start anew when the program re-initalizes. Is there any reasonable way to keep a linear trace of the processes where the trail will pick up where it left off when the computer is restarted?

Thanks

---

In the BOINC folder, ther are some std... text files. The one you want is stdoutdae.txt

And when you want to stop BOINC and the apps., go to Commands in the menu and click Suspend. Wait until the app DOES stop, and then click Exit.