| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: Incredibly Quick Deadline |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 14
|
|
| Author |
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges: 
|
Just an observation this morning. Upon checking my results in SCC I saw I am getting a larger than normal number of resends. In checking somewhat randomly through the resends I noted there appeared to be a disproportionate number listed as "Detached". Without exception they all listed Cent OS as the operating system. Could this be the same machine(s) which have been giving the very short running times and the quick due dates ?
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges: 
|
Cyclops:
We are looking into this and will comment a follow up if we find anything that can help you avoid this issue in the future. Sorry Cyclops, The issue is not about avoiding it nor trying to avoid it; the problem is that the Due Time is incorrect. Adri |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
It looks like something for the good has been done to the Due times in tasks that were distributed to certain CentOS systems. Here are some examples:
----------------------------------------workunit 310789704 MCM1_0199299_4175_0 Linux Debian Valid 2023-05-26T03:06:33 2023-05-27T11:52:04 5.04/5.04Details: --------------------------------------------------------------------------------------------------------------------------------------- MCM1_0199299_4175_1 CentOS Linux Detached 2023-05-26T03:39:55 2023-05-26T03:46:54 0.00/0.00 workunit 314048004 MCM1_0199580_9627_0 Linux Ubuntu Valid 2023-05-31T14:55:07 2023-06-01T02:29:35 3.55/3.57Details: --------------------------------------------------------------------------------------------------------------------------------------- MCM1_0199580_9627_1 CentOS Linux Detached 2023-05-31T14:56:21 2023-05-31T14:57:28 0.00/0.00 workunit 312454344 MCM1_0199456_2181_0 CentOS Linux Detached 2023-05-29T02:39:35 2023-05-29T02:41:23 0.00/0.00Details: --------------------------------------------------------------------------------------------------------------------------------------- MCM1_0199456_2181_0 CentOS Linux Detached 2023-05-29T02:39:35 2023-05-29T02:41:23 0.00/0.00 Close enough to exactly 6 days.  Adri [Edit 1 times, last edit by adriverhoef at Jun 1, 2023 3:27:38 PM] |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
Thanks to three Server Aborted tasks …:
workunit 606633129 MCM1_0225568_2014_0 Linux Debian Valid 2024-10-02T09:25:09 2024-10-02T21:03:00 2.34/2.35Details: --------------------------------------------------------------------------------------------------------------------------------------- MCM1_0225568_2014_0 Linux Debian Valid 2024-10-02T09:25:09 2024-10-02T21:03:00 2.34/2.35 workunit 606633157 MCM1_0225571_1614_0 Linux Debian Valid 2024-10-02T09:25:09 2024-10-04T10:15:31 4.14/4.94Details: --------------------------------------------------------------------------------------------------------------------------------------- MCM1_0225571_1614_0 Linux Debian Valid 2024-10-02T09:25:09 2024-10-04T10:15:31 4.14/4.94 workunit 606633161 MCM1_0225557_2062_0 Linux Debian Valid 2024-10-02T09:25:09 2024-10-02T23:24:31 2.34/2.35Details: --------------------------------------------------------------------------------------------------------------------------------------- MCM1_0225557_2062_0 Linux Debian Valid 2024-10-02T09:25:09 2024-10-02T23:24:31 2.34/2.35 … I discovered 68 more tasks — all of their names ending in _2 — in my queue. Looking at their workunits — all tasks that you receive (from the BOINC server) are part of a workunit — they all had a short Due Time for one of my wingmen: workunit 606634157 | workunit 606634162 | workunit 606634165 | workunit 606634169 | workunit 606634206 | workunit 606634209 | workunit 606634210 workunit 606644410 | workunit 606644414 | workunit 606644418 | workunit 606644422 | workunit 606644426 | workunit 606644430 | workunit 606644439 workunit 606644443 | workunit 606644455 | workunit 606645847 | workunit 606645851 | workunit 606645854 | workunit 606645859 | workunit 606645863 workunit 606645867 | workunit 606645878 | workunit 606645882 | workunit 606645886 | workunit 606645890 | workunit 606647277 | workunit 606647279 workunit 606647281 | workunit 606647283 | workunit 606647285 | workunit 606647287 | workunit 606647289 | workunit 606647295 | workunit 606647297 workunit 606647301 | workunit 606647307 | workunit 606647309 | workunit 606647311 | workunit 606647313 | workunit 606647315 | workunit 606647319 workunit 606647321 | workunit 606647323 | workunit 606648147 | workunit 606648163 | workunit 606648173 | workunit 606648207 | workunit 606663682 workunit 606663686 | workunit 606663690 | workunit 606663710 | workunit 606663721 | workunit 606663725 | workunit 606663729 | workunit 606663733 workunit 606666118 | workunit 606668557 | workunit 606671376 | workunit 606671380 | workunit 606691680 | workunit 606691692 | workunit 606691700 workunit 606695280 | workunit 606947767 | workunit 606947771 | workunit 606947775 | workunit 606947779 How do we know that it is only one specific wingman? Because its OS-Version and its Due Times are quite specific: 19 Due Time: 2024-10-03T05:06:50+0000(that's the final output of this command: grep -E OS-\|Due | sort | uniq -c) Adri |
||
|
|
|