Message boards :
News :
maximum time limit elapsed bug
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
Author | Message |
---|---|
Send message Joined: 11 Nov 07 Posts: 232 Credit: 178,229,009 RAC: 0 |
I'm having the same issue which is becoming really annoying. Have you also try to leave 1 CPU core free from BOINC by going in to the BOINC manager under 'Advanced' \ 'Preferences' and set the 'On multiprocessor system, use at most' to 75% ( for a quad core, or 50% if the CPU has 2 cores )? Also. Do you have a standard OS or a hacked copy? ( I ask this caus I have try to run BOINC on an other PC with a hacked OS before and got lot's of errors) What is your GPU temp under load? |
Send message Joined: 27 Aug 10 Posts: 19 Credit: 153,747,675 RAC: 0 |
Yeah tried the 75% option which didn't work. GPU temp i've not checked but the same GPU works in another rig without any problems and all my systems are in coolermaster test benches open air. Full legal OEM copy of Windows 7 Home Premium 64 BIT. Works fine with collatz. Thanks |
Send message Joined: 27 Aug 10 Posts: 19 Credit: 153,747,675 RAC: 0 |
09/07/2011 17:46:32 Milkyway@home Aborting task ps_separation_10_3s_fix20_2_714732_0: exceeded elapsed time limit 57.336040 09/07/2011 17:46:32 Milkyway@home Aborting task ps_separation_10_3s_fix20_2_714731_0: exceeded elapsed time limit 57.336040 09/07/2011 17:46:32 Milkyway@home Aborting task ps_separation_10_3s_fix20_2_714730_0: exceeded elapsed time limit 57.336040 09/07/2011 17:46:32 Milkyway@home Aborting task ps_separation_10_3s_fix20_2_714725_0: exceeded elapsed time limit 57.336040 09/07/2011 17:45:34 ATI GPU 0: ATI unknown (CAL version 1.4.1332, 2048MB, 3187 GFLOPS peak) 09/07/2011 17:45:34 ATI GPU 1: ATI unknown (CAL version 1.4.1332, 2048MB, 3187 GFLOPS peak) 09/07/2011 17:45:34 ATI GPU 2: ATI unknown (CAL version 1.4.1332, 2048MB, 3187 GFLOPS peak) 09/07/2011 17:45:34 ATI GPU 3: ATI unknown (CAL version 1.4.1332, 2048MB, 1062 GFLOPS peak) This is using 2 x ATI HD 6990 4 GB and ATI 11.5 driver. Name ps_separation_10_3s_fix20_2_714746_0 Workunit 45302439 Created 8 Jul 2011 | 8:26:43 UTC Sent 8 Jul 2011 | 8:28:02 UTC Received 8 Jul 2011 | 16:43:52 UTC Server state Over Outcome Computation error Client state Compute error Exit status -177 (0xffffffffffffff4f) Computer ID 301899 Report deadline 20 Jul 2011 | 8:28:02 UTC Run time 0.00 CPU time 0.00 Validate state Invalid Credit 0.00 Application version MilkyWay@Home v0.82 (ati14) Stderr output <core_client_version>6.10.60</core_client_version> <![CDATA[ <message> Maximum elapsed time exceeded </message> ]]> MilkyWay@Home 0.82 windows_x86_64 (ati14) Number of tasks completed 0 Max tasks per day 9966 Number of tasks today 152 Consecutive valid tasks 0 Average turnaround time 0.00 days |
Send message Joined: 5 Feb 11 Posts: 2 Credit: 13,001,571 RAC: 0 |
No problem with Time-limit: 1 unit working with 8cpu's Doing now 42:19 minuts and 14hr's to go. the unit is called: ps_nbody_test_1452_1 I wonder how the credit count will be? |
Send message Joined: 27 Aug 10 Posts: 19 Credit: 153,747,675 RAC: 0 |
i have solved it for me. 11.5 ati and 10.6 boinc works. 11.3 or 11.6 ati and any other boinc version for me gives this problem. |
Send message Joined: 27 Aug 10 Posts: 19 Credit: 153,747,675 RAC: 0 |
nope spoke 2 soon. Did about 10 units then started to error again. Given up and doing another project now |
Send message Joined: 18 Dec 10 Posts: 6 Credit: 20,092,518 RAC: 0 |
problem with new cruncher: tried dcf-trick, reset does not work. Current client_state.xml <flops>60253697793888.297000</flops> will try app_info.xml, next edit: with app_info.xml and <flops>1.0e11</flops> = JOY. @Travis, Please consider looking into <flops> assignment/calculation. Lower <flops> and let dcf do the correction. |
Send message Joined: 26 Mar 09 Posts: 7 Credit: 702,781 RAC: 0 |
I still have the same total points (115,472) that I had back on 6/30/2011. Those 400+ points were never added to my account. |
Send message Joined: 28 Feb 10 Posts: 120 Credit: 109,840,492 RAC: 0 |
Thats what boinc stats say: Last 30 days (based on the daily update numbers): 2011-07-08 2011-07-07 2011-07-06 2011-07-05 2011-07-04 2011-07-03 2011-07-02 2011-07-01 2011-06-30 2011-06-29 Total Credit 481 481 481 Credit/day 0 0 481 0 0 0 0 0 0 0 Position 4,716,292 4,696,295 4,698,724 Position change 19997 2429 4698724 0 0 0 0 0 0 0 but this is the wrong thread. greetings Franz |
Send message Joined: 3 Jul 11 Posts: 8 Credit: 66,330,086 RAC: 0 |
Now, although I have .82 and .88 workunits processing OK by using an app_info.xml file, I am receiving messages from Milkway in the form :- 09/07/2011 22:08:33 | Milkyway@home | Message from server: Your app_info.xml file doesn't have a usable version of MilkyWay@Home N-Body Simulation. So I tried to add it by creating this app_info file :- <app_info> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_nbody_0.66_windows_intelx86__mt.exe</name> <executable /> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>66</version_num> <cmdline></cmdline> <file_ref> <file_name>milkyway_nbody_0.66_windows_intelx86__mt.exe</file_name> <main_program/> </file_ref> </app_version> <file_info> <name>milkyway_separation_0.82_windows_intelx86__ati14.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>82</version_num> <flops>1.0e11</flops> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>ati14ati</plan_class> <coproc> <type>ATI</type> <count>1</count> </coproc> <cmdline></cmdline> <file_ref> <file_name>milkyway_separation_0.82_windows_intelx86__ati14.exe</file_name> <main_program/> </file_ref> </app_version> <file_info> <name>milkyway_separation_0.88_windows_intelx86.exe</name> <executable /> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>88</version_num> <cmdline></cmdline> <file_ref> <file_name>milkyway_separation_0.88_windows_intelx86.exe</file_name> <main_program/> </file_ref> </app_version> </app_info> But I realised that the .66 exe file is wrong because I copied it from my other machine which is 32 bit windows, not 64 bit. Can anyone tell me where I can get the 64 bit exe and dll files from so I can get this working until someone gets enough time to fix the MTLE bug with the .82 ? TIA. Dave. |
Send message Joined: 14 Feb 09 Posts: 999 Credit: 74,932,619 RAC: 0 |
You can get them from here, it does load slow though. http://milkyway.cs.rpi.edu/milkyway/download/?C=M;O=A http://milkyway.cs.rpi.edu/milkyway/download/milkyway_nbody_0.66_windows_x86_64__mt.exe http://milkyway.cs.rpi.edu/milkyway/download/libgomp_64_nbody_0.66.dll http://milkyway.cs.rpi.edu/milkyway/download/pthreadGC2_64_nbody_0.66.dll |
Send message Joined: 3 Jul 11 Posts: 8 Credit: 66,330,086 RAC: 0 |
You can get them from here, it does load slow though. Thanks very much Arkayn, exactly what I needed. All the best. Dave. |
Send message Joined: 15 Jun 10 Posts: 1 Credit: 4,482,014 RAC: 0 |
The app_info.xml fixed the problem with elapsed time errors, but I can't process any units with the nbody 0.66 or separation 0.82 any more - if I expand the .xml file to include them using something like the suggestion above, it just deletes the .exe files for them out of the project data directory. Does real well with the ATI files now, though, not a single error. |
Send message Joined: 30 Dec 09 Posts: 3 Credit: 57,148,727 RAC: 20,755 |
I have also the below time problem on an ATi HD5850 CF system for all WU's. 2011.07.15. 23:47:18 | Milkyway@home | Computation for task ps_separation_82_2s_mix3_1_2016_0 finished 2011.07.15. 23:47:36 | Milkyway@home | Aborting task ps_separation_82_2s_mix3_1_2012_0: exceeded elapsed time limit 58.09 (2960429.33G/50965.82G) 2011.07.15. 23:48:10 | Milkyway@home | Computation for task ps_separation_82_2s_mix3_1_2012_0 finished 2011.07.15. 23:48:10 | Milkyway@home | Starting task ps_separation_82_2s_mix3_1_2011_0 using milkyway version 82 2011.07.15. 23:49:10 | Milkyway@home | Aborting task ps_separation_82_2s_mix3_1_2011_0: exceeded elapsed time limit 58.09 (2960429.33G/50965.82G) 2011.07.15. 23:49:10 | Milkyway@home | Starting task ps_separation_82_2s_mix3_1_2010_0 using milkyway version 82 tb |
Send message Joined: 4 Nov 10 Posts: 1 Credit: 201,595,549 RAC: 0 |
2011/7/16 9:51:15 | Milkyway@home | Starting task ps_separation_82_2s_mix1_1_8123_0 using milkyway version 82 2011/7/16 9:52:12 | Milkyway@home | Aborting task ps_separation_82_2s_mix1_1_8123_0: exceeded elapsed time limit 55.68 (2960400.45G/53169.51G) 2011/7/16 9:52:15 | Milkyway@home | Starting task ps_separation_82_2s_mix1_1_8079_0 using milkyway version 82 2011/7/16 9:52:37 | Milkyway@home | Computation for task ps_separation_82_2s_mix1_1_8123_0 finished HD5870 - Catalyst 11.6 - WIN7 64 |
Send message Joined: 10 Mar 08 Posts: 7 Credit: 60,169,291 RAC: 0 |
I have the problem with all my computers - running Win7 64 error at about 55% progress with both 4850's and 5850's |
Send message Joined: 15 Jul 08 Posts: 383 Credit: 729,293,740 RAC: 0 |
I have the problem with all my computers - running Win7 64 If your machines are hidden no one can give suggestions... |
Send message Joined: 8 Feb 08 Posts: 261 Credit: 104,050,322 RAC: 0 |
ps_separation_82_2s seems to have the same problem like the ps_separation_13_3s_free_2. Compared to their real run times their estimation and credits are too low (~30%). Using an app_info.xml they don't error out with maximum time limit elapsed on me. |
Send message Joined: 18 Nov 08 Posts: 291 Credit: 2,461,693,501 RAC: 0 |
My ATI system is failing with this error. It has 5850 and 4890. All the CUDA systems run ok. ATI systems: http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=260372 I switched to Primegrid and got same problem. Seems these boards are too dis-simular to be used ??? |
Send message Joined: 11 Nov 07 Posts: 232 Credit: 178,229,009 RAC: 0 |
My ATI system is failing with this error. It has 5850 and 4890. All the CUDA systems run ok. Try to roll back to the catalyst 11.3 driver. I had the same probelm before on my crossfire setup ( 2X5870) box here but now when I use catalyst 11.3 it's working fine. Older Catalyst drivers is on this page |
©2024 Astroinformatics Group