False "abandoned" tasks

I have an issue with one computer for which 55 tasks were wrongly reported as "abandoned" on 18 Feb 2013, 15:06:59 UTC, though the completed ones were regularly reported during the black out period. The others are still being executed. One exemple is:

http://setiathome.berkeley.edu/result.php?resultid=2836266935

Anyway to correct the situation?

JL

Not your computer's fault, it's seti@home.
Nothing you can do on your side... except abort those tasks on your computer, because even if you complete them, they'll get ignored.
This happened to me 3 times already, starting after problems with the scheduler timing out began.
Not so much set & forget anymore... :(
____________

Thanks Khangollo.

JL

This occurred to one of my machines two days back but I only noticed it today. Since I access it via remote desktop, it is really a painful task to check individual tasks to see which have been abandoned but still being processed by the machine. Is resetting a good option to clear this issue? And will the tasks be re-downloaded after the reset?
______________

Yes, reset the project, Only the tasks that haven't been abandoned will be resent, 20 at a time,

Claggy

All my hosts have been "abandoning" all their tasks in the last days... one of them did it twice just today...

This is not funny... when the issue is that the project can't supply work my hosts can help another project or in the worst case just sit idle and save electricity... But with this issue Im wasting a lot of energy which goes directly to the drain as there is no usefull science neither credits for the electricity paid doing those tasks...

Any idea why is this happening? Is there something we can do on client side (other than hire somebody to babysit the hosts or opt-out of SETI)?

TBH, If it's something on server side, I think, it should be fixed ASAP... besides me wasting money, I think that thousands of abandoned tasks and a continuos download of already downloaded tasks is not good for the server's load neither for the saturated pipes...
____________

In the host that did it twice today, the last batch of abandoned where at 19:37:04 (UTC) Im at -3 UTC so it was at 16:37:04 my time, this time matches (more or less) a RPC and there is nothing unusual in the log... (there are a lot of "project comunication failed" entries, but those are related to the downloads and are a very common, frequent and consistent issue downloading SETI WUs...)

It happened again, in another host, for the second time today.
As in my previous post nothing unusual on the event log, but there is a RPC answer (just after the "abandoning event") saying that the last RPC was too recent: 66 Secs, when in fact the previous one was more than 5 mins before (18:27:02 and 18:32:27 makes 325 seconds) and both were normal updates automatically triggered by BOINC...

Something smells really bad... it seems like the scheduller is kind of confusing the RPC of different hosts ... (or having halucinations... they should stop smoking things in the lab ... :b )
____________

That could conceivably happen if two different machines were reporting in and claiming to have the same HostID.

You haven't ever set up a new machine by cloning a BOINC data directory from another machine, have you?

When a task is marked 'abandoned', there's a server timestamp for the event on the website task list.

If you convert that to local time, can you match it against anything unusual in your boinc message/event log?