I've recently added a new host (3223) to the project and it now has 85,000+ tasks marked as "Not started by deadline - canceled"
For example: http://srbase.myfirewall.org/sr5/result.php?resultid=96766818
Sent: 14 Dec 2015, 14:13:45 UTC
Received 14 Dec 2015, 14:16:09 UTC
Report deadline 15 Dec 2015, 14:13:45 UTC
Returned 14 Dec 2015, 14:16:09 UTC - Not started by deadline - canceled
The host has successfully ran the tasks before (and still is now) but my other hosts don't have the problem so I assume it's some setting that I've got wrong.
The entry says "Aborted by user" but the host is remotely located and I haven't been near it for at least three days. Besides, the error code is "200 (0xc8) EXIT_UNSTARTED_LATE"
Settings for work fetch are currently at 0.1 days with 0.1 days extra and there's only 10 WUs in progress (it's an eight core machine) so I don't think the cache is too big for the WUs to get crunched before the deadline.
It's not a problem for me as the host quite happily crunches WU 24/7 but I don't know what effect it might be having on the project.
/ 
Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7497
Credit: 44,029,375
RAC: 32,894
I've recently added a new host (3223) to the project and it now has 85,000+ tasks marked as "Not started by deadline - canceled"
For example: http://srbase.myfirewall.org/sr5/result.php?resultid=96766818
Sent: 14 Dec 2015, 14:13:45 UTC
Received 14 Dec 2015, 14:16:09 UTC
Report deadline 15 Dec 2015, 14:13:45 UTC
Returned 14 Dec 2015, 14:16:09 UTC - Not started by deadline - canceled
The host has successfully ran the tasks before (and still is now) but my other hosts don't have the problem so I assume it's some setting that I've got wrong.
The entry says "Aborted by user" but the host is remotely located and I haven't been near it for at least three days. Besides, the error code is "200 (0xc8) EXIT_UNSTARTED_LATE"
Settings for work fetch are currently at 0.1 days with 0.1 days extra and there's only 10 WUs in progress (it's an eight core machine) so I don't think the cache is too big for the WUs to get crunched before the deadline.
It's not a problem for me as the host quite happily crunches WU 24/7 but I don't know what effect it might be having on the project.
Can you check the wall clock of this host? The client think that you cannot reach the deadline in time vs. runtime.
/ Reply
Quote
Hi Reb,
Well spotted, at this time, the host thinks the time is 20:48. But it also thinks it's Tuesday the 15th. I must have messed up when I set it originally.
Corrected now, I'll see how it goes.
/ Reply
Quote
Yep,that's fixed it Reb, many thanks. I knew it would be something stupid that I'd done :)
/ Reply
Quote