Weird Time Limit WU

Message boards : Number crunching : Weird Time Limit WU
Message board moderation

To post messages, you must log in.

AuthorMessage
juan BFP Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 16 Mar 07
Posts: 7132
Credit: 411,752,896
RAC: 280,794
Panama
Message 1908434 - Posted: 22 Dec 2017, 13:23:43 UTC
Last modified: 22 Dec 2017, 13:30:01 UTC

Just look and in Dez 19 my host receive a set of few weird expiration time CPU WU

An example of one: https://setiathome.berkeley.edu/result.php?resultid=6245493793

Received: 19 Dec 2017, 12:29:16 UTC
Expired: 19 Dec 2017, 23:41:11 UTC

Less than 12 Hrs to expire after they where received.

Something breaks on the scheduler? Or is in my host? Do I need to do anything to avoid this?
ID: 1908434 · Report as offensive
Profile Brent Norman Special Project $250 donor
Volunteer tester

Send message
Joined: 1 Dec 99
Posts: 2394
Credit: 273,184,020
RAC: 686,007
Canada
Message 1908445 - Posted: 22 Dec 2017, 17:00:55 UTC - in response to Message 1908434.  

Sometimes the server just screws up. I have seen deadlines of just a few minutes, but that this is rare to occur.
ID: 1908445 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 5566
Credit: 385,800,697
RAC: 1,034,189
United States
Message 1908447 - Posted: 22 Dec 2017, 17:22:26 UTC - in response to Message 1908445.  

Sometimes the server just screws up. I have seen deadlines of just a few minutes, but that this is rare to occur.

I always thought it was when the server screws up and sends a Arecibo VLAR to a Nvidia GPU. Those with a Sent time and Deadline time within a few minutes of each other which results in the expected task not completed by deadline.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1908447 · Report as offensive
Profile Jeff Buck Special Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1908450 - Posted: 22 Dec 2017, 17:30:00 UTC - in response to Message 1908434.  

Just look and in Dez 19 my host receive a set of few weird expiration time CPU WU

An example of one: https://setiathome.berkeley.edu/result.php?resultid=6245493793

Received: 19 Dec 2017, 12:29:16 UTC
Expired: 19 Dec 2017, 23:41:11 UTC

Less than 12 Hrs to expire after they where received.

Something breaks on the scheduler? Or is in my host? Do I need to do anything to avoid this?
It looks like those were sent about a half hour before the Tuesday outage, but didn't finish downloading before the outage started, for some reason. When the servers came back up 11 hours later, they immediately decided that they'd waited long enough for the downloads to complete and just cut them off. Your Event Log might show why they didn't manage to download in that half hour before the outage, but it may not be anything you could have done anything about.
ID: 1908450 · Report as offensive
Profile Jeff Buck Special Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1908451 - Posted: 22 Dec 2017, 17:32:38 UTC - in response to Message 1908447.  

I always thought it was when the server screws up and sends a Arecibo VLAR to a Nvidia GPU.
I've only seen that happen when I'm recovering "ghosts", but then they get marked as "Abandoned" rather than "Timed out".
ID: 1908451 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 5566
Credit: 385,800,697
RAC: 1,034,189
United States
Message 1908469 - Posted: 22 Dec 2017, 19:10:10 UTC - in response to Message 1908451.  

I always thought it was when the server screws up and sends a Arecibo VLAR to a Nvidia GPU.
I've only seen that happen when I'm recovering "ghosts", but then they get marked as "Abandoned" rather than "Timed out".

Yes, I see that as the most common scenario. But I have also seen these tasks downloaded in a normal scenario in the log and then only a few minutes later reported as timed out. Rather rare but I have seen it a couple of times on all machines over the years. I just put it down to the servers having a brain fart.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1908469 · Report as offensive

Message boards : Number crunching : Weird Time Limit WU


 
©2018 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.