I've recently started testing the PyMW/BOINC interface with 2 physical nodes and started getting "no canonical result" errors. When I tested it with a single client (the new one added today), it seems that the PyMW client executable (which is a file attached to the task) is getting deleted from the server before the tasks associated with it are completed. So I have two questions:
1) Is there a way to get detailed debugging info from the client? Right now, all I have is the client_state = aborted [6] and a message in the BOINC manager on the client. 2) Currently PyMW creates tasks by attaching the custom executable code and a data file to the task. All the executable files share a single filename (for example, monte_pi), but the name of the data file is unique to the task (i.e. in_monte_pi_<task_index>). Would this cause the executable file to get delete prematurely? It seems like this may be the wrong way to send the executable code, since it's not changing for the entire batch of tasks. Thanks, Jeremy _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
