Issues submitting WUs - Received short response

Moderators: Site Moderators, FAHC Science Team

Post Reply
Sashleycatty
Posts: 6
Joined: Wed Mar 18, 2020 5:26 pm

Issues submitting WUs - Received short response

Post by Sashleycatty »

Hi.

One of my machines is having trouble submitting WUs when they are completed. The log is filled with errors to this nature: (only warnings and errors are displayed, otherwise the log is too large to post here).

Code: Select all

*********************** Log Started 2021-01-16T19:28:00Z ***********************
19:28:01:ERROR:GPU with PCI bus 65 and slot 0 not found.: Deleting folding slot.
19:28:01:WARNING:FS01:No CUDA or OpenCL 1.2+ support detected for GPU slot 01: gpu:-1:-1.  Disabling.
19:28:01:WARNING:WU00:Slot ID 1 no longer exists, migrating to FS00
19:28:01:WARNING:WU02:No longer matches Slot 0's configuration, migrating to FS02
19:28:27:WU02:FS02:0x22:ERROR:125: Failed to create a GPU-enabled OpenMM Context.
19:28:27:WU00:FS00:0x22:ERROR:125: Failed to create a GPU-enabled OpenMM Context.
19:28:28:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
19:28:28:WARNING:WU02:FS02:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
19:28:32:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:29:07:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
19:29:39:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:30:14:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
19:30:47:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:31:21:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
19:31:57:WU04:FS02:0x22:WARNING:Console control signal 1 on PID 18956
19:32:22:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:32:58:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
19:34:59:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:35:35:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
19:39:14:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:39:51:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
19:44:32:WU04:FS02:0x22:WARNING:Console control signal 1 on PID 10660
19:46:05:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:46:49:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
19:57:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:57:59:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
20:15:07:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
20:15:42:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
20:44:09:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
20:44:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
21:31:08:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
21:31:43:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
22:31:08:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
22:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
23:31:08:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
23:31:44:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
00:31:09:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
00:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
00:33:54:WARNING:WU03:FS00:WorkServer connection failed on port 8080 trying 80
00:33:57:WARNING:WU03:FS00:Exception: Failed to send results to work server: Failed to connect to 129.32.209.203:80: No connection could be made because the target machine actively refused it.
******************************* Date: 2021-01-17 *******************************
01:31:09:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
01:31:44:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
02:31:09:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
02:31:44:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
03:31:09:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
03:31:44:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
04:31:09:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
04:31:44:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
05:31:09:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
05:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
06:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
06:31:44:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
******************************* Date: 2021-01-17 *******************************
07:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
07:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
08:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
08:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
09:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
09:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
10:13:30:WU02:FS02:0x22:WARNING:Console control signal 1 on PID 10816
10:13:30:WU03:FS00:0x22:WARNING:Console control signal 1 on PID 6032
10:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
10:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
11:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
11:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
12:19:00:WU00:FS00:0x22:WARNING:Console control signal 1 on PID 5128
12:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
12:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
******************************* Date: 2021-01-17 *******************************
13:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
14:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
14:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
15:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
15:31:47:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
16:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
16:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
17:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
17:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
11:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
11:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
12:19:00:WU00:FS00:0x22:WARNING:Console control signal 1 on PID 5128
12:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
12:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
******************************* Date: 2021-01-17 *******************************
13:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
13:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
14:31:10:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
14:31:45:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
15:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
15:31:47:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
16:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
16:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
17:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
17:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
17:49:36:ERROR:Receive error: 10053: An established connection was aborted by the software in your host machine.
18:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
18:31:47:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
******************************* Date: 2021-01-17 *******************************
19:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
19:31:47:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
20:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
20:31:47:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
21:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
21:31:47:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
22:08:18:WU02:FS00:0x22:WARNING:Console control signal 1 on PID 18912
22:31:11:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
22:31:46:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
23:31:12:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
23:31:51:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
23:36:28:WU02:FS00:0x22:WARNING:Console control signal 1 on PID 3112
I believe the WUs are submitted eventually, it just takes ages. Sometimes they have 30+ attempts. Is this a problem or should I just ignore it?

