Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 1
|
![]() |
Author |
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
For those of you who are experiencing the exit status 293 error - we need a littel more information - the good news is that we are getting closer!
We need to get a copy of the client_state.xml file with the information about the result that experienced the error that is still in the file (i.e. not yet reported back to the server) AND we need the scheduler request and scheduler response that sent the result to the client. In order for us to get this, what we you to do is the following: 1) Modify the cc_config.xml and enable <task_debug>1</task_debug> See http://boinc.berkeley.edu/wiki/Client_configuration for details 2) In a few minutes I will add more work for the project 2) Get some of the beta work and watch it run 3) If you see the result error out, immediately go into the BOINC Manager and stop all network communication 4) Check to see if the exit status was 293 (you should see this now because of enabling task_debug) 5) If it was 293, then Send me the client_state.xml file as well as the message log file to knreed@us.ibm.com. Also send me the scheduler_request_www.worldcommunitygrid.org.xml and sched_reply_www.worldcommunitygrid.org.xml. 6) Re-enable network communication. Thank you everyone for this extensive help - we are making progress. |
||
|
|
![]() |