Client suspended work for another task?
Posted: Fri Mar 27, 2020 6:52 am
Hi all,
I have a client running for a few days now.
All working well so far, but for a few days now, I have an unfinished task (14 minutes to go), that the client stopped working on in favor of a new work unit.
As far as I remember, that was before the Timeout was reached, but I'm not certain.
![Image](https://dialin.mcr42.de/fah.png)
Update:
The log reads:
Funny thing is, the client seems to have asked for more work before finishing the job, and the core crashed after that.
It then started working on the new task, so a BSOD is not the cause. (Thus, I_m not pdating the title as proposed.)
However, meanwhile the client finished the newer task, and seems to have returned to the old one.
Update: Yep, confirmed, it finished the old task and published the results.
I have a client running for a few days now.
All working well so far, but for a few days now, I have an unfinished task (14 minutes to go), that the client stopped working on in favor of a new work unit.
As far as I remember, that was before the Timeout was reached, but I'm not certain.
![Image](https://dialin.mcr42.de/fah.png)
Update:
The log reads:
Code: Select all
******************************* Date: 2020-03-26 *******************************
11:57:05:WU02:FS01:0x22:Completed 1920000 out of 2000000 steps (96%)
12:11:40:WU02:FS01:0x22:Completed 1940000 out of 2000000 steps (97%)
12:26:10:WU02:FS01:0x22:Completed 1960000 out of 2000000 steps (98%)
12:41:02:WU02:FS01:0x22:Completed 1980000 out of 2000000 steps (99%)
12:41:02:WU01:FS01:Connecting to 65.254.110.245:8080
12:41:03:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
...
12:42:04:WU01:FS01:Connecting to 18.218.241.186:80
12:42:04:WU01:FS01:Assigned to work server 140.163.4.231
12:42:04:WU01:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:GK106 [GeForce GTX 765M] from 140.163.4.231
12:42:04:WU01:FS01:Connecting to 140.163.4.231:8080
12:42:25:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
12:42:25:WU01:FS01:Connecting to 140.163.4.231:80
12:44:46:WU01:FS01:Downloading 7.85MiB
12:44:52:WU01:FS01:Download 30.26%
12:44:58:WU01:FS01:Download 66.10%
12:45:03:WU01:FS01:Download complete
12:45:03:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:11750 run:0 clone:1142 gen:10 core:0x22 unit:0x000000198ca304e75e6a801f85923962
12:54:10:WARNING:WU02:FS01:FahCore returned an unknown error code which probably indicates that it crashed
12:54:10:WARNING:WU02:FS01:FahCore returned: WU_STALLED (127 = 0x7f)
12:54:10:WU01:FS01:Starting
12:54:10:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\mcr\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/Core_22.fah/FahCore_22.exe -dir 01 -suffix 01 -version 705 -lifeline 2152 -checkpoint 15 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu 0
12:54:10:WU01:FS01:Started FahCore on PID 8692
12:54:10:WU01:FS01:Core PID:6080
12:54:10:WU01:FS01:FahCore 0x22 started
12:54:11:WU01:FS01:0x22:*********************** Log Started 2020-03-26T12:54:10Z ***********************
It then started working on the new task, so a BSOD is not the cause. (Thus, I_m not pdating the title as proposed.)
However, meanwhile the client finished the newer task, and seems to have returned to the old one.
Update: Yep, confirmed, it finished the old task and published the results.