Is 18.218.241.186 a zombie WU server? [No - Assign2]
Moderators: Site Moderators, FAHC Science Team
Is 18.218.241.186 a zombie WU server? [No - Assign2]
I find that when I am referred to 18.218.241.186 I never get work units, and when I look at the server stats page this address is not even there. What is funny is that it takes connections but then never has work units. My client will keep retrying this server for WUs instead of trying other servers. Is it possible to change the algorithm to not keep retrying zombie WU servers?
I look here and I do not ssee the address.
https://apps.foldingathome.org/serverstats
This is a small b sample of my log if I grep the IP address
06:35:55:WU00:FS02:Connecting to 18.218.241.186:80
06:35:56:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:40:10:WU00:FS02:Connecting to 18.218.241.186:80
06:40:10:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:47:01:WU00:FS02:Connecting to 18.218.241.186:80
06:47:01:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:16:03:WU00:FS02:Connecting to 18.218.241.186:80
07:16:04:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:45:06:WU00:FS02:Connecting to 18.218.241.186:80
07:45:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:32:04:WU00:FS02:Connecting to 18.218.241.186:80
08:32:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
09:48:05:WU00:FS02:Connecting to 18.218.241.186:80
09:48:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:51:05:WU00:FS02:Connecting to 18.218.241.186:80
11:51:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
I look here and I do not ssee the address.
https://apps.foldingathome.org/serverstats
This is a small b sample of my log if I grep the IP address
06:35:55:WU00:FS02:Connecting to 18.218.241.186:80
06:35:56:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:40:10:WU00:FS02:Connecting to 18.218.241.186:80
06:40:10:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:47:01:WU00:FS02:Connecting to 18.218.241.186:80
06:47:01:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:16:03:WU00:FS02:Connecting to 18.218.241.186:80
07:16:04:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:45:06:WU00:FS02:Connecting to 18.218.241.186:80
07:45:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:32:04:WU00:FS02:Connecting to 18.218.241.186:80
08:32:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
09:48:05:WU00:FS02:Connecting to 18.218.241.186:80
09:48:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:51:05:WU00:FS02:Connecting to 18.218.241.186:80
11:51:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
-
- 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: Is 18.218.241.186 a zombie WU server?
There are a number of newer servers that may not be properly listed yet.
This may just be server load meaning you are not getting WUs … but if you post a log (the top 200 or so lines and some of the latest bit someone may be able to check there aren't any issues with your setup … viewtopic.php?f=24&t=26036
This may just be server load meaning you are not getting WUs … but if you post a log (the top 200 or so lines and some of the latest bit someone may be able to check there aren't any issues with your setup … viewtopic.php?f=24&t=26036
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)
-
- 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: Is 18.218.241.186 a zombie WU server?
No, as answered elsewhere, this is the actual IP address for assign2. Due to a glitch in the Server Status page, it is showing the private IP address instead of the actual one.
If you look closer at your log, this address is checked after the one for assign1 gives you the same message. This post still applies - viewtopic.php?f=16&t=33193. You may get a WU after a wait. Or it could depend on which type of WU is being requested for your hardware.
If you look closer at your log, this address is checked after the one for assign1 gives you the same message. This post still applies - viewtopic.php?f=16&t=33193. You may get a WU after a wait. Or it could depend on which type of WU is being requested for your hardware.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Is 18.218.241.186 a zombie WU server?
Thank you for your quick reply. My day job is troubleshooting network load balancers. That may color my thinking and I apologize if I am missing something because I am looking at the logs with that perspective.
What I find baffling is that as this 19.218.241.186 always fails, but as an example 40.114.52.201 almost always succeeds with just a few errors. I'm assuming that if everyone just went to 40.114.52.201 you would be out of the frying pan and into the fire but this still seems like I'm spending a lot of waiting to figure out that 19.218.241.186 (which is in AWS) does not have any work units. There is an exponential backoff so if I keep trying 19.218.241.186 a bunch of times my retry interval stretches out be hours between retries. In this from 11:51:05 we then wait till 15:10:06. If I pause and restart I can restart the clock
Mod Edit: Added Code Tags - PantherX
What I find baffling is that as this 19.218.241.186 always fails, but as an example 40.114.52.201 almost always succeeds with just a few errors. I'm assuming that if everyone just went to 40.114.52.201 you would be out of the frying pan and into the fire but this still seems like I'm spending a lot of waiting to figure out that 19.218.241.186 (which is in AWS) does not have any work units. There is an exponential backoff so if I keep trying 19.218.241.186 a bunch of times my retry interval stretches out be hours between retries. In this from 11:51:05 we then wait till 15:10:06. If I pause and restart I can restart the clock
Code: Select all
06:35:55:WU00:FS02:Connecting to 65.254.110.245:8080
06:35:55:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:35:55:WU00:FS02:Connecting to 18.218.241.186:80
06:35:56:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:35:56:ERROR:WU00:FS02:Exception: Could not get an assignment
06:40:09:WU00:FS02:Connecting to 65.254.110.245:8080
06:40:10:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:40:10:WU00:FS02:Connecting to 18.218.241.186:80
06:40:10:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:40:10:ERROR:WU00:FS02:Exception: Could not get an assignment
06:47:01:WU00:FS02:Connecting to 65.254.110.245:8080
06:47:01:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:47:01:WU00:FS02:Connecting to 18.218.241.186:80
06:47:01:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:47:01:ERROR:WU00:FS02:Exception: Could not get an assignment
06:58:06:WU00:FS02:Connecting to 65.254.110.245:8080
06:58:06:WU00:FS02:Assigned to work server 40.114.52.201
06:58:06:WU00:FS02:Requesting new work unit for slot 02: READY gpu:1:TU104 [GeForce RTX 2070 Super] 8218 from 40.114.52.201
06:58:06:WU00:FS02:Connecting to 40.114.52.201:8080
06:58:27:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 80
06:58:27:WU00:FS02:Connecting to 40.114.52.201:80
06:58:49:ERROR:WU00:FS02:Exception: Failed to connect to 40.114.52.201: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:16:03:WU00:FS02:Connecting to 65.254.110.245:8080
07:16:03:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
07:16:03:WU00:FS02:Connecting to 18.218.241.186:80
07:16:04:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:16:04:ERROR:WU00:FS02:Exception: Could not get an assignment
07:45:05:WU00:FS02:Connecting to 65.254.110.245:8080
07:45:06:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
07:45:06:WU00:FS02:Connecting to 18.218.241.186:80
07:45:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:45:06:ERROR:WU00:FS02:Exception: Could not get an assignment
08:32:04:WU00:FS02:Connecting to 65.254.110.245:8080
08:32:04:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:32:04:WU00:FS02:Connecting to 18.218.241.186:80
08:32:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:32:05:ERROR:WU00:FS02:Exception: Could not get an assignment
******************************* Date: 2020-04-06 *******************************
09:48:05:WU00:FS02:Connecting to 65.254.110.245:8080
09:48:05:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
09:48:05:WU00:FS02:Connecting to 18.218.241.186:80
09:48:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
09:48:06:ERROR:WU00:FS02:Exception: Could not get an assignment
11:51:05:WU00:FS02:Connecting to 65.254.110.245:8080
11:51:05:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
11:51:05:WU00:FS02:Connecting to 18.218.241.186:80
11:51:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
11:51:05:ERROR:WU00:FS02:Exception: Could not get an assignment
15:10:05:WU00:FS02:Connecting to 65.254.110.245:8080
15:10:06:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
15:10:06:WU00:FS02:Connecting to 18.218.241.186:80
15:10:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
15:10:06:ERROR:WU00:FS02:Exception: Could not get an assignment
Re: Is 18.218.241.186 a zombie WU server? [No - Assign2]
Code: Select all
00:35:46: GPU 0: Bus:2 Slot:0 Func:0 NVIDIA:7 GP106 [GeForce GTX 1060 6GB] 4372
00:35:46: GPU 1: Bus:1 Slot:0 Func:0 NVIDIA:8 TU104 [GeForce RTX 2070 Super]
00:35:46: 8218
00:35:46: CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:7.5 Driver:10.2
00:35:46: CUDA Device 1: Platform:0 Device:1 Bus:2 Slot:0 Compute:6.1 Driver:10.2
00:35:46:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:442.19
00:35:46:OpenCL Device 1: Platform:0 Device:1 Bus:2 Slot:0 Compute:1.2 Driver:442.19
00:35:46: Win32 Service: false
00:35:46:***********************************************************************
00:35:46:<config>
00:35:46: <!-- Folding Slot Configuration -->
00:35:46: <smp v='false'/>
00:35:46:
00:35:46: <!-- Network -->
00:35:46: <proxy v=':8080'/>
00:35:46:
00:35:46: <!-- Slot Control -->
00:35:46: <power v='full'/>
00:35:46:
00:35:46: <!-- User Information -->
00:35:46: <passkey v='********************************'/>
00:35:46: <user v='markllo'/>
00:35:46:
00:35:46: <!-- Folding Slots -->
00:35:46: <slot id='0' type='CPU'/>
00:35:46: <slot id='1' type='GPU'/>
00:35:46: <slot id='2' type='GPU'/>
00:35:46:</config>
00:35:46:Trying to access database...
00:35:46:Successfully acquired database lock
00:35:46:Enabled folding slot 00: READY cpu:1
00:35:46:Enabled folding slot 01: READY gpu:0:GP106 [GeForce GTX 1060 6GB] 4372
00:35:46:Enabled folding slot 02: READY gpu:1:TU104 [GeForce RTX 2070 Super] 8218
00:35:46:WU03:FS00:Starting
00:35:46:WU03:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\Mark\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 03 -suffix 01 -version 705 -lifeline 1844 -checkpoint 15 -np 1
00:35:46:WU03:FS00:Started FahCore on PID 14952
00:35:46:WU03:FS00:Core PID:13472
00:35:46:WU03:FS00:FahCore 0xa7 started
00:35:46:WU00:FS01:Starting
00:35:46:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\Mark\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 705 -lifeline 1844 -checkpoint 15 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 1 -cuda-device 1 -gpu 1
00:35:46:WU00:FS01:Started FahCore on PID 1504
00:35:46:WU00:FS01:Core PID:13508
00:35:46:WU00:FS01:FahCore 0x22 started
00:35:46:WU03:FS00:0xa7:*********************** Log Started 2020-03-31T00:35:46Z ***********************
00:35:46:WU03:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
00:35:46:WU03:FS00:0xa7: Type: 0xa7
00:35:46:WU03:FS00:0xa7: Core: Gromacs
00:35:46:WU03:FS00:0xa7: Args: -dir 03 -suffix 01 -version 705 -lifeline 14952 -checkpoint 15 -np
00:35:46:WU03:FS00:0xa7: 1
00:35:46:WU03:FS00:0xa7:************************************ CBang *************************************
00:35:46:WU03:FS00:0xa7: Date: Oct 26 2019
00:35:46:WU03:FS00:0xa7: Time: 01:38:25
00:35:46:WU03:FS00:0xa7: Revision: c46a1a011a24143739ac7218c5a435f66777f62f
00:35:46:WU03:FS00:0xa7: Branch: master
00:35:46:WU03:FS00:0xa7: Compiler: Visual C++ 2008
00:35:46:WU03:FS00:0xa7: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
00:35:46:WU03:FS00:0xa7: Platform: win32 10
00:35:46:WU03:FS00:0xa7: Bits: 64
00:35:46:WU03:FS00:0xa7: Mode: Release
00:35:46:WU03:FS00:0xa7:************************************ System ************************************
00:35:46:WU03:FS00:0xa7: CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
00:35:46:WU03:FS00:0xa7: CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
00:35:46:WU03:FS00:0xa7: CPUs: 8
00:35:46:WU03:FS00:0xa7: Memory: 31.95GiB
00:35:46:WU03:FS00:0xa7:Free Memory: 28.62GiB
00:35:46:WU03:FS00:0xa7: Threads: WINDOWS_THREADS
00:35:46:WU03:FS00:0xa7: OS Version: 6.2
00:35:46:WU03:FS00:0xa7:Has Battery: false
00:35:46:WU03:FS00:0xa7: On Battery: false
00:35:46:WU03:FS00:0xa7: UTC Offset: -7
00:35:46:WU03:FS00:0xa7: PID: 13472
00:35:46:WU03:FS00:0xa7: CWD: C:\Users\Mark\AppData\Roaming\FAHClient\work
00:35:46:WU03:FS00:0xa7:******************************** Build - libFAH ********************************
00:35:46:WU03:FS00:0xa7: Version: 0.0.18
00:35:46:WU03:FS00:0xa7: Author: Joseph Coffland <[email protected]>
00:35:46:WU03:FS00:0xa7: Copyright: 2019 foldingathome.org
00:35:46:WU03:FS00:0xa7: Homepage: https://foldingathome.org/
00:35:46:WU03:FS00:0xa7: Date: Oct 26 2019
00:35:46:WU03:FS00:0xa7: Time: 01:52:30
00:35:46:WU03:FS00:0xa7: Revision: c1e3513b1bc0c16013668f2173ee969e5995b38e
00:35:46:WU03:FS00:0xa7: Branch: master
00:35:46:WU03:FS00:0xa7: Compiler: Visual C++ 2008
00:35:46:WU03:FS00:0xa7: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
00:35:46:WU03:FS00:0xa7: Platform: win32 10
00:35:46:WU03:FS00:0xa7: Bits: 64
00:35:46:WU03:FS00:0xa7: Mode: Release
00:35:46:WU03:FS00:0xa7:************************************ Build *************************************
00:35:46:WU03:FS00:0xa7: SIMD: avx_256
00:35:46:WU03:FS00:0xa7:********************************************************************************
00:35:46:WU03:FS00:0xa7:Project: 13850 (Run 0, Clone 3758, Gen 9)
00:35:46:WU03:FS00:0xa7:Unit: 0x00000011287234c95e7258f943989c22
00:35:46:WU03:FS00:0xa7:Digital signatures verified
00:35:46:WU03:FS00:0xa7:Calling: mdrun -s frame9.tpr -o frame9.trr -x frame9.xtc -e frame9.edr -cpi state.cpt -cpt 15 -nt 1
00:35:46:WU03:FS00:0xa7:Steps: first=4500000 total=500000
00:35:47:WU00:FS01:0x22:*********************** Log Started 2020-03-31T00:35:46Z ***********************
00:35:47:WU00:FS01:0x22:*************************** Core22 Folding@home Core ***************************
00:35:47:WU00:FS01:0x22: Type: 0x22
00:35:47:WU00:FS01:0x22: Core: Core22
00:35:47:WU00:FS01:0x22: Website: https://foldingathome.org/
00:35:47:WU00:FS01:0x22: Copyright: (c) 2009-2018 foldingathome.org
00:35:47:WU00:FS01:0x22: Author: John Chodera <[email protected]> and Rafal Wiewiora
00:35:47:WU00:FS01:0x22: <[email protected]>
00:35:47:WU00:FS01:0x22: Args: -dir 00 -suffix 01 -version 705 -lifeline 1504 -checkpoint 15
00:35:47:WU00:FS01:0x22: -gpu-vendor nvidia -opencl-platform 0 -opencl-device 1 -cuda-device
00:35:47:WU00:FS01:0x22: 1 -gpu 1
00:35:47:WU00:FS01:0x22: Config: <none>
00:35:47:WU00:FS01:0x22:************************************ Build *************************************
00:35:47:WU00:FS01:0x22: Version: 0.0.2
00:35:47:WU00:FS01:0x22: Date: Dec 6 2019
00:35:47:WU00:FS01:0x22: Time: 21:30:31
00:35:47:WU00:FS01:0x22: Repository: Git
00:35:47:WU00:FS01:0x22: Revision: abeb39247cc72df5af0f63723edafadb23d5dfbe
00:35:47:WU00:FS01:0x22: Branch: HEAD
00:35:47:WU00:FS01:0x22: Compiler: Visual C++ 2008
00:35:47:WU00:FS01:0x22: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
00:35:47:WU00:FS01:0x22: Platform: win32 10
00:35:47:WU00:FS01:0x22: Bits: 64
00:35:47:WU00:FS01:0x22: Mode: Release
00:35:47:WU00:FS01:0x22:************************************ System ************************************
00:35:47:WU00:FS01:0x22: CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
00:35:47:WU00:FS01:0x22: CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
00:35:47:WU00:FS01:0x22: CPUs: 8
00:35:47:WU00:FS01:0x22: Memory: 31.95GiB
00:35:47:WU00:FS01:0x22:Free Memory: 28.61GiB
00:35:47:WU00:FS01:0x22: Threads: WINDOWS_THREADS
00:35:47:WU00:FS01:0x22: OS Version: 6.2
00:35:47:WU00:FS01:0x22:Has Battery: false
00:35:47:WU00:FS01:0x22: On Battery: false
00:35:47:WU00:FS01:0x22: UTC Offset: -7
00:35:47:WU00:FS01:0x22: PID: 13508
00:35:47:WU00:FS01:0x22: CWD: C:\Users\Mark\AppData\Roaming\FAHClient\work
00:35:47:WU00:FS01:0x22: OS: Windows 10 Pro
00:35:47:WU00:FS01:0x22: OS Arch: AMD64
00:35:47:WU00:FS01:0x22:********************************************************************************
00:35:47:WU00:FS01:0x22:Project: 11777 (Run 0, Clone 15596, Gen 5)
00:35:47:WU00:FS01:0x22:Unit: 0x0000000c287234c95e774aa7c1de597a
00:35:47:WU00:FS01:0x22:Digital signatures verified
00:35:47:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
00:35:47:WU00:FS01:0x22:Version 0.0.2
00:35:47:WU00:FS01:0x22: Found a checkpoint file
00:35:47:WU03:FS00:0xa7:Completed 451321 out of 500000 steps (90%)
00:35:52:WU01:FS02:Connecting to 65.254.110.245:8080bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
.....
06:32:02:WU03:FS02:FahCore returned: FINISHED_UNIT (100 = 0x64)
06:32:02:WU03:FS02:Sending unit results: id:03 state:SEND error:NO_ERROR project:11781 run:0 clone:8988 gen:28 core:0x22 unit:0x0000002a0d5a98395e7588db631ccb11
06:32:02:WU03:FS02:Uploading 55.24MiB to 13.90.152.57
06:32:02:WU03:FS02:Connecting to 13.90.152.57:8080
06:32:08:WU03:FS02:Upload 7.13%
06:32:14:WU03:FS02:Upload 15.27%
06:32:20:WU03:FS02:Upload 23.42%
06:32:26:WU03:FS02:Upload 31.45%
06:32:32:WU03:FS02:Upload 37.34%
06:32:38:WU03:FS02:Upload 43.90%
06:32:44:WU03:FS02:Upload 51.82%
06:32:50:WU03:FS02:Upload 59.29%
06:32:56:WU03:FS02:Upload 67.43%
06:33:02:WU03:FS02:Upload 75.58%
06:33:08:WU03:FS02:Upload 83.61%
06:33:14:WU03:FS02:Upload 91.42%
06:33:18:WU00:FS02:Connecting to 65.254.110.245:8080
06:33:18:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:33:18:WU00:FS02:Connecting to 18.218.241.186:80
06:33:18:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:33:18:ERROR:WU00:FS02:Exception: Could not get an assignment
06:33:20:WU03:FS02:Upload 94.70%
06:33:26:WU03:FS02:Upload 97.53%
06:33:28:WU03:FS02:Upload complete
06:33:28:WU03:FS02:Server responded WORK_ACK (400)
06:33:28:WU03:FS02:Final credit estimate, 137029.00 points
06:33:28:WU03:FS02:Cleaning up
06:35:55:WU00:FS02:Connecting to 65.254.110.245:8080
06:35:55:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:35:55:WU00:FS02:Connecting to 18.218.241.186:80
06:35:56:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:35:56:ERROR:WU00:FS02:Exception: Could not get an assignment
06:40:09:WU00:FS02:Connecting to 65.254.110.245:8080
06:40:10:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:40:10:WU00:FS02:Connecting to 18.218.241.186:80
06:40:10:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:40:10:ERROR:WU00:FS02:Exception: Could not get an assignment
06:47:01:WU00:FS02:Connecting to 65.254.110.245:8080
06:47:01:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
06:47:01:WU00:FS02:Connecting to 18.218.241.186:80
06:47:01:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
06:47:01:ERROR:WU00:FS02:Exception: Could not get an assignment
06:58:06:WU00:FS02:Connecting to 65.254.110.245:8080
06:58:06:WU00:FS02:Assigned to work server 40.114.52.201
06:58:06:WU00:FS02:Requesting new work unit for slot 02: READY gpu:1:TU104 [GeForce RTX 2070 Super] 8218 from 40.114.52.201
06:58:06:WU00:FS02:Connecting to 40.114.52.201:8080
06:58:27:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 80
06:58:27:WU00:FS02:Connecting to 40.114.52.201:80
06:58:49:ERROR:WU00:FS02:Exception: Failed to connect to 40.114.52.201: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:16:03:WU00:FS02:Connecting to 65.254.110.245:8080
07:16:03:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
07:16:03:WU00:FS02:Connecting to 18.218.241.186:80
07:16:04:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:16:04:ERROR:WU00:FS02:Exception: Could not get an assignment
07:45:05:WU00:FS02:Connecting to 65.254.110.245:8080
07:45:06:WARNING:WU00:FS02:Failed to get assignment from '65.254.110A.245:8080': No WUs available for this configuration
07:45:06:WU00:FS02:Connecting to 18.218.241.186:80
07:45:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:45:06:ERROR:WU00:FS02:Exception: Could not get an assignment
08:32:04:WU00:FS02:Connecting to 65.254.110.245:8080
08:32:04:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:32:04:WU00:FS02:Connecting to 18.218.241.186:80
08:32:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:32:05:ERROR:WU00:FS02:Exception: Could not get an assignment
******************************* Date: 2020-04-06 *******************************
09:48:05:WU00:FS02:Connecting to 65.254.110.245:8080
09:48:05:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
09:48:05:WU00:FS02:Connecting to 18.218.241.186:80
09:48:06:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
09:48:06:ERROR:WU00:FS02:Exception: Could not get an assignment
11:51:05:WU00:FS02:Connecting to 65.254.110.245:8080
11:51:05:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
11:51:05:WU00:FS02:Connecting to 18.218.241.186:80
11:51:05:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
Re: Is 18.218.241.186 a zombie WU server? [No - Assign2]
So I think you saying that 18.218.241.186 is a private address for 65.254.110.245 or 172.31.11.240. The other servers have a status of Assign but I'm guessing that there are two meanings here. If I have the sequence right the top level assign the servers that send work units but there are no work units available. Eventually the client backs off to the point that it does not recheck for hours. If this is hard coded in the client this will be difficult to change on the fly. Can we consider a shorter maximum timeout in future clients? I understand that it is important to have clients back off to keep servers from being overwhelmed.
Re: Is 18.218.241.186 a zombie WU server? [No - Assign2]
172.31.11.240 is the private address for 18.218.241.186 (172.31.11.240 is an RFC1918 address in the 172.16.0.0/12 block) -- but 18.218.241.186 is indeed the correct public IP for the assign2 server.
Your client connects first to an Assignment Server (AS) -- the AS assigns you to a Work Server (WS) -- then your client connects to the work server and you download a work unit. Due to the huge amount of people volunteering for F@H at the moment, they have been outstripped of WU's and server capacity. It has gotten a lot better recently as most of my machines have not been idle -- just be patient -- the errors you are seeing are not indicative of any problems on your side. You can pause/resume the client if you want to reset the delay, but please only after the delay has grown fairly large.
Your client connects first to an Assignment Server (AS) -- the AS assigns you to a Work Server (WS) -- then your client connects to the work server and you download a work unit. Due to the huge amount of people volunteering for F@H at the moment, they have been outstripped of WU's and server capacity. It has gotten a lot better recently as most of my machines have not been idle -- just be patient -- the errors you are seeing are not indicative of any problems on your side. You can pause/resume the client if you want to reset the delay, but please only after the delay has grown fairly large.
-
- 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: Is 18.218.241.186 a zombie WU server? [No - Assign2]
No, that is the public IP address for the assign2 server, 172.31.11.240 is in the reserved private IP address range of this block - 172.16.0.0/12. You can do a DNS lookup for assign2.foldingathome.org, the result points to the actual IP on an AWS host.
As for how this works, your folding client connects to one of the AS's and based on the WU request is given a connection to one of the WS's. No WUs come directly from an AS. Each WS updates the AS's with WU and connection availability periodically. Which WS your client will get sent to is based on what most matches the WU request among the available ones.
If the client can not get a connection to the first AS, it tries the second. If either assigns the client to a WS, it then connects directly to the WS, and if a WU is still available, starts a download.
Currently all of the servers are under what could be considered a "friendly DDOS". In the 3 weeks since posts by a number of large social media outlets started mentioning F@h and its working on COVID-19, the number of systems connecting has grown by 30-40 times. They have managed to expand the capability of the WS's to send out work by about 12 times. More servers have been provided to the project, but it takes time to setup and configure each, and the researchers and staff of the F@h groups are relatively small.
The increasing interval is hard coded into the client, it was originally intended to deal with outages of servers from such things as power failures, and the like. So its coding is not optimal for this situation where the servers are up, but have limits on how many connections they can handle.
As for how this works, your folding client connects to one of the AS's and based on the WU request is given a connection to one of the WS's. No WUs come directly from an AS. Each WS updates the AS's with WU and connection availability periodically. Which WS your client will get sent to is based on what most matches the WU request among the available ones.
If the client can not get a connection to the first AS, it tries the second. If either assigns the client to a WS, it then connects directly to the WS, and if a WU is still available, starts a download.
Currently all of the servers are under what could be considered a "friendly DDOS". In the 3 weeks since posts by a number of large social media outlets started mentioning F@h and its working on COVID-19, the number of systems connecting has grown by 30-40 times. They have managed to expand the capability of the WS's to send out work by about 12 times. More servers have been provided to the project, but it takes time to setup and configure each, and the researchers and staff of the F@h groups are relatively small.
The increasing interval is hard coded into the client, it was originally intended to deal with outages of servers from such things as power failures, and the like. So its coding is not optimal for this situation where the servers are up, but have limits on how many connections they can handle.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Is 18.218.241.186 a zombie WU server? [No - Assign2]
Thank you for your fast reply. I paused and restarted my client and I'm processing a new work unit.
-
- Posts: 34
- Joined: Sat Sep 29, 2012 2:40 am
- Hardware configuration: i5-3570k / Gigabyte Z77X-D3H / G.Skill DDR3 2x4GB Sniper / Galax GTX1660 Super 6GB 192 bits / CoolerMaster Hyper 212 + / Corsair HX750W modular / Seagate 500GB Sata 3 + Seagate 160GB Sata 2 + Samsung 1TB Sata 2/ Flatron W2253V / Windows 7 Ultimate 64bits / Corsair Obsidian 650D
- Location: Porto Alegre - RS - Brazil
Re: Is 18.218.241.186 a zombie WU server? [No - Assign2]
Good morning.
Hitchhiking on the colleague's topic, is it possible to trust the server statistics page? If so, why am I waiting 8 hours (and counting) for a WU from a server that, which according to the server stats page, has thousands available?
Thanks in advance.
Hitchhiking on the colleague's topic, is it possible to trust the server statistics page? If so, why am I waiting 8 hours (and counting) for a WU from a server that, which according to the server stats page, has thousands available?
Code: Select all
22:41:08:WU00:FS01:0x22:*********************** Log Started 2020-04-06T22:41:08Z ***********************
22:41:08:WU00:FS01:0x22:*************************** Core22 Folding@home Core ***************************
22:41:08:WU00:FS01:0x22: Type: 0x22
22:41:08:WU00:FS01:0x22: Core: Core22
22:41:08:WU00:FS01:0x22: Website: https://foldingathome.org/
22:41:08:WU00:FS01:0x22: Copyright: (c) 2009-2018 foldingathome.org
22:41:08:WU00:FS01:0x22: Author: John Chodera <[email protected]> and Rafal Wiewiora
22:41:08:WU00:FS01:0x22: <[email protected]>
22:41:08:WU00:FS01:0x22: Args: -dir 00 -suffix 01 -version 704 -lifeline 7508 -checkpoint 15 -gpu
22:41:08:WU00:FS01:0x22: 0 -gpu-vendor nvidia
22:41:08:WU00:FS01:0x22: Config: <none>
22:41:08:WU00:FS01:0x22:************************************ Build *************************************
22:41:08:WU00:FS01:0x22: Version: 0.0.2
22:41:08:WU00:FS01:0x22: Date: Dec 6 2019
22:41:08:WU00:FS01:0x22: Time: 21:30:31
22:41:08:WU00:FS01:0x22: Repository: Git
22:41:08:WU00:FS01:0x22: Revision: abeb39247cc72df5af0f63723edafadb23d5dfbe
22:41:08:WU00:FS01:0x22: Branch: HEAD
22:41:08:WU00:FS01:0x22: Compiler: Visual C++ 2008
22:41:08:WU00:FS01:0x22: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
22:41:08:WU00:FS01:0x22: Platform: win32 10
22:41:08:WU00:FS01:0x22: Bits: 64
22:41:08:WU00:FS01:0x22: Mode: Release
22:41:08:WU00:FS01:0x22:************************************ System ************************************
22:41:08:WU00:FS01:0x22: CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
22:41:08:WU00:FS01:0x22: CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
22:41:08:WU00:FS01:0x22: CPUs: 4
22:41:08:WU00:FS01:0x22: Memory: 7.96GiB
22:41:08:WU00:FS01:0x22:Free Memory: 6.23GiB
22:41:08:WU00:FS01:0x22: Threads: WINDOWS_THREADS
22:41:08:WU00:FS01:0x22: OS Version: 6.1
22:41:08:WU00:FS01:0x22:Has Battery: false
22:41:08:WU00:FS01:0x22: On Battery: false
22:41:08:WU00:FS01:0x22: UTC Offset: -3
22:41:08:WU00:FS01:0x22: PID: 2460
22:41:08:WU00:FS01:0x22: CWD: C:\Users\markus\AppData\Roaming\FAHClient\work
22:41:08:WU00:FS01:0x22: OS: Windows 7 Ultimate Service Pack 1
22:41:08:WU00:FS01:0x22: OS Arch: AMD64
22:41:08:WU00:FS01:0x22:********************************************************************************
22:41:08:WU00:FS01:0x22:Project: 13876 (Run 0, Clone 647, Gen 16)
22:41:08:WU00:FS01:0x22:Unit: 0x000000140d5262775e7cf10be573cfb1
22:41:08:WU00:FS01:0x22:Reading tar file core.xml
22:41:08:WU00:FS01:0x22:Reading tar file integrator.xml
22:41:08:WU00:FS01:0x22:Reading tar file state.xml
22:41:08:WU00:FS01:0x22:Reading tar file system.xml
22:41:09:WU00:FS01:0x22:Digital signatures verified
22:41:09:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
22:41:09:WU00:FS01:0x22:Version 0.0.2
22:43:00:WU00:FS01:0x22:Completed 0 out of 1000000 steps (0%)
22:43:00:WU00:FS01:0x22:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
22:46:42:WU00:FS01:0x22:Completed 10000 out of 1000000 steps (1%)
22:49:42:WU00:FS01:0x22:Completed 20000 out of 1000000 steps (2%)
22:52:43:WU00:FS01:0x22:Completed 30000 out of 1000000 steps (3%)
22:55:44:WU00:FS01:0x22:Completed 40000 out of 1000000 steps (4%)
22:58:45:WU00:FS01:0x22:Completed 50000 out of 1000000 steps (5%)
23:02:32:WU00:FS01:0x22:Completed 60000 out of 1000000 steps (6%)
23:05:33:WU00:FS01:0x22:Completed 70000 out of 1000000 steps (7%)
23:08:33:WU00:FS01:0x22:Completed 80000 out of 1000000 steps (8%)
23:11:36:WU00:FS01:0x22:Completed 90000 out of 1000000 steps (9%)
23:14:40:WU00:FS01:0x22:Completed 100000 out of 1000000 steps (10%)
23:18:37:WU00:FS01:0x22:Completed 110000 out of 1000000 steps (11%)
23:21:40:WU00:FS01:0x22:Completed 120000 out of 1000000 steps (12%)
23:24:42:WU00:FS01:0x22:Completed 130000 out of 1000000 steps (13%)
23:27:45:WU00:FS01:0x22:Completed 140000 out of 1000000 steps (14%)
23:30:48:WU00:FS01:0x22:Completed 150000 out of 1000000 steps (15%)
23:34:36:WU00:FS01:0x22:Completed 160000 out of 1000000 steps (16%)
23:37:38:WU00:FS01:0x22:Completed 170000 out of 1000000 steps (17%)
23:40:39:WU00:FS01:0x22:Completed 180000 out of 1000000 steps (18%)
23:43:41:WU00:FS01:0x22:Completed 190000 out of 1000000 steps (19%)
23:46:44:WU00:FS01:0x22:Completed 200000 out of 1000000 steps (20%)
23:50:34:WU00:FS01:0x22:Completed 210000 out of 1000000 steps (21%)
23:53:38:WU00:FS01:0x22:Completed 220000 out of 1000000 steps (22%)
23:56:42:WU00:FS01:0x22:Completed 230000 out of 1000000 steps (23%)
23:59:44:WU00:FS01:0x22:Completed 240000 out of 1000000 steps (24%)
00:02:46:WU00:FS01:0x22:Completed 250000 out of 1000000 steps (25%)
00:06:34:WU00:FS01:0x22:Completed 260000 out of 1000000 steps (26%)
00:09:35:WU00:FS01:0x22:Completed 270000 out of 1000000 steps (27%)
00:12:37:WU00:FS01:0x22:Completed 280000 out of 1000000 steps (28%)
00:15:38:WU00:FS01:0x22:Completed 290000 out of 1000000 steps (29%)
00:18:40:WU00:FS01:0x22:Completed 300000 out of 1000000 steps (30%)
00:22:32:WU00:FS01:0x22:Completed 310000 out of 1000000 steps (31%)
00:25:35:WU00:FS01:0x22:Completed 320000 out of 1000000 steps (32%)
00:28:38:WU00:FS01:0x22:Completed 330000 out of 1000000 steps (33%)
00:31:41:WU00:FS01:0x22:Completed 340000 out of 1000000 steps (34%)
00:34:43:WU00:FS01:0x22:Completed 350000 out of 1000000 steps (35%)
00:38:32:WU00:FS01:0x22:Completed 360000 out of 1000000 steps (36%)
00:41:36:WU00:FS01:0x22:Completed 370000 out of 1000000 steps (37%)
00:44:41:WU00:FS01:0x22:Completed 380000 out of 1000000 steps (38%)
00:47:43:WU00:FS01:0x22:Completed 390000 out of 1000000 steps (39%)
00:50:46:WU00:FS01:0x22:Completed 400000 out of 1000000 steps (40%)
00:54:35:WU00:FS01:0x22:Completed 410000 out of 1000000 steps (41%)
00:57:40:WU00:FS01:0x22:Completed 420000 out of 1000000 steps (42%)
01:00:48:WU00:FS01:0x22:Completed 430000 out of 1000000 steps (43%)
01:03:57:WU00:FS01:0x22:Completed 440000 out of 1000000 steps (44%)
01:07:05:WU00:FS01:0x22:Completed 450000 out of 1000000 steps (45%)
01:11:08:WU00:FS01:0x22:Completed 460000 out of 1000000 steps (46%)
01:14:15:WU00:FS01:0x22:Completed 470000 out of 1000000 steps (47%)
******************************* Date: 2020-04-07 *******************************
01:17:20:WU00:FS01:0x22:Completed 480000 out of 1000000 steps (48%)
01:20:22:WU00:FS01:0x22:Completed 490000 out of 1000000 steps (49%)
01:23:24:WU00:FS01:0x22:Completed 500000 out of 1000000 steps (50%)
01:27:12:WU00:FS01:0x22:Completed 510000 out of 1000000 steps (51%)
01:30:13:WU00:FS01:0x22:Completed 520000 out of 1000000 steps (52%)
01:33:14:WU00:FS01:0x22:Completed 530000 out of 1000000 steps (53%)
01:36:16:WU00:FS01:0x22:Completed 540000 out of 1000000 steps (54%)
01:39:17:WU00:FS01:0x22:Completed 550000 out of 1000000 steps (55%)
01:43:03:WU00:FS01:0x22:Completed 560000 out of 1000000 steps (56%)
01:46:05:WU00:FS01:0x22:Completed 570000 out of 1000000 steps (57%)
01:49:06:WU00:FS01:0x22:Completed 580000 out of 1000000 steps (58%)
01:52:07:WU00:FS01:0x22:Completed 590000 out of 1000000 steps (59%)
01:55:09:WU00:FS01:0x22:Completed 600000 out of 1000000 steps (60%)
01:58:57:WU00:FS01:0x22:Completed 610000 out of 1000000 steps (61%)
02:02:00:WU00:FS01:0x22:Completed 620000 out of 1000000 steps (62%)
02:03:01:FS01:Finishing
02:05:05:WU00:FS01:0x22:Completed 630000 out of 1000000 steps (63%)
02:08:09:WU00:FS01:0x22:Completed 640000 out of 1000000 steps (64%)
02:11:16:WU00:FS01:0x22:Completed 650000 out of 1000000 steps (65%)
02:15:14:WU00:FS01:0x22:Completed 660000 out of 1000000 steps (66%)
02:18:18:WU00:FS01:0x22:Completed 670000 out of 1000000 steps (67%)
02:21:19:WU00:FS01:0x22:Completed 680000 out of 1000000 steps (68%)
02:24:27:WU00:FS01:0x22:Completed 690000 out of 1000000 steps (69%)
02:27:34:WU00:FS01:0x22:Completed 700000 out of 1000000 steps (70%)
02:31:29:WU00:FS01:0x22:Completed 710000 out of 1000000 steps (71%)
02:34:37:WU00:FS01:0x22:Completed 720000 out of 1000000 steps (72%)
02:37:44:WU00:FS01:0x22:Completed 730000 out of 1000000 steps (73%)
02:40:52:WU00:FS01:0x22:Completed 740000 out of 1000000 steps (74%)
02:43:59:WU00:FS01:0x22:Completed 750000 out of 1000000 steps (75%)
02:47:58:WU00:FS01:0x22:Completed 760000 out of 1000000 steps (76%)
02:51:01:WU00:FS01:0x22:Completed 770000 out of 1000000 steps (77%)
02:54:03:WU00:FS01:0x22:Completed 780000 out of 1000000 steps (78%)
02:57:08:WU00:FS01:0x22:Completed 790000 out of 1000000 steps (79%)
03:00:10:WU00:FS01:0x22:Completed 800000 out of 1000000 steps (80%)
03:03:57:WU00:FS01:0x22:Completed 810000 out of 1000000 steps (81%)
03:06:59:WU00:FS01:0x22:Completed 820000 out of 1000000 steps (82%)
03:10:00:WU00:FS01:0x22:Completed 830000 out of 1000000 steps (83%)
03:13:02:WU00:FS01:0x22:Completed 840000 out of 1000000 steps (84%)
03:16:03:WU00:FS01:0x22:Completed 850000 out of 1000000 steps (85%)
03:19:50:WU00:FS01:0x22:Completed 860000 out of 1000000 steps (86%)
03:22:52:WU00:FS01:0x22:Completed 870000 out of 1000000 steps (87%)
03:25:53:WU00:FS01:0x22:Completed 880000 out of 1000000 steps (88%)
03:28:55:WU00:FS01:0x22:Completed 890000 out of 1000000 steps (89%)
03:31:56:WU00:FS01:0x22:Completed 900000 out of 1000000 steps (90%)
03:35:43:WU00:FS01:0x22:Completed 910000 out of 1000000 steps (91%)
03:38:45:WU00:FS01:0x22:Completed 920000 out of 1000000 steps (92%)
03:41:46:WU00:FS01:0x22:Completed 930000 out of 1000000 steps (93%)
03:44:47:WU00:FS01:0x22:Completed 940000 out of 1000000 steps (94%)
03:47:48:WU00:FS01:0x22:Completed 950000 out of 1000000 steps (95%)
03:51:34:WU00:FS01:0x22:Completed 960000 out of 1000000 steps (96%)
03:54:35:WU00:FS01:0x22:Completed 970000 out of 1000000 steps (97%)
03:57:37:WU00:FS01:0x22:Completed 980000 out of 1000000 steps (98%)
04:00:38:WU00:FS01:0x22:Completed 990000 out of 1000000 steps (99%)
04:00:39:WU01:FS01:Connecting to 65.254.110.245:80
04:00:40:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:00:40:WU01:FS01:Connecting to 18.218.241.186:80
04:00:41:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:00:41:ERROR:WU01:FS01:Exception: Could not get an assignment
04:00:41:WU01:FS01:Connecting to 65.254.110.245:80
04:00:42:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:00:42:WU01:FS01:Connecting to 18.218.241.186:80
04:00:42:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:00:42:ERROR:WU01:FS01:Exception: Could not get an assignment
04:01:41:WU01:FS01:Connecting to 65.254.110.245:80
04:01:42:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:01:42:WU01:FS01:Connecting to 18.218.241.186:80
04:01:42:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:01:42:ERROR:WU01:FS01:Exception: Could not get an assignment
04:03:18:WU01:FS01:Connecting to 65.254.110.245:80
04:03:19:WU01:FS01:Assigned to work server 40.114.52.201
04:03:19:WU01:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:TU116 [GeForce GTX 1660 SUPER] from 40.114.52.201
04:03:19:WU01:FS01:Connecting to 40.114.52.201:8080
04:03:27:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0
04:03:40:WU00:FS01:0x22:Completed 1000000 out of 1000000 steps (100%)
04:04:26:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
04:04:26:WU00:FS01:0x22:Saving result file checkpointState.xml
04:04:27:WU00:FS01:0x22:Saving result file checkpt.crc
04:04:27:WU00:FS01:0x22:Saving result file positions.xtc
04:04:27:WU00:FS01:0x22:Saving result file science.log
04:04:27:WU00:FS01:0x22:Folding@home Core Shutdown: FINISHED_UNIT
04:04:28:WU00:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
04:04:28:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:13876 run:0 clone:647 gen:16 core:0x22 unit:0x000000140d5262775e7cf10be573cfb1
04:04:28:WU00:FS01:Uploading 48.06MiB to 13.82.98.119
04:04:28:WU00:FS01:Connecting to 13.82.98.119:8080
04:04:34:WU00:FS01:Upload 42.91%
04:04:40:WU00:FS01:Upload 44.34%
04:04:46:WU00:FS01:Upload 45.90%
04:04:52:WU00:FS01:Upload 47.46%
04:04:58:WU00:FS01:Upload 48.90%
04:05:04:WU00:FS01:Upload 50.46%
04:05:10:WU00:FS01:Upload 52.02%
04:05:16:WU00:FS01:Upload 53.58%
04:05:22:WU00:FS01:Upload 55.14%
04:05:28:WU00:FS01:Upload 56.57%
04:05:34:WU00:FS01:Upload 58.00%
04:05:40:WU00:FS01:Upload 59.56%
04:05:46:WU00:FS01:Upload 60.99%
04:05:52:WU00:FS01:Upload 62.55%
04:05:56:WU01:FS01:Connecting to 65.254.110.245:80
04:05:56:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:05:56:WU01:FS01:Connecting to 18.218.241.186:80
04:05:57:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:05:57:ERROR:WU01:FS01:Exception: Could not get an assignment
04:05:58:WU00:FS01:Upload 63.85%
04:06:04:WU00:FS01:Upload 65.41%
04:06:10:WU00:FS01:Upload 66.84%
04:06:16:WU00:FS01:Upload 68.40%
04:06:22:WU00:FS01:Upload 69.96%
04:06:28:WU00:FS01:Upload 71.52%
04:06:34:WU00:FS01:Upload 72.95%
04:06:40:WU00:FS01:Upload 74.51%
04:06:46:WU00:FS01:Upload 76.07%
04:06:52:WU00:FS01:Upload 77.63%
04:06:58:WU00:FS01:Upload 79.06%
04:07:04:WU00:FS01:Upload 80.63%
04:07:10:WU00:FS01:Upload 82.19%
04:07:16:WU00:FS01:Upload 83.62%
04:07:22:WU00:FS01:Upload 85.18%
04:07:28:WU00:FS01:Upload 86.74%
04:07:34:WU00:FS01:Upload 88.17%
04:07:41:WU00:FS01:Upload 89.34%
04:07:47:WU00:FS01:Upload 90.25%
04:07:53:WU00:FS01:Upload 91.81%
04:07:59:WU00:FS01:Upload 93.24%
04:08:05:WU00:FS01:Upload 94.80%
04:08:11:WU00:FS01:Upload 96.36%
04:08:17:WU00:FS01:Upload 97.79%
04:08:23:WU00:FS01:Upload 99.35%
04:10:10:WU01:FS01:Connecting to 65.254.110.245:80
04:10:11:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:10:11:WU01:FS01:Connecting to 18.218.241.186:80
04:10:12:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:10:12:ERROR:WU01:FS01:Exception: Could not get an assignment
04:11:10:WU00:FS01:Upload complete
04:11:10:WU00:FS01:Server responded WORK_ACK (400)
04:11:10:WU00:FS01:Final credit estimate, 146574.00 points
04:11:10:WU00:FS01:Cleaning up
04:17:01:WU01:FS01:Connecting to 65.254.110.245:80
04:17:02:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:17:02:WU01:FS01:Connecting to 18.218.241.186:80
04:17:02:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:17:02:ERROR:WU01:FS01:Exception: Could not get an assignment
04:28:07:WU01:FS01:Connecting to 65.254.110.245:80
04:28:07:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:28:07:WU01:FS01:Connecting to 18.218.241.186:80
04:28:08:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:28:08:ERROR:WU01:FS01:Exception: Could not get an assignment
04:46:04:WU01:FS01:Connecting to 65.254.110.245:80
04:46:05:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
04:46:05:WU01:FS01:Connecting to 18.218.241.186:80
04:46:06:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
04:46:06:ERROR:WU01:FS01:Exception: Could not get an assignment
05:15:06:WU01:FS01:Connecting to 65.254.110.245:80
05:15:06:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
05:15:06:WU01:FS01:Connecting to 18.218.241.186:80
05:15:07:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
05:15:07:ERROR:WU01:FS01:Exception: Could not get an assignment
06:02:05:WU01:FS01:Connecting to 65.254.110.245:80
06:02:06:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
06:02:06:WU01:FS01:Connecting to 18.218.241.186:80
06:02:06:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
06:02:06:ERROR:WU01:FS01:Exception: Could not get an assignment
******************************* Date: 2020-04-07 *******************************
07:18:06:WU01:FS01:Connecting to 65.254.110.245:80
07:18:06:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
07:18:06:WU01:FS01:Connecting to 18.218.241.186:80
07:18:07:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
07:18:07:ERROR:WU01:FS01:Exception: Could not get an assignment
09:21:05:WU01:FS01:Connecting to 65.254.110.245:80
09:21:06:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
09:21:06:WU01:FS01:Connecting to 18.218.241.186:80
09:21:07:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
09:21:07:ERROR:WU01:FS01:Exception: Could not get an assignment
11:50:12:FS01:Paused
11:51:07:Removing old file 'configs/config-20200402-201611.xml'
11:51:07:Saving configuration to config.xml
11:51:07:<config>
11:51:07: <!-- Network -->
11:51:07: <proxy v=':8080'/>
11:51:07:
11:51:07: <!-- Slot Control -->
11:51:07: <pause-on-battery v='false'/>
11:51:07: <power v='MEDIUM'/>
11:51:07:
11:51:07: <!-- User Information -->
11:51:07: <passkey v='********************************'/>
11:51:07: <team v='13802'/>
11:51:07: <user v='krilenko'/>
11:51:07:
11:51:07: <!-- Folding Slots -->
11:51:07: <slot id='1' type='GPU'>
11:51:07: <paused v='true'/>
11:51:07: </slot>
11:51:07:</config>
11:52:04:FS01:Unpaused
11:52:04:WU01:FS01:Connecting to 65.254.110.245:80
11:52:05:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
11:52:05:WU01:FS01:Connecting to 18.218.241.186:80
11:52:05:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
11:52:05:ERROR:WU01:FS01:Exception: Could not get an assignment
11:52:08:Removing old file 'configs/config-20200402-213428.xml'
11:52:08:Saving configuration to config.xml
11:52:08:<config>
11:52:08: <!-- Network -->
11:52:08: <proxy v=':8080'/>
11:52:08:
11:52:08: <!-- Slot Control -->
11:52:08: <pause-on-battery v='false'/>
11:52:08: <power v='MEDIUM'/>
11:52:08:
11:52:08: <!-- User Information -->
11:52:08: <passkey v='********************************'/>
11:52:08: <team v='13802'/>
11:52:08: <user v='krilenko'/>
11:52:08:
11:52:08: <!-- Folding Slots -->
11:52:08: <slot id='1' type='GPU'/>
11:52:08:</config>
11:53:41:WU01:FS01:Connecting to 65.254.110.245:80
11:53:41:WU01:FS01:Assigned to work server 13.82.98.119
11:53:41:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:TU116 [GeForce GTX 1660 SUPER] from 13.82.98.119
11:53:41:WU01:FS01:Connecting to 13.82.98.119:8080
11:53:42:ERROR:WU01:FS01:Exception: Server did not assign work unit
11:56:18:WU01:FS01:Connecting to 65.254.110.245:80
11:56:19:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
11:56:19:WU01:FS01:Connecting to 18.218.241.186:80
11:56:19:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
11:56:19:ERROR:WU01:FS01:Exception: Could not get an assignment
12:00:33:WU01:FS01:Connecting to 65.254.110.245:80
12:00:33:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
12:00:33:WU01:FS01:Connecting to 18.218.241.186:80
12:00:34:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
12:00:34:ERROR:WU01:FS01:Exception: Could not get an assignment
12:07:24:WU01:FS01:Connecting to 65.254.110.245:80
12:07:24:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
12:07:24:WU01:FS01:Connecting to 18.218.241.186:80
12:07:25:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
12:07:25:ERROR:WU01:FS01:Exception: Could not get an assignment
12:18:29:WU01:FS01:Connecting to 65.254.110.245:80
12:18:30:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:80': Empty work server assignment
12:18:30:WU01:FS01:Connecting to 18.218.241.186:80
12:18:30:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': Empty work server assignment
12:18:30:ERROR:WU01:FS01:Exception: Could not get an assignment
-
- 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: Is 18.218.241.186 a zombie WU server? [No - Assign2]
The status page does not tell you how many connections each server has available, there is a practical limit. Each WS is not just providing downloads, they are also receiving uploads.
Indirectly you can see the limits, most of the WS entries for Assign Rate are nice whole numbers. They are taking that many connections an hour for clients to download WUs. The rates could be set higher, but then there would be less network capacity for returns. There are already many posts about slow or failed uploads as it is.
Indirectly you can see the limits, most of the WS entries for Assign Rate are nice whole numbers. They are taking that many connections an hour for clients to download WUs. The rates could be set higher, but then there would be less network capacity for returns. There are already many posts about slow or failed uploads as it is.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Is 18.218.241.186 a zombie WU server? [No - Assign2]
While the nice round numbers do tell the story that the server is working hard, when I look at that page, my mind substitutes the work "saturated" for the familiar values that indicate just that. Maybe there are a few servers that could have the saturation level reduced by 5% - 10% to leave more capacity for uploads, but as long as there are functional Collection Servers I guess it really doesn't matter.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.