Another `ghost` wu Completed but not on my computer anymore; http://climateapps2.oerc.ox.ac.uk/cpdnboinc/result.php?resultid=19944779

So feel free to delete / resend..

It seems the model I started the thread with is no longer "In progress" but "Abandoned".

One can see the following status:
Received 25 Nov 2016, 21:49:33 UTC (though completed on 7 Oct ) so I have no idea what it means or what caused it. I hope it reached the researchers.

I also looked at some of the other WAHs reported here and they seem to be still in progress. Mystery to me it is.

Also, both Run time and CPU time are empty in the model page, and 0.00 in the Tasks list.
Even though all of the trickles seem to be there, and it was given credits.

I too am puzzled.

Mine is still showing as in progress. despite all the trickles being there and the credit granted. - Prompted to check by the previous posts.

http://climateapps2.oerc.ox.ac.uk/cpdnboinc/result.php?resultid=19976711

Dave

I have 3 hadam3p_eu WUs that are gone from BOINC's task tab but are still in progress on the web:

hadam3p_eu_ltcl_201611_3_482_010804528_0
hadam3p_eu_luo8_201611_3_482_010806243_0
hadam3p_eu_lupx_201611_3_481_010802680_0

One more WU (wah2_pnw25_c158_200312_48_485_010813435_0) has finished and uploaded, but still in progress.

I've got a model that I reported as abort, long ago. But the website says still in progress:
https://www.cpdn.org/cpdnboinc/result.php?resultid=17525647

This seems to be a systemic problem with CPDN.

I did report this problem late last year, but nothing could be found that was wrong.
I'll ask again next week.

Interestingly, the one I had now has the status of, "Abandoned" instead of, "in progress."However when searching for particular tasks that isn't available as a way of searching, you have to click on the, "error" tab to find tasks listed as abandoned. Too late to look on my computer now but I wonder if there was a problem with the upload of the final zip file or something?

BOINC requires that the BOINC client report the completion of tasks before they are marked as complete to the server in order to prevent the server from trying to process tasks whose uploads are not yet complete (e.g. the internet connection failed during the middle of uploading one of the files of the result). Have you verified that the work unit is not sitting in your list of tasks waiting to be reported? If it is, then you could click the update button after selecting the project in the projects tab to force the BOINC client to transmit the completion message. Otherwise, you could wait for it to automatically contact the project, and the completion message will be transmitted then. If the task is not in the project tab and there are no more tasks for the project in the queue, you could detach from and reattach to the project to cause the server to mark the task as abandoned, so the work unit can be reprocessed by another computer. Doing this while there are other Climateprediction.net tasks left in the queue will cause you to lose progress in those tasks, so you should set the project to no new tasks mode to ensure that your computer does not get any work and that your computer could drain the queue of remaining tasks. You will still get credit for the lost task due to the trickles for the lost task that were reported.

Thanks Jesse,
but I've been closely monitoring all the tasks reported here, so they all finished nicely in BOINC and has been reported as finished (log checked). These has been on different machines WIN7, ubuntu with WINE so my guess is the problem is not client side.

Workunit finished uploaded and reported but still listed as in progress on web

https://www.cpdn.org/cpdnboinc/result.php?resultid=20116340

---

Kevin

OK, this is a bit much. The reason given back in December was "it may have been the transitioner not running". (There was nothing in the server logs.)

But now it seems to be ongoing, so another email.

Just listing mine as well.

hadam3p_eu_lul3_201611_3_482_010806130_0

hadam3p_eu_lue5_201611_3_482_010805880_0

hadam3p_eu_lxkp_201611_3_482_010810004_0

I've just cleaned mine by detaching and re-attaching again. I now have only one orphaned hadcm3n_7jft_1980_40_008436476_2 that does not fit the category of WUs reported here and with a deadline 2023.

I've just cleaned mine by detaching and re-attaching again. I now have only one orphaned hadcm3n_7jft_1980_40_008436476_2 that does not fit the category of WUs reported here and with a deadline 2023.

If I remember correctly, the WU’s that were sent out with deadlines of 2023 were “no resubmission” WU’s that somehow slipped back into the que and were sent out by mistake.

---

The -2 at the end of the task number indicates its the third issue of this task and therefore probably the last. First issue would be -0 and second issue -1. Interestingly looking at the model its initial incarnation - (back in 2013!) - is labelled as "didn't need".

The -2 at the end of the task number indicates its the third issue of this task and therefore probably the last. First issue would be -0 and second issue -1. Interestingly looking at the model its initial incarnation - (back in 2013!) - is labelled as "didn't need".

Yeah, I got this one in 2013, the machine was disconnected and I drag this one for some years.

"didn't need" was intended to indicate to the server that it wasn't to be re-issued. But that didn't work.

A deadline of 2023 was another attempt to stop re-issues. The date was changed after the first attempt was reported. It'll be a while before that one shows up again.

Got another one:-(

https://www.cpdn.org/cpdnboinc/result.php?resultid=20117981

I have suspended the WU at 99.700%, so still have files on computer.

---

Kevin