The two GPUs in this machine are GTX 1650 SUPER and GTX 1660 SUPER. My other machine with an RTX 2080 Ti doesn't have such warnings in the logs. By the way, I troubleshooted the "Bad Work Unit" errors because my GPUs were incorrectly configured and I had to change their positions in the PCI-E slots. With that remedied, they are fully operational and stable. They have had their power limit lowered with the "Auto OC" voltage/frequency state software run to improve efficiency.

Additional information that may be useful:

This machine runs Kaspersky Internet Security 2020 but the FAH client and its directory are enabled in the full exclusions list.

Here is one of the WUs that takes a long time to submit:

Image

Thank you in advance for any advice you can provide.
Top
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:
Contact PantherX

Re: Issues submitting WUs - Received short response

Post by PantherX »

Welcome to the F@H Forum Sashleycatty,

This section of the log log doesn't seem great as WUs have failed on your system and we don't know why. Moreover, can you please post the first 100 lines which will inform us of what the system configuration is and what the client settings are?

Code: Select all

19:28:01:ERROR:GPU with PCI bus 65 and slot 0 not found.: Deleting folding slot.
19:28:01:WARNING:FS01:No CUDA or OpenCL 1.2+ support detected for GPU slot 01: gpu:-1:-1.  Disabling.
19:28:01:WARNING:WU00:Slot ID 1 no longer exists, migrating to FS00
19:28:01:WARNING:WU02:No longer matches Slot 0's configuration, migrating to FS02
19:28:27:WU02:FS02:0x22:ERROR:125: Failed to create a GPU-enabled OpenMM Context.
19:28:27:WU00:FS00:0x22:ERROR:125: Failed to create a GPU-enabled OpenMM Context.
19:28:28:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
19:28:28:WARNING:WU02:FS02:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
It seems that the one cause of this message is that the firewall/router blocks the last ACK packet causing the client to continue trying to upload:
Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0

Can you try to completely disable Kaspersky and see if that behavior changes or not?
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Top
Sashleycatty
Posts: 6
Joined: Wed Mar 18, 2020 5:26 pm

Re: Issues submitting WUs - Received short response

Post by Sashleycatty »

Hello, thank you for your reply.

Here is the log start, to when the Bad Work Units occurred:

Code: Select all

