Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: CEP2 beta for windows - Version 6.25 |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 311
|
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The validator is awake
|
||
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: |
The validator is awake Yes, it is albeit ex post facto. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
At any rate I don't allow my quad to run more than 2 concurrent... What are good ways to enforce such limits other than manually? I limited DDDT2 by putting one core onto CEP2 andLinux, which worked fine. I can of course limit the total # cores BOINC gets on the windows side, but that's not an appealing option! Currently I use suspend/resume to force at least one core to be doing something other than this Beta, but that's more time & attention than I can spare for long. Better methods? (Not experienced at micro-managing a host, and what do people with host farms do? even with boinctasks or boincview that's a lot of work!) |
||
|
jasm580
Senior Cruncher USA Joined: Dec 20, 2007 Post Count: 157 Status: Offline Project Badges: |
What are good ways to enforce such limits other than manually? You might try adjusting how much memory your client(s) are allowed to use for crunching. It might limit CEP2 but still allow other in. edit: fix quotation markers
-Jasm
----------------------------------------[Edit 1 times, last edit by jasm580 at Sep 16, 2010 3:06:29 AM] |
||
|
evilkats
Senior Cruncher USA Joined: May 4, 2007 Post Count: 162 Status: Offline Project Badges: |
At any rate I don't allow my quad to run more than 2 concurrent... What are good ways to enforce such limits other than manually? I limited DDDT2 by putting one core onto CEP2 andLinux, which worked fine. I can of course limit the total # cores BOINC gets on the windows side, but that's not an appealing option! Currently I use suspend/resume to force at least one core to be doing something other than this Beta, but that's more time & attention than I can spare for long. Better methods? (Not experienced at micro-managing a host, and what do people with host farms do? even with boinctasks or boincview that's a lot of work!) I think for now babysitting clients like you and I do is the only way to get desired project ratios. I have heard that a centralized managemenet on a profile level is in development by WCG. |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Have 6 Betas, one PV (currently), 4 IP, and one ERROR... Result Name: BETA_ E200366_ 581_ A.24.C19H12N2OS2.266.2.set1d06_ 1-- <core_client_version>6.10.56</core_client_version> <![CDATA[ <message> WU download error: couldn't get input files: <file_xfer_error> <file_name>beta11.qcaux.zip</file_name> <error_code>-119</error_code> <error_message>MD5 check failed</error_message> </file_xfer_error> </message> ]]> PV was on a PM 770 (Pentium Mobile 2.13 MHz), WinXP SP3, estimated runtime was ~12.5 hrs, actual runtime 8.65 hrs All others are on a Q8300 (Core 2 Quad 4*2.5 MHz), Win Vista, estimated runtime ~7 hrs This MD5 flag suggest the result did not download or store correctly on the host and failed the verification.
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All! |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
My first Beta completed in 0.77 hours and is PV? Result Log Result Name: BETA_ E200362_ 255_ A.24.C18H13N3S2Si.71.0.set1d06_ 1-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [17:53:10] Number of jobs = 16 [17:53:10] Starting job 0,CPU time has been restored to 0.000000. [17:54:50] Finished Job #0 [17:54:50] Starting job 1,CPU time has been restored to 86.143752. [17:59:35] Finished Job #1 [17:59:36] Starting job 2,CPU time has been restored to 359.753906. Application exited with RC = 0x1 [18:40:24] Finished Job #2 [18:40:24] Starting job 3,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #3 [18:40:24] Starting job 4,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #4 [18:40:24] Starting job 5,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #5 [18:40:24] Starting job 6,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #6 [18:40:24] Starting job 7,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #7 [18:40:24] Starting job 8,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #8 [18:40:24] Starting job 9,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #9 [18:40:24] Starting job 10,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #10 [18:40:24] Starting job 11,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #11 [18:40:24] Starting job 12,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #12 [18:40:24] Starting job 13,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #13 [18:40:24] Starting job 14,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #14 [18:40:24] Starting job 15,CPU time has been restored to 2785.085853. [18:40:24] Skipping Job #15 called boinc_finish </stderr_txt> ]]> BETA_ E200362_ 255_ A.24.C18H13N3S2Si.71.0.set1d06_ 1-- 625 Pending Validation 9/15/10 08:52:52 9/15/10 23:25:11 0.77 19.0 / 0.0 What's up with that? At step 3 it seemed there was nothing there of interest, so it cycled to the end. The Application exited with RC = 0x1 is one of these that will eventually go into the "benign log lines" summary. Interesting for the scientists, not for us mortals. Someone asked in another post, what happens to these skipped/missed steps? Recorded in the database. The scientist said they take ALL information produced, be it a short or long run.
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All! |
||
|
X-Files 27
Senior Cruncher Canada Joined: May 21, 2007 Post Count: 391 Status: Offline Project Badges: |
Here's a new one: "All pipe instances are busy. (0xe7) - exit code 231 (0xe7)". Got 2 of them on the same host. ERR_CRYPTO???
----------------------------------------BETA_ E200365_ 741_ A.24.C19H12N2OS2.114.2.set1d06_ 1-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> All pipe instances are busy. (0xe7) - exit code 231 (0xe7) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. Error could not extract qcaux. called boinc_finish </stderr_txt> ]]> ******** BETA_ E200366_ 020_ A.24.C19H12N2OS2.165.1.set1d06_ 1-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> All pipe instances are busy. (0xe7) - exit code 231 (0xe7) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. [15:41:09] Number of jobs = 16 [15:41:09] Starting job 0,CPU time has been restored to 0.000000. [15:43:12] Finished Job #0 [15:43:12] Starting job 1,CPU time has been restored to 111.821517. [15:48:47] Finished Job #1 [15:48:47] Starting job 2,CPU time has been restored to 422.279107. Application exited with RC = 0xc000013a [17:08:29] Finished Job #2 [17:08:29] Starting job 3,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #3 [17:08:29] Starting job 4,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #4 [17:08:29] Starting job 5,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #5 [17:08:29] Starting job 6,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #6 [17:08:29] Starting job 7,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #7 [17:08:29] Starting job 8,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #8 [17:08:29] Starting job 9,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #9 [17:08:29] Starting job 10,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #10 [17:08:29] Starting job 11,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #11 [17:08:29] Starting job 12,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #12 [17:08:29] Starting job 13,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #13 [17:08:29] Starting job 14,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #14 [17:08:29] Starting job 15,CPU time has been restored to 4933.890427. [17:08:29] Skipping Job #15 called boinc_finish Error reading job description file A.24.C19H13N3S2.72.2.jobs </stderr_txt> ]]> |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
... [18:40:24] Skipping Job #3 ... At step 3 it seemed there was nothing there of interest, so it cycled to the end. The Application exited with RC = 0x1 is one of these that will eventually go into the "benign log lines" summary. Interesting for the scientists, not for us mortals. I have two of these as well, BETA_ E200366_ 836_ A.24.C19H12N2OS2.67.2.set1d06_ 1-- and BETA_ E200366_ 598_ A.24.C19H12N2OS2.269.4.set1d06_ 0--, both skipping job #3...#15, exited with RC = 0x1 whilst computing job #2, runtime was 1 hr for both |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
and a third one, skipping job #3...#15, but now with Application exited with RC = 0xc0000005
BETA_ E200366_ 735_ A.24.C19H12N2OS2.49.1.set1d06_ 1--, runtime was 2.5 hrs That'll be a quick Beta test if that should continue...?! |
||
|
|