Report Deadline: Friday Dec 13 1901
17 Apr 2006 18:09:22 UTC
Topic 191094
(moderation:
Ok, so the subject line says it all. Suddenly, all my work units (including SETI units) have changed to a report dealine of Friday December 13th in 1901. Obvously isn't right. So, anyone know how to fix it or what went wrong to cause that change? Any help would be appreciated since I probably won't get credit.
Here is the message I got:
Mon Apr 17 10:34:51 2006|Einstein@Home|Result z1_1101.0__748_S4R2a_0 is 134768.26 days overdue.
Mon Apr 17 10:34:51 2006|Einstein@Home|You may not get credit for it. Consider aborting it.
Mon Apr 17 10:34:51 2006|SETI@home|Result 01se99aa.26654.6418.1028410.1.172_4 is 134765.12 days overdue.
Mon Apr 17 10:34:51 2006|SETI@home|You may not get credit for it. Consider aborting it.
Here is a screenshot:
I am assuming this is related to my machine since it is affecting both SETI and Einstein.
Thanks
Report Deadline: Friday Dec 13 1901
)
This was reported before. As far as I remember this was solved by a simple reboot. The deadlines only *appear* to be in 1901, but no need to worry. The correct deadlines are kept in the server database. (Look here.)
You don't need to abort the WUs.
Michael
Team Linux Users Everywhere
Why this happens is because
)
Why this happens is because the BIOS date got reset back to default. This happens because of a dying BIOS battery, surge, or something else, like a rogue program.
If the data will finish before the server deadline, then crunch away. You will just stay in EDF mode until they are done. Doesn't hurt anything.
Thanks for the reassurance.
)
Thanks for the reassurance. I will try a reboot and see if that fixes things.
Thanks again!
I note that the erroneous
)
I note that the erroneous date is exactly 2^31 seconds before the Internet-time epoch of 1970 January 1.0, after applying a five-hour time-zone adjustment. No coincidence, I think!