No problems here.

Yes, on one of my rigs I have (94) completed tasks that are stuck in the "ready to report" state. Tried everything I can think of and they don't process out of the task list. I also posted in that linked thread above with a bit more info. Guess I'll just let it go and see what happens over time. Maybe it will right itself on its owm.

That worked for me (used 40 since I only had 42 task ready). Thank you.

OK, here's what I discovered with one ground observation to start.

I first looked at the "cc_config.xml" file on my Win7 machine (that does not have this issue). I found that the "max_tasks..." setting was ">0<" in that file's options.

Next I went to my Ubuntu rig and first had to figure out where and how to get into the "cc_config.xml" file. For anyone else that may need to know, here's a link that tells you how (assuming you have some basic understanding of how to use the Terminal screen and commands). Pertinent area on that page it Item 4 "Editing BOINC-Client Config File..."

https://wiki.ubuntu.com/BOINC#Editing_BOINC-C...INC_6.2.12_in_Ubuntu_8.10

After getting into the cc_config.xml file, I found that it had very little in options/settings entered into the file. It was a base file with really no options included as statements. So, I had to do some editing and added this to the file:

<options>
<max_tasks_reported>50</max_tasks_reported>
</options>

I restarted Boinc, requested a "Read config file" under the "Advanced" tab.
- Restarted the World Community Grid project.
- Looked at the Tasks list and nothing had happened.
- Forced an "Update" of the project.
- Noted that I now had only (50) of the "ready to report" completed WUs (instead of 90+ WUs)

That told me that the setting of (50) in the cc_config.xml file was simply limiting that list of "ready to report" WUs to 50. I still had a pretty cluttered WU task list with 50 WUs still saying "ready to report".

I also looked in the log and noted the following statement for 46 of the 90-some-odd "ready to report" tasks that may be a concern. It said "Result MCM1_0000466_xxxx_x is no longer usable" for each of the 46 tasks that got lopped off by the change to the cc_config.xml file. The lower case x's were all the unique WU numbers for each of the 46 WUs that reported that status.

So, I went back into the cc_config.xml file and set the "max_tasks" to ">0<" as I had seen it in set my Win7 rig. I repeated the routine above and now all those remaining (50) "ready to report" tasks were cleared from the list. I checked the log again and this time the log indicated "Reporting 50 completed tasks".

Hope this helps someone else and I still don;t know why "out of the blue" this issue surfaced on a dedicated Crunching machine that has been static from any changes.

Many thanks to ca05065 (above) who shared what to do.

Rob, I took your advice and checked my "Results Status" log. I didn't go through and find every one of the 46 WUs, but did spot check several and all were in the "Valid" status. I also sorted the Results list by "Error" status and had nothing come up for that Ubuntu rig. So, thanks for that suggestion and I feel better now that I didn't lose any work.

Unless there is a problem leaving the ">0<" setting in the "max_tasks_reported" setting, I'm gonna leave it that way. That is the way it was set on my Win7 machine and I have never edited the config file (or even attempted to before today). The Boinc install on my Win7 machine must have come with that setting. I'm guessing that ">0<" was the default setting?

Neither of my Ubuntu rigs have much at all in the config file by default. I now have that setting added to the config file on both of my Ubuntu rigs.

Thanks for all the help today!