Message boards : Number crunching : nci not starting asap as expected
Author | Message |
---|---|
I've just attached the project, got 4 WUs (why isn't there a limit to 1 per computer) but none of those started asap, although both are at least named "nci". | |
ID: 24 | Rating: 0 | rate: / Reply Quote | |
We still work on app and server configuration. | |
ID: 25 | Rating: 0 | rate: / Reply Quote | |
I've just attached the project, got 4 WUs (why isn't there a limit to 1 per computer) but none of those started asap, although both are at least named "nci". The server was slightly misconfigured. Right now it handles the work as "nci". The app has been changed a bit, instead of exiting immediately if the sensor is not present, it waits a while. | |
ID: 27 | Rating: 0 | rate: / Reply Quote | |
This time it started asap as ecpected, it was only one DLed, it runs as nci with 0.01 CPU, it doesn't error out. | |
ID: 28 | Rating: 0 | rate: / Reply Quote | |
They error with this one after nearly exact 6000sec: <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255) </message> <stderr_txt> error finding DataStore: The specified device was not found </stderr_txt> ]]> As they don't use any ressources it's fine with me that I don't get any reward, but are you testing something with them or just the server? ____________ Gruesse vom Saenger | |
ID: 29 | Rating: 0 | rate: / Reply Quote | |
These workunits are used to test communication with the sensors. | |
ID: 30 | Rating: 0 | rate: / Reply Quote | |
Message boards :
Number crunching :
nci not starting asap as expected