Too Many Exits/Lockfile Error??

Message boards : Number crunching : Too Many Exits/Lockfile Error??

To post messages, you must log in.

AuthorMessage
Profile Rhe
Avatar

Send message
Joined: 17 Dec 99
Posts: 50
Credit: 488,837
RAC: 0
United States
Message 888269 - Posted: 25 Apr 2009, 15:45:37 UTC

Hi, ya'll!

Received this result on one of my MB work units. Did a message board search and couldn't find anything on this. Anyone have any ideas on what happened here? Thanks in advance!

<core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
too many exit(0)s
</message>
<stderr_txt>
setiathome_enhanced 6.02 DevC++/MinGW
libboinc: 6.3.6

Work Unit Info:
...............
WU true angle range is : 0.448124
Optimal function choices:
-----------------------------------------------------
name
-----------------------------------------------------
v_BaseLineSmooth (no other)
v_vGetPowerSpectrum 0.00205 0.00000
sse1_ChirpData_ak 0.04127 0.00000
v_vTranspose4ntw 0.01658 0.00000
BH SSE folding 0.00512 0.00000
No heartbeat from core client for 30 sec - exiting
Restarted at 19.58 percent.
Can't set up shared mem: -1
Will run in standalone mode.
Restarted at 38.77 percent.
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting
Can't acquire lockfile - exiting

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 17.3208995346886
Granted credit 0
application version 6.03



Team SETI.USA Forums
Somewhere, something incredible is waiting to be known. ~~Carl Sagan

ID: 888269 · Report as offensive
Aurora Borealis
Volunteer tester
Avatar

Send message
Joined: 14 Jan 01
Posts: 3075
Credit: 5,631,463
RAC: 0
Canada
Message 888280 - Posted: 25 Apr 2009, 16:57:44 UTC
Last modified: 25 Apr 2009, 16:58:21 UTC

The only thing that come to mind is to make sure the Boinc and Boinc Data folder are exempt from virus check.

ID: 888280 · Report as offensive
Profile Byron S Goodgame
Volunteer tester
Avatar

Send message
Joined: 16 Jan 06
Posts: 1145
Credit: 3,936,993
RAC: 0
United States
Message 888298 - Posted: 25 Apr 2009, 17:50:56 UTC
Last modified: 25 Apr 2009, 18:04:25 UTC

This may also have to do with having cpu time in Boinc Manager, set to less than 100% on multi core systems. I'm not sure this is still a bug in 6.6x, but it was in the past.

Edit: there's also some info HERE about "too many exit(0)s"


ID: 888298 · Report as offensive
Profile Rhe
Avatar

Send message
Joined: 17 Dec 99
Posts: 50
Credit: 488,837
RAC: 0
United States
Message 888791 - Posted: 27 Apr 2009, 15:38:57 UTC - in response to Message 888298.  

Just wanted to say thanks all for your input on this!



Team SETI.USA Forums
Somewhere, something incredible is waiting to be known. ~~Carl Sagan

ID: 888791 · Report as offensive

Message boards : Number crunching : Too Many Exits/Lockfile Error??


 
©2016 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.