WU Timed Out After 7 Hours?

Join PrimeGrid

Read our rules and policies.
Download, install and run the BOINC software used by PrimeGrid.
When prompted, enter the URL:
http://www.primegrid.com/
Select which subprojects to run via the PrimeGrid Preferences.

If you are not using graphics enabled BOINC client, you may use manual registration form.

Author

Message

Eric Nietering
Send message
Joined: 30 Mar 09
Posts: 12
ID: 37742
Credit: 883,341,255
RAC: 336,253

Good afternoon,

I was just scanning through my task history, and came across something that seems odd. For this WU: http://www.primegrid.com/workunit.php?wuid=398122810, I got a timeout error after less than 7 hours. These tasks take about 10 hours to run on that PC. My event log doesn't go back far enough to see if I actually completed and returned that task, but I probably did. My computer very rarely have errors, and they're generally validate errors, not timeout errors. At that time I was running only PG, and I think only SR5 tasks, to help with the cleanup.

Any ideas why I might have received a timeout error after less than 7 hours on a 15 day task? Let me know if I can provide any more info that might be useful.

Thanks,
Eric

ID: 78482 |

Michael Goetz

Volunteer moderator
Project administrator

Send message
Joined: 21 Jan 10
Posts: 13634
ID: 53948
Credit: 281,155,805
RAC: 20,342

Good afternoon,

I was just scanning through my task history, and came across something that seems odd. For this WU: http://www.primegrid.com/workunit.php?wuid=398122810, I got a timeout error after less than 7 hours. These tasks take about 10 hours to run on that PC. My event log doesn't go back far enough to see if I actually completed and returned that task, but I probably did. My computer very rarely have errors, and they're generally validate errors, not timeout errors. At that time I was running only PG, and I think only SR5 tasks, to help with the cleanup.

Any ideas why I might have received a timeout error after less than 7 hours on a 15 day task? Let me know if I can provide any more info that might be useful.

Thanks,
Eric

We're aware of a scenario where this can happen when the clock on your computer is set wrong. If the clock is set far enough into the future, the BOINC client thinks the task has timed out and instead of running it will report it back to the server as "timed out".

That's the only reason I'm aware of that can cause this particular error/

____________
My lucky number is 75898⁵²⁴²⁸⁸+1

ID: 78483 |

Eric Nietering
Send message
Joined: 30 Mar 09
Posts: 12
ID: 37742
Credit: 883,341,255
RAC: 336,253

Thanks for the information Michael. According to my event log, the windows time sync service had some sort of issue on 6/30. Pretty weird though, I don't remember the clock being way off.

I guess that must be what happened. Thanks for the quick reply!

Eric

ID: 78484 |

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other