From time to time, some impossible time to crunch WU apears, today i see at least 2 of them for CPU.

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

both WU where DL on Fev 09 at 02:13 and reported with a time limit exceded error in Feb 10 at 00:21 and where resended to a new host after that.

What it´s wierd is why the server sends a WU with that impossible time to crunch? Less than 1 day... Others WU sended to CPU this day has a expiration date in the middle of March, not only few hrs.

Any ideia why that happening and a way to prevent that?

---

The field is "Time reported or deadline". The time you see is not the original deadline time, but the timestamp of when they were marked as timed out.

This most often happens with VLAR tasks that were assigned to the CPU but then the client did not download. Then on next work request GPU requested work and as VLAR are not allowed to GPU they were be flagged as "timed out" with the current timestamp. I don't recall the condition where this occurs for a non VLAR task at the moment.
That machine also has an AP that looks to have gotten the similar treatment.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

...Then on next work request GPU requested work and as VLAR are not allowed to GPU they were be flagged as "timed out" with the current timestamp. ...

Thanks Hal, i allready know that, but thats exactly what i can´t understand, first they are CPU WU (who have no problem with VLARS) not GPU WU, and the WU was reported as expired after 22hrs not in the next work request (few minutes before). So something else must be in place here.

---

As I said I currently only recall the VLAR issue that does this, but there could be a dozen other conditions where this happens.
If you have the logs in your stdoutdae.txt or stdoutdae.old for 10 Feb 2014, 0:21:29 UTC then it might help point to the cause.

Edit: Doing some digging in the threads.
This also occurs when:
There is a ghost task & for whatever reason the server decides not to send it.
There was a "transient HTTP error" or other connection issue.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I had a couple that timed out in less than an hour.

---