*********************** Log Started 2021-01-16T19:28:00Z ***********************
19:28:00:******************************* libFAH ********************************
19:28:00:           Date: Oct 20 2020
19:28:00:           Time: 13:36:55
19:28:00:       Revision: 5ca109d295a6245e2a2f590b3d0085ad5e567aeb
19:28:00:         Branch: master
19:28:00:       Compiler: Visual C++ 2015
19:28:00:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:28:00:       Platform: win32 10
19:28:00:           Bits: 32
19:28:00:           Mode: Release
19:28:00:****************************** FAHClient ******************************
19:28:00:        Version: 7.6.21
19:28:00:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:28:00:      Copyright: 2020 foldingathome.org
19:28:00:       Homepage: https://foldingathome.org/
19:28:00:           Date: Oct 20 2020
19:28:00:           Time: 13:41:04
19:28:00:       Revision: 6efbf0e138e22d3963e6a291f78dcb9c6422a278
19:28:00:         Branch: master
19:28:00:       Compiler: Visual C++ 2015
19:28:00:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:28:00:       Platform: win32 10
19:28:00:           Bits: 32
19:28:00:           Mode: Release
19:28:00:         Config: C:\ProgramData\FAHClient\config.xml
19:28:00:******************************** CBang ********************************
19:28:00:           Date: Oct 20 2020
19:28:00:           Time: 11:36:18
19:28:00:       Revision: 7e4ce85225d7eaeb775e87c31740181ca603de60
19:28:00:         Branch: master
19:28:00:       Compiler: Visual C++ 2015
19:28:00:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:28:00:       Platform: win32 10
19:28:00:           Bits: 32
19:28:00:           Mode: Release
19:28:00:******************************* System ********************************
19:28:00:            CPU: AMD Ryzen Threadripper 2950X 16-Core Processor
19:28:00:         CPU ID: AuthenticAMD Family 23 Model 8 Stepping 2
19:28:00:           CPUs: 32
19:28:00:         Memory: 63.87GiB
19:28:00:    Free Memory: 60.22GiB
19:28:00:        Threads: WINDOWS_THREADS
19:28:00:     OS Version: 6.2
19:28:00:    Has Battery: false
19:28:00:     On Battery: false
19:28:00:     UTC Offset: 0
19:28:00:            PID: 15568
19:28:00:            CWD: C:\ProgramData\FAHClient
19:28:00:  Win32 Service: false
19:28:00:             OS: Windows 10 Enterprise
19:28:00:        OS Arch: AMD64
19:28:00:           GPUs: 2
19:28:00:          GPU 0: Bus:10 Slot:0 Func:0 NVIDIA:7 TU116 [GeForce GTX 1650 SUPER]
19:28:00:          GPU 1: Bus:66 Slot:0 Func:0 NVIDIA:7 TU116 [GeForce GTX 1660 SUPER]
19:28:00:  CUDA Device 0: Platform:0 Device:0 Bus:66 Slot:0 Compute:7.5 Driver:11.2
19:28:00:  CUDA Device 1: Platform:0 Device:1 Bus:10 Slot:0 Compute:7.5 Driver:11.2
19:28:00:OpenCL Device 0: Platform:0 Device:0 Bus:66 Slot:0 Compute:1.2 Driver:460.79
19:28:00:OpenCL Device 1: Platform:0 Device:1 Bus:10 Slot:0 Compute:1.2 Driver:460.79
19:28:00:***********************************************************************
19:28:00:<config>
19:28:00:  <!-- Network -->
19:28:00:  <proxy v=':8080'/>
19:28:00:
19:28:00:  <!-- Slot Control -->
19:28:00:  <power v='full'/>
19:28:00:
19:28:00:  <!-- User Information -->
19:28:00:  <passkey v='*****'/>
19:28:00:  <team v='50711'/>
19:28:00:  <user v='Sashleycatty'/>
19:28:00:
19:28:00:  <!-- Folding Slots -->
19:28:00:  <slot id='1' type='GPU'>
19:28:00:    <paused v='true'/>
19:28:00:    <pci-bus v='65'/>
19:28:00:    <pci-slot v='0'/>
19:28:00:  </slot>
19:28:00:  <slot id='0' type='GPU'>
19:28:00:    <pci-bus v='10'/>
19:28:00:    <pci-slot v='0'/>
19:28:00:  </slot>
19:28:00:</config>
19:28:01:Trying to access database...
19:28:01:Successfully acquired database lock
19:28:01:ERROR:GPU with PCI bus 65 and slot 0 not found.: Deleting folding slot.
19:28:01:WARNING:FS01:No CUDA or OpenCL 1.2+ support detected for GPU slot 01: gpu:-1:-1.  Disabling.
19:28:01:FS00:Initialized folding slot 00: gpu:10:0 TU116 [GeForce GTX 1650 SUPER]
19:28:01:FS02:Initialized folding slot 02: gpu:66:0 TU116 [GeForce GTX 1660 SUPER]
19:28:01:WARNING:WU00:Slot ID 1 no longer exists, migrating to FS00
19:28:01:WARNING:WU02:No longer matches Slot 0's configuration, migrating to FS02
19:28:01:WU00:FS00:Starting
19:28:01:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.13/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 706 -lifeline 15568 -checkpoint 15 -opencl-platform 0 -opencl-device 1 -cuda-device 1 -gpu-vendor nvidia -gpu 1 -gpu-usage 100
19:28:01:WU00:FS00:Started FahCore on PID 1124
19:28:01:WU00:FS00:Core PID:15692
19:28:01:WU00:FS00:FahCore 0x22 started
19:28:01:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:17322 run:0 clone:1980 gen:93 core:0x22 unit:0x000007bc0000005d000043aa00000000
19:28:01:WU01:FS01:Uploading 31.01MiB to 140.163.4.200
19:28:01:WU02:FS02:Starting
19:28:01:WU01:FS01:Connecting to 140.163.4.200:8080
19:28:01:WU02:FS02:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.13/Core_22.fah/FahCore_22.exe -dir 02 -suffix 01 -version 706 -lifeline 15568 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor nvidia -gpu 0 -gpu-usage 100
19:28:01:WU02:FS02:Started FahCore on PID 8548
19:28:01:WU02:FS02:Core PID:9240
19:28:01:WU02:FS02:FahCore 0x22 started
19:28:01:WU00:FS00:0x22:*********************** Log Started 2021-01-16T19:28:01Z ***********************
19:28:01:WU00:FS00:0x22:*************************** Core22 Folding@home Core ***************************
19:28:01:WU00:FS00:0x22:       Core: Core22
19:28:01:WU00:FS00:0x22:       Type: 0x22
19:28:01:WU00:FS00:0x22:    Version: 0.0.13
19:28:01:WU00:FS00:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:28:01:WU00:FS00:0x22:  Copyright: 2020 foldingathome.org
19:28:01:WU00:FS00:0x22:   Homepage: https://foldingathome.org/
19:28:01:WU00:FS00:0x22:       Date: Sep 19 2020
19:28:01:WU00:FS00:0x22:       Time: 02:35:58
19:28:01:WU00:FS00:0x22:   Revision: 571cf95de6de2c592c7c3ed48fcfb2e33e9ea7d3
19:28:01:WU00:FS00:0x22:     Branch: core22-0.0.13
19:28:01:WU00:FS00:0x22:   Compiler: Visual C++ 2015
19:28:01:WU00:FS00:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
19:28:01:WU00:FS00:0x22:             -DOPENMM_GIT_HASH="\"189320d0\""
19:28:01:WU00:FS00:0x22:   Platform: win32 10
19:28:01:WU00:FS00:0x22:       Bits: 64
19:28:01:WU00:FS00:0x22:       Mode: Release
19:28:01:WU00:FS00:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
19:28:01:WU00:FS00:0x22:             <peastman@stanford.edu>
19:28:01:WU00:FS00:0x22:       Args: -dir 00 -suffix 01 -version 706 -lifeline 1124 -checkpoint 15
19:28:01:WU00:FS00:0x22:             -opencl-platform 0 -opencl-device 1 -cuda-device 1 -gpu-vendor
19:28:01:WU00:FS00:0x22:             nvidia -gpu 1 -gpu-usage 100
19:28:01:WU00:FS00:0x22:************************************ libFAH ************************************
19:28:01:WU00:FS00:0x22:       Date: Sep 7 2020
19:28:01:WU00:FS00:0x22:       Time: 19:09:56
19:28:01:WU00:FS00:0x22:   Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
19:28:01:WU00:FS00:0x22:     Branch: HEAD
19:28:01:WU00:FS00:0x22:   Compiler: Visual C++ 2015
19:28:01:WU00:FS00:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
19:28:01:WU00:FS00:0x22:   Platform: win32 10
19:28:01:WU00:FS00:0x22:       Bits: 64
19:28:01:WU00:FS00:0x22:       Mode: Release
19:28:01:WU00:FS00:0x22:************************************ CBang *************************************
19:28:01:WU00:FS00:0x22:       Date: Sep 7 2020
19:28:01:WU00:FS00:0x22:       Time: 19:08:30
19:28:01:WU00:FS00:0x22:   Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
19:28:01:WU00:FS00:0x22:     Branch: HEAD
19:28:01:WU00:FS00:0x22:   Compiler: Visual C++ 2015
19:28:01:WU00:FS00:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
19:28:01:WU00:FS00:0x22:   Platform: win32 10
19:28:01:WU00:FS00:0x22:       Bits: 64
19:28:01:WU00:FS00:0x22:       Mode: Release
19:28:01:WU00:FS00:0x22:************************************ System ************************************
19:28:02:WU00:FS00:0x22:        CPU: AMD Ryzen Threadripper 2950X 16-Core Processor
19:28:02:WU00:FS00:0x22:     CPU ID: AuthenticAMD Family 23 Model 8 Stepping 2
19:28:02:WU00:FS00:0x22:       CPUs: 32
19:28:02:WU00:FS00:0x22:     Memory: 63.87GiB
19:28:02:WU00:FS00:0x22:Free Memory: 60.05GiB
19:28:02:WU00:FS00:0x22:    Threads: WINDOWS_THREADS
19:28:02:WU00:FS00:0x22: OS Version: 6.2
19:28:02:WU00:FS00:0x22:Has Battery: false
19:28:02:WU00:FS00:0x22: On Battery: false
19:28:02:WU00:FS00:0x22: UTC Offset: 0
19:28:02:WU00:FS00:0x22:        PID: 15692
19:28:02:WU00:FS00:0x22:        CWD: C:\ProgramData\FAHClient\work
19:28:02:WU00:FS00:0x22:************************************ OpenMM ************************************
19:28:02:WU00:FS00:0x22:   Revision: 189320d0
19:28:02:WU00:FS00:0x22:********************************************************************************
19:28:02:WU00:FS00:0x22:Project: 17321 (Run 0, Clone 1151, Gen 61)
19:28:02:WU00:FS00:0x22:Unit: 0x00000000000000000000000000000000
19:28:02:WU00:FS00:0x22:Digital signatures verified
19:28:02:WU00:FS00:0x22:Folding@home GPU Core22 Folding@home Core
19:28:02:WU00:FS00:0x22:Version 0.0.13
19:28:02:WU00:FS00:0x22:  Checkpoint write interval: 25000 steps (2%) [50 total]
19:28:02:WU00:FS00:0x22:  JSON viewer frame write interval: 12500 steps (1%) [100 total]
19:28:02:WU00:FS00:0x22:  XTC frame write interval: 250000 steps (20%) [5 total]
19:28:02:WU00:FS00:0x22:  Global context and integrator variables write interval: disabled
19:28:02:WU00:FS00:0x22:There are 4 platforms available.
19:28:02:WU00:FS00:0x22:Platform 0: Reference
19:28:02:WU00:FS00:0x22:Platform 1: CPU
19:28:02:WU00:FS00:0x22:Platform 2: OpenCL
19:28:02:WU00:FS00:0x22:  opencl-device 1 specified
19:28:02:WU00:FS00:0x22:Platform 3: CUDA
19:28:02:WU00:FS00:0x22:  cuda-device 1 specified
19:28:02:WU02:FS02:0x22:*********************** Log Started 2021-01-16T19:28:01Z ***********************
19:28:02:WU02:FS02:0x22:*************************** Core22 Folding@home Core ***************************
19:28:02:WU02:FS02:0x22:       Core: Core22
19:28:02:WU02:FS02:0x22:       Type: 0x22
19:28:02:WU02:FS02:0x22:    Version: 0.0.13
19:28:02:WU02:FS02:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:28:02:WU02:FS02:0x22:  Copyright: 2020 foldingathome.org
19:28:02:WU02:FS02:0x22:   Homepage: https://foldingathome.org/
19:28:02:WU02:FS02:0x22:       Date: Sep 19 2020
19:28:02:WU02:FS02:0x22:       Time: 02:35:58
19:28:02:WU02:FS02:0x22:   Revision: 571cf95de6de2c592c7c3ed48fcfb2e33e9ea7d3
19:28:02:WU02:FS02:0x22:     Branch: core22-0.0.13
19:28:02:WU02:FS02:0x22:   Compiler: Visual C++ 2015
19:28:02:WU02:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
19:28:02:WU02:FS02:0x22:             -DOPENMM_GIT_HASH="\"189320d0\""
19:28:02:WU02:FS02:0x22:   Platform: win32 10
19:28:02:WU02:FS02:0x22:       Bits: 64
19:28:02:WU02:FS02:0x22:       Mode: Release
19:28:02:WU02:FS02:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
19:28:02:WU02:FS02:0x22:             <peastman@stanford.edu>
19:28:02:WU02:FS02:0x22:       Args: -dir 02 -suffix 01 -version 706 -lifeline 8548 -checkpoint 15
19:28:02:WU02:FS02:0x22:             -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor
19:28:02:WU02:FS02:0x22:             nvidia -gpu 0 -gpu-usage 100
19:28:02:WU02:FS02:0x22:************************************ libFAH ************************************
19:28:02:WU02:FS02:0x22:       Date: Sep 7 2020
19:28:02:WU02:FS02:0x22:       Time: 19:09:56
19:28:02:WU02:FS02:0x22:   Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
19:28:02:WU02:FS02:0x22:     Branch: HEAD
19:28:02:WU02:FS02:0x22:   Compiler: Visual C++ 2015
19:28:02:WU02:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
19:28:02:WU02:FS02:0x22:   Platform: win32 10
19:28:02:WU02:FS02:0x22:       Bits: 64
19:28:02:WU02:FS02:0x22:       Mode: Release
19:28:02:WU02:FS02:0x22:************************************ CBang *************************************
19:28:02:WU02:FS02:0x22:       Date: Sep 7 2020
19:28:02:WU02:FS02:0x22:       Time: 19:08:30
19:28:02:WU02:FS02:0x22:   Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
19:28:02:WU02:FS02:0x22:     Branch: HEAD
19:28:02:WU02:FS02:0x22:   Compiler: Visual C++ 2015
19:28:02:WU02:FS02:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
19:28:02:WU02:FS02:0x22:   Platform: win32 10
19:28:02:WU02:FS02:0x22:       Bits: 64
19:28:02:WU02:FS02:0x22:       Mode: Release
19:28:02:WU02:FS02:0x22:************************************ System ************************************
19:28:02:WU02:FS02:0x22:        CPU: AMD Ryzen Threadripper 2950X 16-Core Processor
19:28:02:WU02:FS02:0x22:     CPU ID: AuthenticAMD Family 23 Model 8 Stepping 2
19:28:02:WU02:FS02:0x22:       CPUs: 32
19:28:02:WU02:FS02:0x22:     Memory: 63.87GiB
19:28:02:WU02:FS02:0x22:Free Memory: 59.93GiB
19:28:02:WU02:FS02:0x22:    Threads: WINDOWS_THREADS
19:28:02:WU02:FS02:0x22: OS Version: 6.2
19:28:02:WU02:FS02:0x22:Has Battery: false
19:28:02:WU02:FS02:0x22: On Battery: false
19:28:02:WU02:FS02:0x22: UTC Offset: 0
19:28:02:WU02:FS02:0x22:        PID: 9240
19:28:02:WU02:FS02:0x22:        CWD: C:\ProgramData\FAHClient\work
19:28:02:WU02:FS02:0x22:************************************ OpenMM ************************************
19:28:02:WU02:FS02:0x22:   Revision: 189320d0
19:28:02:WU02:FS02:0x22:********************************************************************************
19:28:02:WU02:FS02:0x22:Project: 17322 (Run 0, Clone 1048, Gen 101)
19:28:02:WU02:FS02:0x22:Unit: 0x00000000000000000000000000000000
19:28:02:WU02:FS02:0x22:Digital signatures verified
19:28:02:WU02:FS02:0x22:Folding@home GPU Core22 Folding@home Core
19:28:02:WU02:FS02:0x22:Version 0.0.13
19:28:02:WU02:FS02:0x22:  Checkpoint write interval: 15000 steps (2%) [50 total]
19:28:02:WU02:FS02:0x22:  JSON viewer frame write interval: 7500 steps (1%) [100 total]
19:28:02:WU02:FS02:0x22:  XTC frame write interval: 250000 steps (33%) [3 total]
19:28:02:WU02:FS02:0x22:  Global context and integrator variables write interval: disabled
19:28:02:WU02:FS02:0x22:There are 4 platforms available.
19:28:02:WU02:FS02:0x22:Platform 0: Reference
19:28:02:WU02:FS02:0x22:Platform 1: CPU
19:28:02:WU02:FS02:0x22:Platform 2: OpenCL
19:28:02:WU02:FS02:0x22:  opencl-device 0 specified
19:28:02:WU02:FS02:0x22:Platform 3: CUDA
19:28:02:WU02:FS02:0x22:  cuda-device 0 specified
19:28:25:WU00:FS00:0x22:Attempting to create CUDA context:
19:28:25:WU00:FS00:0x22:  Configuring platform CUDA
19:28:26:WU02:FS02:0x22:Attempting to create CUDA context:
19:28:26:WU02:FS02:0x22:  Configuring platform CUDA
19:28:27:WU02:FS02:0x22:Failed to create CUDA context:
19:28:27:WU00:FS00:0x22:Failed to create CUDA context:
19:28:27:WU02:FS02:0x22:Error initializing FFT: 11
19:28:27:WU00:FS00:0x22:Error uploading array exclusionTiles: CUDA_ERROR_UNKNOWN (999)
19:28:27:WU02:FS02:0x22:Attempting to create OpenCL context:
19:28:27:WU00:FS00:0x22:Attempting to create OpenCL context:
19:28:27:WU02:FS02:0x22:  Configuring platform OpenCL
19:28:27:WU00:FS00:0x22:  Configuring platform OpenCL
19:28:27:WU02:FS02:0x22:Failed to create OpenCL context:
19:28:27:WU00:FS00:0x22:Failed to create OpenCL context:
19:28:27:WU02:FS02:0x22:Error initializing context: clCreateContext (-6)
19:28:27:WU00:FS00:0x22:Error initializing context: clCreateContext (-6)
19:28:27:WU02:FS02:0x22:ERROR:125: Failed to create a GPU-enabled OpenMM Context.
19:28:27:WU00:FS00:0x22:ERROR:125: Failed to create a GPU-enabled OpenMM Context.
19:28:27:WU02:FS02:0x22:Saving result file ..\logfile_01.txt
19:28:27:WU00:FS00:0x22:Saving result file ..\logfile_01.txt
19:28:27:WU02:FS02:0x22:Saving result file science.log
19:28:27:WU00:FS00:0x22:Saving result file science.log
19:28:27:WU02:FS02:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
19:28:27:WU00:FS00:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
19:28:28:WARNING:WU00:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
19:28:28:WU00:FS00:Sending unit results: id:00 state:SEND error:FAULTY project:17321 run:0 clone:1151 gen:61 core:0x22 unit:0x0000047f0000003d000043a900000000
19:28:28:WU00:FS00:Uploading 39.00KiB to 140.163.4.200
19:28:28:WARNING:WU02:FS02:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
19:28:28:WU00:FS00:Connecting to 140.163.4.200:8080
19:28:28:WU02:FS02:Sending unit results: id:02 state:SEND error:FAULTY project:17322 run:0 clone:1048 gen:101 core:0x22 unit:0x0000041800000065000043aa00000000
19:28:28:WU02:FS02:Uploading 44.00KiB to 140.163.4.200
19:28:28:WU02:FS02:Connecting to 140.163.4.200:8080
19:28:28:WU03:FS00:Connecting to assign1.foldingathome.org:80
19:28:28:WU04:FS02:Connecting to assign1.foldingathome.org:80
19:28:29:WU00:FS00:Upload complete
19:28:29:WU02:FS02:Upload complete
19:28:29:WU00:FS00:Server responded WORK_ACK (400)
19:28:29:WU00:FS00:Cleaning up
19:28:29:WU02:FS02:Server responded WORK_ACK (400)
19:28:29:WU02:FS02:Cleaning up
The client has been restarted many times as I was setting up my server, and running a significant amount of other software (WCG for CPU Compute, for example). The machine is now left on 24/7, but the GPUs are not overclocked and haven't created any more Bad Work Units - I wonder if this was a result of my changing the PCIE locations of the cards? It always concerns me when a fault like this occurs.

