| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: WU's failing with disk exceeded error. |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 37
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Heres the error log from the fail point
call_glss(): pop_size: 200 num_evals: 10000000 start: [18:07:06] Crashed executable name: wcg_faah_autodock_5.10_i686-apple-darwin built using BOINC library version 5.4.9 Machine type Intel 80486 System version: Macintosh OS 10.4.8 build 8N1051 Tue Feb 6 18:08:31 2007 Stack frame backtrace: # Flags Frame Addr Caller PC Return Address Symbol === === ========== ========== ===================== 1 --- 0xb007ef68 0x0005801c 2 --- 0xb00807a8 0x000560c1 3 --- 0xb0080f38 0x0005ea2d 4 --- 0xb0080fe8 0x90023d87 _pthread_body + 0x54 5 FP- 0x00000000 0x00000000 Thread number 0: Stack frame backtrace: # Flags Frame Addr Caller PC Return Address Symbol === === ========== ========== ===================== 1 --- 0xbfeab1d8 0x000097e4 2 --- 0xbfeab598 0x0000a609 3 --- 0xbfeab5b8 0x000278fb 4 --- 0xbfeab688 0x00012b5d 5 --- 0xbfeab6d8 0x0001236f 6 --- 0xbfeaba08 0x00005140 7 --- 0xbffffb98 0x0003b60a 8 --- 0xbffffc78 0x0004d4f1 9 --- 0xbffffcb8 0x00001e1a 10 --- 0xbffffcd4 0x00001d35 11 FP- 0x00000000 0x00000005 It was up to checkpoint file 33 (hex) before it ran out of space. Each checkpoint is about 2 Meg. So its not surprising I'll try resetting it. But I only joined the project a few days ago. So it should be pretty clean. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello robertc99,
Thanks for this information. I suspect that it is pointing at the problem, but I am too ignorant of Mac OS X to make the diagnosis. All I can wonder about are things like file permissions. Lawrence |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
robertc99,
I have started looking into why your machine is getting the disc exceed error, and it appears to be that you computer is failing on every checkpoint it tries to recover from for Fight AIDS @ Home. Your computer has worked on Genome Comparison properly so it appears to be something specific with Fight AIDS @ Home. Thank you for this information and I'm looking into it. -Uplinger |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Another question for you,
Do you have your "Leave applications in memory while preempted?" set to yes or no? This may be what is causing your machine to start and stop excessively. Also how often do you switch between science applications? -Uplinger |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Leave applications in memory: yes
Switch applications: 60 min The only mildly unusual setting I have is to use no more than 70% of the cpu. Which is a relatively new option. After I reset the project, things seem to be better. faah has been running for 5 hours, it never got past 40 minutes before. Of course, its using 80 Meg of disk space, which is roughly where it normally craps out. So it might fall over at any moment. And it only thinks its 2% finished, which is a worry. And the time to completion keeps going up. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yup, just like I thought. It just fell over with disk space exceeded.
|
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Greetings,
What Mac do you have? And what version of the operating system? Also, we're testing this issue at the moment to see what may be causing it. -Uplinger |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Its a new macbook pro (core 2 duo) with 10.4.8
I tested the theory that its related to the "use no more than 70% of the processor" option. By allowing it to use 100% processor. And that seems to fix the problem. Several faah WU's have completed now. I was using that option to stop the CPU from heating up and making the fans spin up. I guess I'll have restrict it to 1 CPU instead. If its any consolation, the other projects I'm on also seem to have issues with that setting, although not as bad. Most of them generate errors about "exited with status 0 but not finished" every so often. Then restart and pick up where they left off. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
 Glad you found a fix.  But that sure is a puzzle. Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, I suspect there are 2 problems here.
One is that when you limit applications to some % cpu, they tend to fall over every so often. Which makes them restart from the latest checkpoint. That problem isnt specific to faah. It happens to most of the applications like rosetta and einstein as well. So presumably it isn't really your problem. The other problem is that checkpointing isnt working for faah. That is specific to faah. And will cause problems in other circumstances. For example if people don't leave applications in memory. That one is your problem and should be looked into. So by putting app use to 100%, I only worked around the 1st problem. The second problem is still there. Just not bothering me. Although is might bother other people. |
||
|
|
|