Failed to send error
Moderators: Site Moderators, FAHC Science Team
Failed to send error
One of my laptop is stuck at "Failed to send results" error for CPU job. I am not completely sure if the WU got processed after the deadline time. If the WU gets processed after the deadline time, does this error come? If so, will it go away by itself? Currently the client is retrying repeatedly.
-
- Site Admin
- Posts: 7937
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: Failed to send error
If the WU is past the deadline, the client will delete it. Otherwise the client will retry sending until the WU is accepted or the deadline passes.
We would nee to see information from your log file to see if there was a specific problem with sending the WU back.
We would nee to see information from your log file to see if there was a specific problem with sending the WU back.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Failed to send error
here are some snippets of the log(please let me know if I need to share any other part of the log):
Mod Edit: Added Code Tags - PantherX
Code: Select all
14:42:14:WU01:FS00:0xa7:Completed 490000 out of 500000 steps (98%)
14:48:14:WU01:FS00:0xa7:Completed 495000 out of 500000 steps (99%)
14:54:14:WU01:FS00:0xa7:Completed 500000 out of 500000 steps (100%)
14:54:15:WU01:FS00:0xa7:Saving result file ..\logfile_01.txt
14:54:15:WU01:FS00:0xa7:Saving result file frame18.edr
14:54:15:WU01:FS00:0xa7:Saving result file frame18.trr
14:54:15:WU01:FS00:0xa7:Saving result file frame18.xtc
14:54:15:WU01:FS00:0xa7:Saving result file md.log
14:54:15:WU01:FS00:0xa7:Saving result file science.log
14:54:15:WU01:FS00:0xa7:Folding@home Core Shutdown: FINISHED_UNIT
14:54:16:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
06:36:34:WU01:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
06:36:34:WU01:FS00:0xa7: Type: 0xa7
06:36:34:WU01:FS00:0xa7: Core: Gromacs
06:36:34:WU01:FS00:0xa7: Args: -dir 01 -suffix 01 -version 705 -lifeline 10120 -checkpoint 15 -np
06:36:34:WU01:FS00:0xa7: 3
06:36:34:WU01:FS00:0xa7:************************************ CBang *************************************
06:36:34:WU01:FS00:0xa7: Date: Oct 26 2019
06:36:34:WU01:FS00:0xa7: Time: 01:38:25
06:36:34:WU01:FS00:0xa7: Revision: c46a1a011a24143739ac7218c5a435f66777f62f
06:36:34:WU01:FS00:0xa7: Branch: master
06:36:34:WU01:FS00:0xa7: Compiler: Visual C++ 2008
06:36:34:WU01:FS00:0xa7: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
06:36:34:WU01:FS00:0xa7: Platform: win32 10
06:36:34:WU01:FS00:0xa7: Bits: 64
06:36:34:WU01:FS00:0xa7: Mode: Release
06:36:34:WU01:FS00:0xa7:************************************ System ************************************
06:36:34:WU01:FS00:0xa7: CPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz
06:36:34:WU01:FS00:0xa7: CPU ID: GenuineIntel Family 6 Model 69 Stepping 1
06:36:34:WU01:FS00:0xa7: CPUs: 4
06:36:34:WU01:FS00:0xa7: Memory: 7.53GiB
06:36:34:WU01:FS00:0xa7:Free Memory: 4.18GiB
06:36:34:WU01:FS00:0xa7: Threads: WINDOWS_THREADS
06:36:34:WU01:FS00:0xa7: OS Version: 6.2
06:36:34:WU01:FS00:0xa7:Has Battery: true
06:36:34:WU01:FS00:0xa7: On Battery: false
06:36:34:WU01:FS00:0xa7: UTC Offset: -7
06:36:34:WU01:FS00:0xa7: PID: 10200
06:36:34:WU01:FS00:0xa7: CWD: C:\Users\Owner\AppData\Roaming\FAHClient\work
06:36:34:WU01:FS00:0xa7:******************************** Build - libFAH ********************************
06:36:34:WU01:FS00:0xa7: Version: 0.0.18
06:36:34:WU01:FS00:0xa7: Author: Joseph Coffland <[email protected]>
06:36:34:WU01:FS00:0xa7: Copyright: 2019 foldingathome.org
06:36:34:WU01:FS00:0xa7: Homepage: https://foldingathome.org/
06:36:34:WU01:FS00:0xa7: Date: Oct 26 2019
06:36:34:WU01:FS00:0xa7: Time: 01:52:30
06:36:34:WU01:FS00:0xa7: Revision: c1e3513b1bc0c16013668f2173ee969e5995b38e
06:36:34:WU01:FS00:0xa7: Branch: master
06:36:34:WU01:FS00:0xa7: Compiler: Visual C++ 2008
06:36:34:WU01:FS00:0xa7: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
06:36:34:WU01:FS00:0xa7: Platform: win32 10
06:36:34:WU01:FS00:0xa7: Bits: 64
06:36:34:WU01:FS00:0xa7: Mode: Release
06:36:34:WU01:FS00:0xa7:************************************ Build *************************************
06:36:34:WU01:FS00:0xa7: SIMD: avx_256
06:36:34:WU01:FS00:0xa7:********************************************************************************
06:36:34:WU01:FS00:0xa7:Project: 13851 (Run 0, Clone 15411, Gen 18)
16:55:44:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:13851 run:0 clone:15411 gen:18 core:0xa7 unit:0x0000001f287234c95e730195d16e171b
16:55:44:WU01:FS00:Uploading 2.59MiB to 40.114.52.201
16:55:44:WU01:FS00:Connecting to 40.114.52.201:8080
16:55:48:WU01:FS00:Upload complete
16:55:48:WU01:FS00:Server responded PLEASE_WAIT (464)
16:55:48:WARNING:WU01:FS00:Failed to send results, will try again later
18:11:45:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:13851 run:0 clone:15411 gen:18 core:0xa7 unit:0x0000001f287234c95e730195d16e171b
18:11:45:WU01:FS00:Uploading 2.59MiB to 40.114.52.201
18:11:45:WU01:FS00:Connecting to 40.114.52.201:8080
18:11:49:WU01:FS00:Upload complete
18:11:49:WU01:FS00:Server responded PLEASE_WAIT (464)
18:11:49:WARNING:WU01:FS00:Failed to send results, will try again later
Re: Failed to send error
i should add, that it has tried 13 times already.
Re: Failed to send error
If it helps, the FAHControl screen says assigned 4/11, timeout 4/12, expiration 4/18 ... so the expiry date has not passed. Not sure what this timeout date means though.
-
- Posts: 1996
- Joined: Sun Mar 22, 2020 5:52 pm
- Hardware configuration: 1: 2x Xeon [email protected], 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon [email protected], 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: [email protected], 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21 - Location: UK
Re: Failed to send error
The timeout is the point at which the WU will be reissued - that doesn't mean your WU is redundant as it may still get received first but points will be base point … Until the expiry the WU you have folded should still be a valid upload - after that your client will (I believe) dump it.
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)
Re: Failed to send error
21 retries, and still going on
-
- Site Moderator
- Posts: 6986
- 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:
Re: Failed to send error
That server (40.114.52.201) has recently been restarted so hopefully, your WU can be uploaded successfully... it has 16 GBs of free space so it isn't much but since it is only accepting completed WUs, will hopefully be enough.
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
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
Re: Failed to send error
Thank you, the WU got uploaded now.