I will disable KIS for a few days and see if it fixes the issue. I run some forwarded ports on this machine so Ideally I'd like to have it enabled with FAH allowed through, but for debugging sake I 'll test it. My Router has a firewall but it also serves another machine with the FAH client; and a 2080 Ti, which has no issues so I think it is local to this machine.

Thank you for your assistance it is greatly appreciated!

Best regards,
Ash
Top
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Issues submitting WUs - Received short response

Post by bruce »

Blocked ACKs is one place to start. It might also be traceable as a server-based problem.

Every completed WU needs to find its way back to the Work Server that issued it. The "short response" message might indicate that the Work Server that issued the WU is having a problem. If that server has failed, there probably is a Collection Server that can accept the WU and then forward it to the Work Server.

You should be able to find two IP addresses shown in the log to tell us where to look for a server-based problem. (Your extract of the log is too brief.)
Top
Sashleycatty
Posts: 6
Joined: Wed Mar 18, 2020 5:26 pm

Re: Issues submitting WUs - Received short response

Post by Sashleycatty »

bruce wrote:Blocked ACKs is one place to start. It might also be traceable as a server-based problem.

Every completed WU needs to find its way back to the Work Server that issued it. The "short response" message might indicate that the Work Server that issued the WU is having a problem. If that server has failed, there probably is a Collection Server that can accept the WU and then forward it to the Work Server.

