Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1501 times and has 3 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
There appears to be a problem...

In my "Results Status," I have 74 pages of NRW results.

6 of those pages are valid results.

60-61 pages are errors (going back to May 28, 2009).

We run Mac OS X 10.5.7 and BOINC 6.6.29 (except for a straggler or two) on our 100+ machines.

I'd like to crunch data for this project, but it's not a real good return on investment.
[Jun 15, 2009 1:04:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: There appears to be a problem...

hmmm, not heard of RICE failing on Mac's before, but certainly 6.6.29 is suspect as a client, it's an alpha development version afaik.

I've got 1 XP machine refusing to run this project beyond 1 minute unless using client version 5.10.45, so that's the one I'm using. Recommended by WCG presently is 6.2.18. This is the link to get it: http://boincdl.ssl.berkeley.edu/dl/boinc_6.2.18_macOSX_universal.zip

anyway if you post a result log of any 'error' result, I'll carry it to the techs.

sorry for your IPO's poor ROI ;>)
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jun 15, 2009 1:14:50 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: There appears to be a problem...

6.6.29 is what the BOINC folk have posted as the most "desirable" release. Since NRW appears to be the only problematic project, it's easier to just exclude it from the crunching farm.

FWIW, we do a lot of remote maintenance, so we leave the machines running pretty much 24/7. I can rationalize this to my colleagues (faculty, staff, and students) due to the altruistic nature of many distributed computing projects.

I cannot, in good conscience, let cycles go to waste like this now that I'm aware of it (pesky ethics). So I *have* to drop NRW--at least for now. Be happy to run some alpha/beta for them if it helps fix the problem.

Anyhoo, here's the most recent error report. It appears to be pretty representative:

<core_client_version>6.6.29</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1245919210.000000
Skipping: /computation_deadline
wcg_seed 285632863
wcg_rice_6.17_i686-apple-darwin(33910,0x64f720) malloc: *** error for object 0x8001f0: double free
*** set a breakpoint in malloc_error_break to debug
wcg_rice_6.17_i686-apple-darwin(33910,0x64f720) malloc: *** error for object 0x800260: double free
*** set a breakpoint in malloc_error_break to debug
SIGBUS: bus error

Crashed executable name: wcg_rice_6.17_i686-apple-darwin
built using BOINC library version 6.1.10
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.5.7 build 9J61
Mon Jun 15 08:04:19 2009

SIGBUS: bus error
atos cannot load symbols for the file wcg_rice_6.17_i686-apple-darwin.
0 0x000273ad SIGPIPE: write on a pipe with no reader
1 0x0001dc42 SIGPIPE: write on a pipe with no reader
2 0x0051a2bb SIGPIPE: write on a pipe with no reader
3 0xffffffff SIGPIPE: write on a pipe with no reader
4 0x00013894 SIGPIPE: write on a pipe with no reader
5 0x0000af3d SIGPIPE: write on a pipe with no reader
6 0x00015161 SIGPIPE: write on a pipe with no reader
7 0x00001ece SIGPIPE: write on a pipe with no reader
8 0x00001df5
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe1 ebx: 0x004e28c2 ecx: 0xbfff815c edx: 0x004ae286
edi: 0x00000000 esi: 0x00000000 ebp: 0xbfff8198 esp: 0xbfff815c
ss: 0x0000001f efl: 0x00000206 eip: 0x004ae286 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:
0x1000 - 0x3cfff /Library/Application Support/BOINC Data/slots/1/../../projects/www.worldcommunitygrid.org/wcg_rice_6.17_i686-apple-darwin
0x4ad000 - 0x614fff /usr/lib/libSystem.B.dylib
0x6a3000 - 0x700fff /usr/lib/libstdc++.6.dylib
0x751000 - 0x755fff /usr/lib/system/libmathCommon.A.dylib
0x759000 - 0x760fff /usr/lib/libgcc_s.1.dylib


Exiting...
wcg_rice_6.17_i686-apple-darwin(33910,0x64f720) malloc: *** error for object 0x8001f0: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug

</stderr_txt>
]]>
[Jun 15, 2009 1:37:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: There appears to be a problem...

Changelog says 6.6.29 - Alpha http://boinc.berkeley.edu/dev/forum_thread.php?id=2518&nowrap=true#24787. They now proceeded to 6.6.36, but unless you run CUDA/GPU projects, this 6.6 is not required, plus the ballast of the GPU added to the software.

Yes, the quick fix is to just de-select RICE in the My Grid > My Projects page.

And thanks for the result log. Most informative when the alerted techs come round to have a look. Atm 1 or more of your machines may have hit the daily quota due this result cycling, but good results quickly up that again, that is if you have other tasks to grind outside of RICE.

cheers
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jun 15, 2009 1:47:12 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread