I think BOINC still has some problems as it shows that I have 52 Active tasks and I only show 38 active tasks in both BOINC Manager and Boinc Tasks or am I just looking at something wrong? http://setiathome.berkeley.edu/results.php?hostid=7451398
Sorry about posting this in another BOINC thread, I have asked that it be removed from there.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Is this Boinc problem or a Seti problem, me thinks Seti.

---

The excess of apparent over real active tasks are known as "ghosts" - I dread to think how many I've got....

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Ghosts, I had forgotten all about them.
Thanks for reminding me of their existence.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

It's a shame the 'Resend Lost Tasks' feature is kept disabled now. You either have to wait for the tasks to Time Out and ruin your Consecutive Valid Task number, or take matters into your own hands and trigger a Resend Event. The trigger isn't that difficult, and doesn't seem to cause any harm. All you have to do is convince BOINC to send the same result twice, and Boom, all your Lost Tasks are resent. I got mine back last night...

I am not sure I know how to do that??

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Well, the discussion begins here, http://setiathome.berkeley.edu/forum_thread.php?id=77597&postid=1697263#1697263, there are a few comments about it. Of course, editing the state file is very unforgiving and could result in all tasks being lost, so, it's best to wait until your cache is low. Right Now would be a good time for some people. There is a way you can accomplish the task without any editing and would probably result in very little risk, but as always, any Extreme Tinkering you attempt is done so at Your Own Risk.

If it were me, I'd probably wait until I had a task ready to report and a few minutes left before scheduled reporting. That would give you time to copy the two client_state files to a different directory and then Hit the Update button to report the task manually after which you would Quit BOINC as soon as the task was reported. Simply replace the two state files with the copied files and restart BOINC. The task is back and gets reported as soon as BOINC starts. Then the Lost Tasks are Resent...if you have your preferences set to receive them and have room in your cache.

I think I will leave well enough alone for the time being. I am leaving for vacation and had little time to have things go wrong right now.
Thanks and I will look into it when I get back.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Thanks, Tbar!
This forcing a resent of lost tasks works great!

If it were me, I'd probably wait until I had a task ready to report and a few minutes left before scheduled reporting. That would give you time to copy the two client_state files to a different directory and then Hit the Update button to report the task manually after which you would Quit BOINC as soon as the task was reported. Simply replace the two state files with the copied files and restart BOINC. The task is back and gets reported as soon as BOINC starts. Then the Lost Tasks are Resent...if you have your preferences set to receive them and have room in your cache.

Much appreciated!

Quick check before I leave.....and the lost tasks seem to have been taken care of as all numbers now agree.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Not jet.
I think, i have to repeat the procedure a few times. But i have 20 out of about 100 back, some have expired already.
I may have to do this for each type of task (gpu, cpu), but i don't know jet.