Greetings!!
I have a WU that is due today. The Boinc status updated to 141 days remaining.( It just changed to 118 days remaining.

Name
corona_RdRp_v2_sidock_01431602_r2_s-20_0
Elapsed
3days 2 hours 60 minutes...
Deadline
Saturday 09March 11:02PM EST
(Note: all other deadlines are listed in EDT,

I ***assume*** this relates to:
From sidock website
Task 81010407
Work Unit 52600263
Sent 4March 4:12 UTC
Deadline 10March4:12 UTC
Note: The deadlines do not match
Computer 55116

How abnormal is this?
I did a cpu restart for OS updates. I **assume** that the checkpoints for Linux SiDock applications work correctly.


Bad assuptions?
Other thoughts?
I was going to let BOINC or the SI server issue an abort/timeout so that the task information can be complete.


I think I found the WU in slot 6.
docking_out.log had two interruptions
first time it restarted at present -1 WU.
second time, it restarted at record 1

docking_out.log is 125996 bytes at present.

Shall I try to get other info from /var/lib/boinc-client?


THANKS,
Jay
PS. Days remaining shifted to 101.

Note: all other deadlines are listed in EDT

That’s because they fall after your clocks go forward tomorrow morning.

I **assume** that the checkpoints for Linux SiDock applications work correctly

AFAIK, CmDock on Linux doesn’t have the same checkpointing issue as on Windows (which, incidentally, is not that checkpoints aren’t made; just that BOINC doesn’t know about them) – but it does still have the restarting problem where (even with successful checkpointing) tasks that get stopped and restarted sometimes go back to the beginning. In this latter case BOINC’s measurement of the task’s progress rate will get confused (because it is tracking CPU time already used, but the task has gone back to 0% complete), which is most likely what leads to the enormous predicted time remaining.

I was going to let BOINC or the SI server issue an abort/timeout

AFAIK, neither your local BOINC nor the SiDock server will abort an already-started task just because it is predicted to miss (or even if it has missed) its deadline. You can still get credit for reporting it late (even, I think, if a resend goes out and gets back before yours completes). But if you want to abort the suspect task yourself and let the server resend the work unit to another host, don’t worry about it. It is just one of the millions that SiDock is running; the project will cope… :-⁠)

PS. Days remaining shifted to 101

The longer the task runs, the better BOINC’s estimate of its ‘speed’ gets. The predicted time remaining will gradually correct itself.

Thanks!!

Jay