Eric posted in News that the old data conversion did not go well and there won't be any work till tomorrow when they can get more work from GBT.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

A very fresh new splitter underway 03fe18aa

A very fresh new splitter underway 03fe18aa

And it's splitting VLARs.

---

Grant
Darwin NT

WoW..Blink and miss them :(

And now Milky Way has a dbase error. Had to kick in a backup project to the backup project this morning

---

~Chris

All the cache gone. And still have 149 WU "in progress" must be Ghosts. Anyone knows who i retrieve them?

---

Ghost recovery protocol. 20 tasks at at time.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

New work is up from both GBT and AO.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

New work is up from both GBT and AO.

I saw that too. I wish I was at home to jump start SETI again. I kicked in Milky way and WCG on at least 1 PC.

---

~Chris

WoW..Blink and miss them :(

. . Lots of hungry crunchers out there currently in starvation mode ...

Stephen

:(

All the cache gone. And still have 149 WU "in progress" must be Ghosts. Anyone knows who i retrieve them?

. . As follows;

. . Set project to No New Tasks

. . Disable network access and wait for a group of completed tasks to accumulate (enough to give you time to run through this procedure, the faster your upload speed the more you will need)

. . Open windows to file transfer, event log and preferences

. . Re-enable the network access and monitor the uploads in the file transfer and event log windows. When the last file has uploaded and the acknowledgement has appeared in event log, but BEFORE the work has been reported disable the network access again. This timing is critical as is the first step of setting NNT. I have the option to disable network access set in advance so I only need to click OK.

. . Shut down Boinc and wait a short period.

. . Restart BOINC, set manager to allow New Tasks. All the completed tasks should show under the tasks tab as ready to report. Re-enable the network and watch. You should get 20 resent tasks (they will show in event log as a list of resends).

. . For large numbers of ghosts this will have to be repeated until all are recovered.

. . If you have no tasks to upload then I don't know how you can trigger the resends.

Stephen

Hope that helps.

We already hashed it out with Juan. Without any tasks to report (0 tasks in progress), the ghost recovery protocol doesn't work.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

We already hashed it out with Juan. Without any tasks to report (0 tasks in progress), the ghost recovery protocol doesn't work.

. . Sorry I didn't see that convo. Yes that is a problem when your cache is empty. It would be nice if there were a work around for that.

Stephen

?

We already hashed it out with Juan. Without any tasks to report (0 tasks in progress), the ghost recovery protocol doesn't work.

A detach and reattach might as well be in order to release them then if this is still the case.

Cheers.

Yes, that would have been the proper thing to do with no tasks on board. But there is always the possibility of generating a new host ID, which I know that Juan is not going to want. He worked hard for his current #2 position in Top Hosts.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

He worked hard for his current #2 position in Top Hosts.

Yes that is something i proud to be.
Not worry the ghosts will clear eventually, i have the wrong idea that was easy to do the clear manually.

---

Actually, it's much easier than some would indicate. Just before a task finishes hit the Update to set the counter to 5 minutes. As soon as the task finishes and uploads, copy client_state.xml & client_state_prev.xml and paste them to a different directory, such as home. Immediately hit update to report the completed task and Quit BOINC as soon as it reports the task. Then move the files you copied to home back to the BOINC folder overwriting the files there. Start BOINC, the completed task will be reported again triggering the 20 task resend. That's all there is to it. It's best if you have the checkpoint set so the GPU tasks will start from the beginning instead of being resumed at a minute or two. CUDA tasks don't like being resumed partly run. I usually remove the GPU tasks from the Active Tasks list so they definitely restart from the beginning, I don't like Invalids. When tasks are finishing every couple of minutes the process moves along quickly. I've done it hundreds of times, mostly to have the server send the tasks back assigned to a different device...after purposely making them a Ghost.

Of course, you Do have to have room in the cache you want the tasks to go to.

Thanks for the instructions TBar. I will have to bookmark this post as I can see it is useful for special occasions.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Glad to see not only do we have new work, but it's back to the previous longer GBT WU processing times. That'll help reduce the load on the servers, and make the work last that much longer before it all gets split & crunched.

---

Grant
Darwin NT

Voyager??? or V'ger....


Edited for spelling. Thanks Keith

---