Message boards :
News :
N-Body Release 1.42
Message board moderation
Author | Message |
---|---|
Send message Joined: 20 Aug 12 Posts: 66 Credit: 406,916 RAC: 0 |
Dear users, N-Body will be released at 4 pm EST today. Features of this release include an improved dwarf galaxy model and new data representation features. Post here with issues. As this is likely my last release on this project (due to my move to England for graduate school), I would like to thank all of you for helping me do great science during my time affiliated with Dr. Newberg's group. I will still be active in the community, but I am proud to hand my role in the project off to Sidd. I look forward to a continued relationship with the BOINC community in the future. Cheers, Jake Bauer |
Send message Joined: 9 Jan 09 Posts: 19 Credit: 1,009,149,134 RAC: 0 |
Thanks for your work! Good luck at the new place! |
Send message Joined: 13 Mar 08 Posts: 804 Credit: 26,380,161 RAC: 0 |
Dear users, Best wishes on your future Jake! |
Send message Joined: 31 Oct 10 Posts: 83 Credit: 38,632,375 RAC: 0 |
Good Luck to you Jake!! |
Send message Joined: 31 Oct 10 Posts: 83 Credit: 38,632,375 RAC: 0 |
Ok, each of the N bodies that I have run has ended Inconclusive (1 error). This is not normally a big deal except I noticed that they have yet to be sent to other crunchers for validation? Is there something that is keeping these units from being dispatched? |
Send message Joined: 20 Aug 12 Posts: 66 Credit: 406,916 RAC: 0 |
Thank you for your reply. I have noticed a slow validation process so far. However, keep in mind that on 1 core, these simulations take half a day to run. It is conceivable that there has not been enough time for validation to occur. I will be monitoring this closely and provide more information later. Jake |
Send message Joined: 31 Oct 10 Posts: 83 Credit: 38,632,375 RAC: 0 |
Jake, All but one of the Inconclusives are MT, using 4 cores and the run time was very reasonable. Here is the result of the one that ended in error: Stderr output <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> The system cannot find the drive specified. (0xf) - exit code 15 (0xf) </message> <stderr_txt> <search_application> milkyway_nbody 1.42 Windows x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 4 max threads on a system with 4 processors RHO MAX IS 7.49218 7.49218Error reading histogram line 37: 1 -48.5294117647 0.0439655511 0.0013148967 23:44:08 (8448): called boinc_finish </stderr_txt> ]]> |
Send message Joined: 26 Oct 12 Posts: 2 Credit: 516,327 RAC: 0 |
Jake, The error experienced has been found by 4 other crunchers; see the following text. Is this due to a bug? Workunit 598935417 Brett Collins · log out name ps_nbody_06_03_orphan_sim_3_1405680903_284123 application MilkyWay@Home N-Body Simulation created 3 Aug 2014, 21:22:48 UTC minimum quorum 2 initial replication 2 max # of error/total/success tasks 3, 9, 6 Task click for details Computer Sent Time reported or deadline explain Status Run time (sec) CPU time (sec) Credit Application 801724734 573430 4 Aug 2014, 6:57:34 UTC 5 Aug 2014, 7:21:19 UTC Error while computing 0.00 0.00 --- MilkyWay@Home N-Body Simulation v1.40 (mt) 802587369 250226 5 Aug 2014, 11:52:51 UTC 5 Aug 2014, 22:20:37 UTC Completed, validation inconclusive 5,307.47 37,389.76 pending MilkyWay@Home N-Body Simulation v1.40 (mt) 802973006 521860 5 Aug 2014, 22:51:13 UTC 6 Aug 2014, 13:52:45 UTC Error while computing 30,425.36 29,961.63 --- MilkyWay@Home N-Body Simulation v1.42 803354779 458852 6 Aug 2014, 14:12:12 UTC 6 Aug 2014, 21:03:46 UTC Error while computing 14,162.51 12,993.16 --- MilkyWay@Home N-Body Simulation v1.42 803638201 --- --- --- Unsent --- --- --- [img]http://boincstats.com/signature/-1/user/3453400/sig.png[img] |
Send message Joined: 20 Aug 12 Posts: 66 Credit: 406,916 RAC: 0 |
The histogram files were updated. Anything dated before 08_06 will definitely error. This is what is being seen. Abort these workunits if you see them. Only ones with 08_05 in them should be valid. Apologies for the inconvenience, but the development team saw no other way. |
Send message Joined: 14 Jun 11 Posts: 2 Credit: 4,809,195 RAC: 279 |
Hi Jake. First of all, best wishes for your stay in Europe! Have a good time over there and get some nice cold beer (or other refreshing things of your choice)! ;) Now reporting errors of my own: I'm also having a unusual amount of errors. My new computer (3 months) works now absolutely reliable, up till now, no error can be assigned to a heat related problem or other pure calculation errors. With V1.42 I now a have some problems, 4 errors up till now, although there valid results too, all of the same download date (10 Aug 2014, 0:50:16 UTC): a) 3 times the same message as @TimeRanger reports e.g.: <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> Das System kann das angegebene Laufwerk nicht finden. (translated: The system cannot find the drive specified). (0xf) - exit code 15 (0xf) </message> <stderr_txt> <search_application> milkyway_nbody 1.42 Windows x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 4 max threads on a system with 8 processors RHO MAX IS 7.41854 7.41854Error reading histogram line 37: 1 -48.5294117647 0.0439655511 0.0013148967 03:51:51 (6448): called boinc_finish </stderr_txt> ]]> b) even one disk size problem (i intentionally have low disk size (only 300MB) for some purposes): <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> Maximum disk usage exceeded </message> <stderr_txt> <search_application> milkyway_nbody 1.42 Windows x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 4 max threads on a system with 8 processors RHO MAX IS 923.65978 923.65978 </stderr_txt> ]]> Besides: What does "Only ones with 08_05 in them..." mean? Where can this data(08_05 or 08_06) be found? |
Send message Joined: 20 Aug 12 Posts: 66 Credit: 406,916 RAC: 0 |
This is the error I had mentioned. It would be in the workunit name. For instance: de_nbody_08_05_orphan_sim will be in the name of the workunit. This simply refers to the date that the run was started. You should stop seeing these errors very soon. |
Send message Joined: 14 Jun 11 Posts: 2 Credit: 4,809,195 RAC: 279 |
Yep, just checked: All my errant tasks contain 06_11 or 06_03 or 06_28 in it's name; valid tasks all have 08_05 in it's name! Completely confirms your remarks. Gotta stop two of the remaining three tasks, since those are non-08_05-types. Thanks a lot for your info, especially on sunday! :thumbsup: By the way: Is it possible to stop those task on all affected users by milkyway itself by some sort of remote-kill-call? Problem is: one of the affected tasks that i have will run an estimated roughly 42 hours (has already run for 1 1/2 hours, which is no big deal, with progress just getting to 3,5%). There will be a ton of users who will run these sometimes ultra long tasks getting an error right at the end of the run. Might be frustrating for those users. Perhaps a report on Milkway-main-page might be helpful too. Greetings! |
Send message Joined: 20 Aug 12 Posts: 66 Credit: 406,916 RAC: 0 |
I'm a slave to this project. It's not a problem to work Sundays at all! Please post to the MilkyWay main page. Truth-be-told, I am the worst person to ask about server operations. Travis is probably your best bet. The runs in question have been stopped so this is only a temporary issue. You mentioned the time estimation issues: It turns out that for this application, time estimation is extremely difficult. N-body simulations are notorious for this. I believe the last person to work on this in our group was Jeff. There are no actual 42 hour workunits to my knowledge, and if there are, appropriate credit should be awarded. Like I said, this should be resolved as the queue is cleared of these old workunits in the coming week. I apologize for this. But maybe someone else will be able to make something of your suggestion. Definitely try posting on the main page. P.S. I'll think I'll have that cold beer now. |
Send message Joined: 15 Feb 10 Posts: 63 Credit: 1,836,010 RAC: 0 |
Yet unreported errors except the histogram on line 37 : 1st: on a MacOS (Darwin), wingman of my PC "BRISINGR"... unit name: ps_nbody_06_28_orphan_sim_0_1405680903_233061_1 result url: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=807037348 output: <core_client_version>6.6.20</core_client_version> <![CDATA[ <message> process got signal 5 </message> <stderr_txt> dyld: unknown required load command 0x80000022 </stderr_txt> ]]> ------- 2nd: on Windows XP - this interesting error happened. WU name: de_nbody_06_11_orphan_sim_0_1405680903_296459_0 result url: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=803230167 output: <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> Impossibile trovare l'unità specificata. (0xf) - exit code 15 (0xf) </message> <stderr_txt> <search_application> milkyway_nbody 1.42 Windows x86 double OpenMP, Crlibm </search_application> Using OpenMP 2 max threads on a system with 2 processors RHO MAX IS 28.70879 28.70879Could not load Ktm32.dll (1815): (null)Error reading histogram line 37: 1 -48.5294117647 0.0439655511 0.0013148967 18:31:15 (4248): called boinc_finish </stderr_txt> ]]> ---------------- 3rd: The "All my wingmen on Linux" problem example. WU id: wuid=600207190 url (does not work anymore) : http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=600207190 This unit had too many (4) ERRORs similar to "Cannot find library CLIB-v2.4" ... and one more type of error I can't remember at all, I am sorry. This unit also have had two *correct* scientific results with "Poor likelihood - returning worst case"). However, it could not be validated, because of too many errors. That's all I have seen and could find for now. Melwen - Child of the Fangorn Forest Rig "BRISINGR" [ASUS G73-JH, i7 720QM 1.73, 4x2GB DDR3 1333 CL7, ATi HD5870M 1GB GDDR5],bought on 2011-02-24 |
Send message Joined: 15 Feb 10 Posts: 63 Credit: 1,836,010 RAC: 0 |
List of errors from "MilkyWay@Home N-Body Simulation v1.42 (mt)" on Linux and Darwin (Mac OS 10.8.5 build 12F45 and Mac OS 10.9.4 build 13E28). source: My wingmen. WU name: ps_nbody_08_05_orphan_sim_2_1405680903_333133 url: http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=600244458 1st ERROR: result: ps_nbody_08_05_orphan_sim_2_1405680903_333133_2 url: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=805977865 PC:http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=518054 OS: Linux 3.2.0-4-amd64 output: <core_client_version>7.0.27</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255) </message> <stderr_txt> ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.42_x86_64-pc-linux-gnu__mt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.42_x86_64-pc-linux-gnu__mt) </stderr_txt> ]]> 2nd ERR: result: ps_nbody_08_05_orphan_sim_2_1405680903_333133_1 url: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=804398268 PC: http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=569399 OS: Darwin 12.5.0 (Macintosh OS 10.8.5 build 12F45) output: <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> dyld: DYLD_ environment variables being ignored because main executable (/Library/Application Support/BOINC Data/slots/3/../../switcher/switcher) is setuid or setgid <search_application> milkyway_nbody 1.42 Darwin x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 8 max threads on a system with 8 processors RHO MAX IS 11.25741 11.25741SIGABRT: abort called dyld: DYLD_ environment variables being ignored because main executable (/bin/ps) is setuid or setgid dyld: DYLD_ environment variables being ignored because main executable (/bin/ps) is setuid or setgid Crashed executable name: milkyway_nbody_1.42_x86_64-apple-darwin__mt Machine type Intel 80486 (64-bit executable) System version: Macintosh OS 10.8.5 build 12F45 Sun Aug 10 19:08:30 2014 dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/atos) has __RESTRICT/__restrict section atos cannot load symbols for the file milkyway_nbody_1.42_x86_64-apple-darwin__mt for architecture x86_64. 0 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x00000001001267e3 SIGPIPE: write on a pipe with no reader 1 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x0000000100118853 SIGPIPE: write on a pipe with no reader 2 libsystem_c.dylib 0x00007fff9727890a SIGPIPE: write on a pipe with no reader 3 ??? 0x0000000000000000 SIGPIPE: write on a pipe with no reader 4 libsystem_c.dylib 0x00007fff9728f047 SIGPIPE: write on a pipe with no reader 5 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x00000001000046ab SIGPIPE: write on a pipe with no reader 6 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000478c SIGPIPE: write on a pipe with no reader 7 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000415c SIGPIPE: write on a pipe with no reader 8 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000e006 SIGPIPE: write on a pipe with no reader 9 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000de7d SIGPIPE: write on a pipe with no reader 10 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000e645 SIGPIPE: write on a pipe with no reader 11 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000d583 SIGPIPE: write on a pipe with no reader 12 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000db92 SIGPIPE: write on a pipe with no reader 13 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x000000010000540e SIGPIPE: write on a pipe with no reader 14 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x0000000100001fb4 SIGPIPE: write on a pipe with no reader 15 ??? 0x0000000000000012 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0100001f rbx: 0x00000028 rcx: 0x7fff5fbfd078 rdx: 0x00000028 rdi: 0x7fff5fbfd0e0 rsi: 0x00000003 rbp: 0x7fff5fbfd0c0 rsp: 0x7fff5fbfd078 r8: 0x00000c07 r9: 0x00000000 r10: 0x000003b0 r11: 0x00000206 r12: 0x00000003 r13: 0x7fff5fbfd0e0 r14: 0x00000c07 r15: 0x000003b0 rip: 0x7fff90a31686 rfl: 0x00000206 Binary Images Description: 0x100000000 - 0x100160fff /Library/Application Support/BOINC Data/slots/3/../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x7fff8d229000 - 0x7fff8d230fff /usr/lib/system/libcopyfile.dylib 0x7fff8d89b000 - 0x7fff8d8c0fff /usr/lib/libc++abi.dylib 0x7fff8d8c1000 - 0x7fff8d8c2fff /usr/lib/libSystem.B.dylib 0x7fff8db2c000 - 0x7fff8db94fff /usr/lib/libc++.1.dylib 0x7fff8e027000 - 0x7fff8e02ffff /usr/lib/system/liblaunch.dylib 0x7fff8e362000 - 0x7fff8e363fff /usr/lib/libDiagnosticMessagesClient.dylib 0x7fff8e563000 - 0x7fff8e56efff /usr/lib/system/libsystem_notify.dylib 0x7fff8ec32000 - 0x7fff8ec40fff /usr/lib/system/libcommonCrypto.dylib 0x7fff8ec41000 - 0x7fff8ec53fff /usr/lib/libz.1.dylib 0x7fff8f5d6000 - 0x7fff8f6eefff /usr/lib/libobjc.A.dylib 0x7fff9031d000 - 0x7fff9031ffff /usr/lib/system/libunc.dylib 0x7fff90819000 - 0x7fff90868fff /usr/lib/system/libcorecrypto.dylib 0x7fff90a21000 - 0x7fff90a3cfff /usr/lib/system/libsystem_kernel.dylib 0x7fff90b06000 - 0x7fff90b1bfff /usr/lib/system/libdispatch.dylib 0x7fff90be5000 - 0x7fff90be6fff /usr/lib/system/libsystem_blocks.dylib 0x7fff91180000 - 0x7fff911b6fff /usr/lib/system/libsystem_info.dylib 0x7fff913ea000 - 0x7fff913effff /usr/lib/system/libcache.dylib 0x7fff92fbb000 - 0x7fff92fddfff /usr/lib/system/libxpc.dylib 0x7fff92fde000 - 0x7fff92fdffff /usr/lib/system/libremovefile.dylib 0x7fff93303000 - 0x7fff93311fff /usr/lib/system/libsystem_network.dylib 0x7fff93312000 - 0x7fff93315fff /usr/lib/system/libdyld.dylib 0x7fff9375d000 - 0x7fff93765fff /usr/lib/system/libsystem_dnssd.dylib 0x7fff937f9000 - 0x7fff937f9fff /usr/lib/system/libkeymgr.dylib 0x7fff938ce000 - 0x7fff93ab8fff /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff95042000 - 0x7fff9508efff /usr/lib/libauto.dylib 0x7fff9604f000 - 0x7fff96050fff /usr/lib/system/libdnsinfo.dylib 0x7fff96169000 - 0x7fff96369fff /usr/lib/libicucore.A.dylib 0x7fff96950000 - 0x7fff969b9fff /usr/lib/libstdc++.6.dylib 0x7fff971bb000 - 0x7fff971c1fff /usr/lib/system/libmacho.dylib 0x7fff97276000 - 0x7fff97342fff /usr/lib/system/libsystem_c.dylib 0x7fff9946a000 - 0x7fff9946ffff /usr/lib/system/libcompiler_rt.dylib 0x7fff99780000 - 0x7fff99786fff /usr/lib/system/libunwind.dylib 0x7fff99787000 - 0x7fff99788fff /usr/lib/system/libsystem_sandbox.dylib 0x7fff99973000 - 0x7fff99975fff /usr/lib/system/libquarantine.dylib 0x7fff99a0e000 - 0x7fff99a3cfff /usr/lib/system/libsystem_m.dylib Exiting... </stderr_txt> ]]> 3rd ERR: result: ps_nbody_08_05_orphan_sim_2_1405680903_333133_0 url: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=803503239 PC: http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=581249 OS: Darwin 13.3.0 (Macintosh OS 10.9.4 build 13E28) output: <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> <search_application> milkyway_nbody 1.42 Darwin x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 6 max threads on a system with 8 processors RHO MAX IS 11.25741 11.25741SIGABRT: abort called Crashed executable name: milkyway_nbody_1.42_x86_64-apple-darwin__mt Machine type Intel 80486 (64-bit executable) System version: Macintosh OS 10.9.4 build 13E28 Fri Aug 8 00:40:14 2014 -- Warning: /usr/bin/atos is moving and will be removed from a future OS X release. It is now available in the Xcode developer tools to be invoked via: `xcrun atos` To silence this warning, pass the '-d' command-line flag to this tool. -- atos cannot load symbols for the file milkyway_nbody_1.42_x86_64-apple-darwin__mt for architecture x86_64. 0 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x00000001001267e3 1 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x0000000100118853 2 libsystem_platform.dylib 0x00007fff8e8c95aa 3 libsystem_kernel.dylib 0x00007fff8f11c1ae 4 libsystem_c.dylib 0x00007fff94d4ab1a 5 libsystem_pthread.dylib 0x00007fff8b91d984 6 libsystem_pthread.dylib 0x00007fff8b91da38 7 libsystem_pthread.dylib 0x00007fff8b91c96f 8 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x0000000100004783 9 milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x00000001000040fe 10 libsystem_pthread.dylib 0x00007fff8b919899 11 libsystem_pthread.dylib 0x00007fff8b91972a 12 libsystem_pthread.dylib 0x00007fff8b91dfc9 Thread 6 crashed with X86 Thread State (64-bit): rax: 0x0100001f rbx: 0x00000003 rcx: 0x103f8f788 rdx: 0x00000028 rdi: 0x103f8f7f0 rsi: 0x00000003 rbp: 0x103f8f7d0 rsp: 0x103f8f788 r8: 0x00001d03 r9: 0x00000000 r10: 0x000003b0 r11: 0x00000206 r12: 0x000003b0 r13: 0x00000028 r14: 0x103f8f7f0 r15: 0x00001d03 rip: 0x7fff8f11ba1a rfl: 0x00000206 Binary Images Description: 0x100000000 - 0x100160fff /Library/Application Support/BOINC Data/slots/3/../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.42_x86_64-apple-darwin__mt 0x7fff88253000 - 0x7fff88254fff /usr/lib/system/libsystem_sandbox.dylib 0x7fff88290000 - 0x7fff882abfff /usr/lib/system/libsystem_malloc.dylib 0x7fff8831f000 - 0x7fff88324fff /usr/lib/system/libunwind.dylib 0x7fff88cf7000 - 0x7fff88d45fff /usr/lib/system/libcorecrypto.dylib 0x7fff88d4f000 - 0x7fff88d7efff /usr/lib/system/libsystem_m.dylib 0x7fff898c4000 - 0x7fff898d5fff /usr/lib/system/libsystem_asl.dylib 0x7fff89933000 - 0x7fff8995afff /usr/lib/system/libsystem_info.dylib 0x7fff8995b000 - 0x7fff899adfff /usr/lib/libc++.1.dylib 0x7fff89e80000 - 0x7fff89e89fff /usr/lib/system/libsystem_notify.dylib 0x7fff89fc5000 - 0x7fff8a1aafff /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff8a66c000 - 0x7fff8a819fff /usr/lib/libobjc.A.dylib 0x7fff8a81a000 - 0x7fff8a81efff /usr/lib/system/libsystem_stats.dylib 0x7fff8a81f000 - 0x7fff8a824fff /usr/lib/system/libmacho.dylib 0x7fff8b662000 - 0x7fff8b669fff /usr/lib/system/liblaunch.dylib 0x7fff8b918000 - 0x7fff8b91ffff /usr/lib/system/libsystem_pthread.dylib 0x7fff8bd8d000 - 0x7fff8bddbfff /usr/lib/libstdc++.6.dylib 0x7fff8bddf000 - 0x7fff8bde1fff /usr/lib/system/libsystem_configuration.dylib 0x7fff8bde2000 - 0x7fff8bde6fff /usr/lib/system/libcache.dylib 0x7fff8bf2d000 - 0x7fff8bf34fff /usr/lib/system/libcompiler_rt.dylib 0x7fff8c0a4000 - 0x7fff8c0a5fff /usr/lib/system/libremovefile.dylib 0x7fff8c87b000 - 0x7fff8c87cfff /usr/lib/libSystem.B.dylib 0x7fff8cd22000 - 0x7fff8cd25fff /usr/lib/system/libdyld.dylib 0x7fff8d489000 - 0x7fff8d48afff /usr/lib/system/libunc.dylib 0x7fff8d4a0000 - 0x7fff8d4c9fff /usr/lib/libc++abi.dylib 0x7fff8d98d000 - 0x7fff8d995fff /usr/lib/system/libsystem_dnssd.dylib 0x7fff8e8c6000 - 0x7fff8e8ccfff /usr/lib/system/libsystem_platform.dylib 0x7fff8ee01000 - 0x7fff8ee1bfff /usr/lib/system/libdispatch.dylib 0x7fff8f10a000 - 0x7fff8f126fff /usr/lib/system/libsystem_kernel.dylib 0x7fff90004000 - 0x7fff9000efff /usr/lib/system/libcommonCrypto.dylib 0x7fff902cf000 - 0x7fff902d1fff /usr/lib/system/libquarantine.dylib 0x7fff91171000 - 0x7fff91198fff /usr/lib/system/libsystem_network.dylib 0x7fff91321000 - 0x7fff91345fff /usr/lib/system/libxpc.dylib 0x7fff913ca000 - 0x7fff913cbfff /usr/lib/libDiagnosticMessagesClient.dylib 0x7fff913d7000 - 0x7fff913d7fff /usr/lib/system/libkeymgr.dylib 0x7fff91925000 - 0x7fff91936fff /usr/lib/libz.1.dylib 0x7fff92996000 - 0x7fff92997fff /usr/lib/system/libsystem_blocks.dylib 0x7fff93bf4000 - 0x7fff93c36fff /usr/lib/libauto.dylib 0x7fff93ed8000 - 0x7fff94090fff /usr/lib/libicucore.A.dylib 0x7fff94c0c000 - 0x7fff94c13fff /usr/lib/system/libcopyfile.dylib 0x7fff94cee000 - 0x7fff94d77fff /usr/lib/system/libsystem_c.dylib Exiting... </stderr_txt> ]]> Melwen - Child of the Fangorn Forest Rig "BRISINGR" [ASUS G73-JH, i7 720QM 1.73, 4x2GB DDR3 1333 CL7, ATi HD5870M 1GB GDDR5],bought on 2011-02-24 |
Send message Joined: 20 Aug 12 Posts: 66 Credit: 406,916 RAC: 0 |
I will look into this. It looks like a library issue. We tried something different this time around. I will suggest that revert back to the previous way of doing things to avoid this error. Jake |
Send message Joined: 15 Feb 10 Posts: 63 Credit: 1,836,010 RAC: 0 |
Thank You so much, Jake! Thou art awesome. Good luck in the U.K. And have fun! Melwen - Child of the Fangorn Forest Rig "BRISINGR" [ASUS G73-JH, i7 720QM 1.73, 4x2GB DDR3 1333 CL7, ATi HD5870M 1GB GDDR5],bought on 2011-02-24 |
Send message Joined: 15 Feb 10 Posts: 63 Credit: 1,836,010 RAC: 0 |
EPIC FAIL - I am sorry. I should have aborted this long time ago. But I could not understand if it shall be older than 2014-08-05 or if it shall be older than 2014-05-08 :) ... TO BE aborted because it will surely error out with histo-line 37. :) de_nbody_06_11_orphan_sim_0_1405680903_257789_5 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=808560279 Destroyed CPU time: 24 hours x 8 cores Sorry. Melwen - Child of the Fangorn Forest Rig "BRISINGR" [ASUS G73-JH, i7 720QM 1.73, 4x2GB DDR3 1333 CL7, ATi HD5870M 1GB GDDR5],bought on 2011-02-24 |
Send message Joined: 1 Jan 14 Posts: 24 Credit: 4,277,349 RAC: 0 |
A couple of errors here also Stderr output <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> The system cannot find the drive specified. (0xf) - exit code 15 (0xf) </message> <stderr_txt> <search_application> milkyway_nbody 1.42 Windows x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 8 max threads on a system with 8 processors RHO MAX IS 7.31454 7.31454Error reading histogram line 37: 1 -48.5294117647 0.0439655511 0.0013148967 15:17:42 (3028): called boinc_finish </stderr_txt> ]]> |
Send message Joined: 20 Aug 12 Posts: 66 Credit: 406,916 RAC: 0 |
Thanks! In response to your earlier point, we have confirmed that this is a library issue. This should be fixed upon the next release (I want to say a couple weeks from now, but don't quote me). |
©2024 Astroinformatics Group