You should be able to find two IP addresses shown in the log to tell us where to look for a server-based problem. (Your extract of the log is too brief.)
I have pasted the entire contents of the log into a text file and hosted it on my Onedrive, here: https://1drv.ms/t/s!AnTOAd0W4WuniMkLILK ... w?e=CqgKYL, as the log is too large to copy entirely onto this post (60000 character limit).

Thanks
Top
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Issues submitting WUs - Received short response

Post by bruce »

Thank you for posting the log.

There are numerous errors, not just the one you are asking about. THe first one I see is the setting <pci-bus v='65'/> which doesn't point to a valid device. Perhaps the best solution will be to start over. Do a clean install of FAHClient and let's see what happens next. You can save your
> <!-- User Information -->
> <passkey v='*****'/> (with the uncensored information)
> <team v='50711'/>
> <user v='Sashleycatty'/>
and re-use them

Once a WU is assigned and it's enqueued on a nonexistent device it's unclear what FAHClient should be able to do with the WU or the report that it has been dumped or migrated.
Top
Sashleycatty
Posts: 6
Joined: Wed Mar 18, 2020 5:26 pm

Re: Issues submitting WUs - Received short response

Post by Sashleycatty »

bruce wrote:Thank you for posting the log.

There are numerous errors, not just the one you are asking about. THe first one I see is the setting <pci-bus v='65'/> which doesn't point to a valid device. Perhaps the best solution will be to start over. Do a clean install of FAHClient and let's see what happens next. You can save your
> <!-- User Information -->
> <passkey v='*****'/> (with the uncensored information)
> <team v='50711'/>
> <user v='Sashleycatty'/>
and re-use them

Once a WU is assigned and it's enqueued on a nonexistent device it's unclear what FAHClient should be able to do with the WU or the report that it has been dumped or migrated.
I did swap the cards around to different slots at one point in the motherboard. I think I will do a clean install, as you suggested.

Also, I haven't got any Short Response errors since disabling KIS; I will continue to monitor that and report back but I think it might indeed have been interfering with the ACK response?

Thanks for your help!
Top
Sashleycatty
Posts: 6
Joined: Wed Mar 18, 2020 5:26 pm

Re: Issues submitting WUs - Received short response

Post by Sashleycatty »

I thought I'd post a quick update:

Disabling Kaspersky Internet Security has stopped the 'Short Response' errors.
Top
Post Reply

Return to “Issues with a specific server”