The "Received short response" messages are more often connected to connections being blocked by firewall or anti-malware software. The FAHClient process needs the same permissions to use HTTP over ports 8080 and/or 80 as a web browser. Many anti-malware software will allow this for "known" browsers such as Chrome, Firefox or Opera; but FAHClient is not one of the recognized ones.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
02:24:53:WU00:FS01:0x22:Project: 11744 (Run 0, Clone 8349, Gen 0)
02:24:53:WU00:FS01:0x22:Unit: 0x000000008ca304f15e6bc406da3f5e39
02:24:53:WU00:FS01:0x22:Reading tar file core.xml
02:24:53:WU00:FS01:0x22:Reading tar file integrator.xml
02:24:53:WU00:FS01:0x22:Reading tar file state.xml
02:24:53:WU00:FS01:0x22:Reading tar file system.xml
02:24:54:WU00:FS01:0x22:Digital signatures verified
02:24:54:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
02:24:54:WU00:FS01:0x22:Version 0.0.2
02:25:09:WU00:FS01:0x22:Completed 0 out of 1000000 steps (0%)
02:25:09:WU00:FS01:0x22:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
02:26:27:WU00:FS01:0x22:Completed 10000 out of 1000000 steps (1%)
02:27:44:WU00:FS01:0x22:Completed 20000 out of 1000000 steps (2%)
02:29:04:WU00:FS01:0x22:Completed 30000 out of 1000000 steps (3%)
02:30:28:WU00:FS01:0x22:Completed 40000 out of 1000000 steps (4%)
02:31:54:WU00:FS01:0x22:Completed 50000 out of 1000000 steps (5%)
02:33:20:WU00:FS01:0x22:Completed 60000 out of 1000000 steps (6%)
02:34:40:WU00:FS01:0x22:Completed 70000 out of 1000000 steps (7%)
02:35:58:WU00:FS01:0x22:Completed 80000 out of 1000000 steps (8%)
02:37:15:WU00:FS01:0x22:Completed 90000 out of 1000000 steps (9%)
02:38:32:WU00:FS01:0x22:Completed 100000 out of 1000000 steps (10%)
02:39:52:WU00:FS01:0x22:Completed 110000 out of 1000000 steps (11%)
02:41:11:WU00:FS01:0x22:Completed 120000 out of 1000000 steps (12%)
02:42:27:WU00:FS01:0x22:Completed 130000 out of 1000000 steps (13%)
02:43:43:WU00:FS01:0x22:Completed 140000 out of 1000000 steps (14%)
02:45:02:WU00:FS01:0x22:Completed 150000 out of 1000000 steps (15%)
02:46:19:WU00:FS01:0x22:Bad State detected... attempting to resume from last good checkpoint. Is your system overclocked?
02:46:19:WU00:FS01:0x22:Following exception occured: Particle coordinate is nan
02:46:34:WU00:FS01:0x22:Bad State detected... attempting to resume from last good checkpoint. Is your system overclocked?
02:46:34:WU00:FS01:0x22:Following exception occured: Particle coordinate is nan
02:46:50:WU00:FS01:0x22:Bad State detected... attempting to resume from last good checkpoint. Is your system overclocked?
02:46:50:WU00:FS01:0x22:Following exception occured: Particle coordinate is nan
02:46:50:WU00:FS01:0x22:ERROR:114: Max Retries Reached
02:46:50:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
02:46:50:WU00:FS01:0x22:Saving result file badstate-0.xml
02:46:50:WU00:FS01:0x22:Saving result file badstate-1.xml
02:46:50:WU00:FS01:0x22:Saving result file badstate-2.xml
02:46:51:WU00:FS01:0x22:Saving result file checkpointState.xml
02:46:51:WU00:FS01:0x22:Saving result file checkpt.crc
02:46:51:WU00:FS01:0x22:Saving result file positions.xtc
02:46:51:WU00:FS01:0x22:Saving result file science.log
02:46:51:WU00:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
02:46:51:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
02:46:51:WU00:FS01:Sending unit results: id:00 state:SEND error:FAULTY project:11744 run:0 clone:8349 gen:0 core:0x22 unit:0x000000008ca304f15e6bc406da3f5e39
I even went default GPU profile because I was thinking it not may like mem OC, but it won't make any difference. I have got done only few thouse new WU's.
Mod note: pleas use Code tags on log files, not Quote
This message usually is associated with a problem with the OpenCL setup. But since your system can also proceed at other times, do you happen to be folding on a system that is a laptop that switched between using an integrated GPU for low power and a discrete GPU when more power is needed?
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
This message usually is associated with a problem with the OpenCL setup. But since your system can also proceed at other times, do you happen to be folding on a system that is a laptop that switched between using an integrated GPU for low power and a discrete GPU when more power is needed?
06:59:38:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:59:59:ERROR:WU01:FS01:Exception: Failed to connect to 140.163.4.231:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
07:00:21:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
07:00:42:ERROR:WU01:FS01:Exception: Failed to connect to 140.163.4.231:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
CPU is pulling jobs fine but GPU is failing from this server. Host traces out to the internet but dies at the far end; telnet on both ports is unresponsive. GPU is a Vega 64
Last edited by schertt on Sat Mar 14, 2020 7:13 am, edited 1 time in total.
05:46:10:WU02:FS01:Assigned to work server 140.163.4.231
05:46:10:WU02:FS01:Requesting new work unit for slot 01: READY gpu:0:GP106 [GeForce GTX 1060 3GB] 3935 from 140.163.4.231
05:46:10:WU02:FS01:Connecting to 140.163.4.231:8080
05:46:31:ERROR:WU02:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
05:57:16:WU02:FS01:Assigned to work server 140.163.4.231
05:57:16:WU02:FS01:Requesting new work unit for slot 01: READY gpu:0:GP106 [GeForce GTX 1060 3GB] 3935 from 140.163.4.231
05:57:16:WU02:FS01:Connecting to 140.163.4.231:8080
05:57:37:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80
05:57:37:WU02:FS01:Connecting to 140.163.4.231:80
05:57:58:ERROR:WU02:FS01:Exception: Failed to connect to 140.163.4.231:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:08:21:WU02:FS01:Assigned to work server 140.163.4.241
06:08:21:WU02:FS01:Requesting new work unit for slot 01: READY gpu:0:GP106 [GeForce GTX 1060 3GB] 3935 from 140.163.4.241
06:08:21:WU02:FS01:Connecting to 140.163.4.241:8080
06:10:13:ERROR:WU02:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
Yes, it's a known issue, there are a couple other discussion threads about this. If you leave F@H running it will keep trying to connect & may eventually get through. If you do get through, the downloads may be slow. I've been seeing download times as long as an hour in some cases, but they do eventually complete & start folding.
For the connection problem in the first posts...
I'm having the same problem and I have some questions:
- Is this problem typical? I'm new to Folding@home, and am not used to having idle GPUs!
- How long until this is typically resolved?
- Have there been any/many cases where the entire project is out of GPU work?
Its not unheard of to have an idle gpu and there have been occasions in the past when the project has been low or out of work. However in this instance the cause is a good one, usually its a server that's crashed. A couple of big cloud computing companies have dedicated serious resources to the project. By serious I mean 6,000 gpu's from one and over 60,000 idle cpu cores from another. These are causing unprecedented demand on the server infrastructure. F@H usually issues around ~4k WU per hour on average, this morning its at over ~27k. The teams are spinning up new servers and additional projects as fast as they can but it all takes time. please be patient and a WU will come your way eventually. If you want to try and and hurry the process up try pausing then unpausing your slots - you *MAY* get a WU quicker but no guarantees
Thanks for the response. I understand that current turbulence for Folding@home is something the team is trying to handle. I'm just trying to figure out the best configuration for BOINC and Folding@home for my resources, and I really hate to see GPUs that I've reallocated to be dedicated to Folding@home, now go idle.
I am hopeful for more transparency about these connection problems, in the form of announcements.
Both 140.163.4.231 and 140.163.4.241 are up and down like a yoyo. I wish we could select what work our GPUs could work on. Currently, most of my GPUs are not working now. Waste of time! Sort it please.