WU 16420 1478 0 35 - what happened to my one?

peterjammo · Post by **peterjammo** » Sat Apr 25, 2020 10:41 am

Looking at my log, I think it says that I completed and successfully returned this wu on 23rd at 01:41. This was a few hours past Timeout.

It never appeared in the recent cpu report https://apps.foldingathome.org/cpu, and when I look in https://apps.foldingathome.org/wu#proje ... e=0&gen=35 it was reassigned to someone else at 20:49 on 23rd.

Here's my log

Code: Select all

20:21:52:WU00:FS00:0xa7:*********************** Log Started 2020-04-21T20:21:52Z ***********************
20:21:52:WU00:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
20:21:52:WU00:FS00:0xa7:       Type: 0xa7
20:21:52:WU00:FS00:0xa7:       Core: Gromacs
20:21:52:WU00:FS00:0xa7:       Args: -dir 00 -suffix 01 -version 706 -lifeline 29506 -checkpoint 15 -np
20:21:52:WU00:FS00:0xa7:             2
20:21:52:WU00:FS00:0xa7:************************************ CBang *************************************
20:21:52:WU00:FS00:0xa7:       Date: Nov 5 2019
20:21:52:WU00:FS00:0xa7:       Time: 05:57:01
20:21:52:WU00:FS00:0xa7:   Revision: 46c96f1aa8419571d83f3e63f9c99a0d602f6da9
20:21:52:WU00:FS00:0xa7:     Branch: master
20:21:52:WU00:FS00:0xa7:   Compiler: GNU 8.3.0
20:21:52:WU00:FS00:0xa7:    Options: -std=c++11 -O3 -funroll-loops -fno-pie -fPIC
20:21:52:WU00:FS00:0xa7:   Platform: linux2 4.19.0-5-amd64
20:21:52:WU00:FS00:0xa7:       Bits: 64
20:21:52:WU00:FS00:0xa7:       Mode: Release
20:21:52:WU00:FS00:0xa7:************************************ System ************************************
20:21:52:WU00:FS00:0xa7:        CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz
20:21:52:WU00:FS00:0xa7:     CPU ID: GenuineIntel Family 6 Model 15 Stepping 13
20:21:52:WU00:FS00:0xa7:       CPUs: 2
20:21:52:WU00:FS00:0xa7:     Memory: 3.84GiB
20:21:52:WU00:FS00:0xa7:Free Memory: 328.46MiB
20:21:52:WU00:FS00:0xa7:    Threads: POSIX_THREADS
20:21:52:WU00:FS00:0xa7: OS Version: 4.15
20:21:52:WU00:FS00:0xa7:Has Battery: true
20:21:52:WU00:FS00:0xa7: On Battery: false
20:21:52:WU00:FS00:0xa7: UTC Offset: 1
20:21:52:WU00:FS00:0xa7:        PID: 29510
20:21:52:WU00:FS00:0xa7:        CWD: /var/lib/fahclient/work
20:21:52:WU00:FS00:0xa7:******************************** Build - libFAH ********************************
20:21:52:WU00:FS00:0xa7:    Version: 0.0.18
20:21:52:WU00:FS00:0xa7:     Author: Joseph Coffland <[email protected]>
20:21:52:WU00:FS00:0xa7:  Copyright: 2019 foldingathome.org
20:21:52:WU00:FS00:0xa7:   Homepage: https://foldingathome.org/
20:21:52:WU00:FS00:0xa7:       Date: Nov 5 2019
20:21:52:WU00:FS00:0xa7:       Time: 06:13:26
20:21:52:WU00:FS00:0xa7:   Revision: 490c9aa2957b725af319379424d5c5cb36efb656
20:21:52:WU00:FS00:0xa7:     Branch: master
20:21:52:WU00:FS00:0xa7:   Compiler: GNU 8.3.0
20:21:52:WU00:FS00:0xa7:    Options: -std=c++11 -O3 -funroll-loops -fno-pie
20:21:52:WU00:FS00:0xa7:   Platform: linux2 4.19.0-5-amd64
20:21:52:WU00:FS00:0xa7:       Bits: 64
20:21:52:WU00:FS00:0xa7:       Mode: Release
20:21:52:WU00:FS00:0xa7:************************************ Build *************************************
20:21:52:WU00:FS00:0xa7:       SIMD: sse2
20:21:52:WU00:FS00:0xa7:********************************************************************************
20:21:52:WU00:FS00:0xa7:Project: 16420 (Run 1478, Clone 0, Gen 35)
20:21:52:WU00:FS00:0xa7:Unit: 0x0000002ca8f5c67d5e8a605ba5ebe6bf
20:21:52:WU00:FS00:0xa7:Reading tar file core.xml
20:21:52:WU00:FS00:0xa7:Reading tar file frame35.tpr
20:21:52:WU00:FS00:0xa7:Digital signatures verified
20:21:52:WU00:FS00:0xa7:Calling: mdrun -s frame35.tpr -o frame35.trr -x frame35.xtc -cpt 15 -nt 2
20:21:52:WU00:FS00:0xa7:Steps: first=8750000 total=250000
20:21:55:WU00:FS00:0xa7:Completed 1 out of 250000 steps (0%)
20:21:57:WU01:FS00:Upload 69.92%
20:22:00:WU01:FS00:Upload complete
20:22:00:WU01:FS00:Server responded WORK_ACK (400)
20:22:00:WU01:FS00:Final credit estimate, 2014.00 points
20:22:00:WU01:FS00:Cleaning up
20:39:29:WU00:FS00:0xa7:Completed 2500 out of 250000 steps (1%)
20:57:04:WU00:FS00:0xa7:Completed 5000 out of 250000 steps (2%)
21:14:34:WU00:FS00:0xa7:Completed 7500 out of 250000 steps (3%)
21:32:09:WU00:FS00:0xa7:Completed 10000 out of 250000 steps (4%)
21:49:41:WU00:FS00:0xa7:Completed 12500 out of 250000 steps (5%)
22:07:16:WU00:FS00:0xa7:Completed 15000 out of 250000 steps (6%)
22:24:45:WU00:FS00:0xa7:Completed 17500 out of 250000 steps (7%)
22:42:19:WU00:FS00:0xa7:Completed 20000 out of 250000 steps (8%)
******************************* Date: 2020-04-21 *******************************
22:59:50:WU00:FS00:0xa7:Completed 22500 out of 250000 steps (9%)
23:17:19:WU00:FS00:0xa7:Completed 25000 out of 250000 steps (10%)
23:34:59:WU00:FS00:0xa7:Completed 27500 out of 250000 steps (11%)
23:52:32:WU00:FS00:0xa7:Completed 30000 out of 250000 steps (12%)
00:10:00:WU00:FS00:0xa7:Completed 32500 out of 250000 steps (13%)
00:27:29:WU00:FS00:0xa7:Completed 35000 out of 250000 steps (14%)
00:45:00:WU00:FS00:0xa7:Completed 37500 out of 250000 steps (15%)
01:02:30:WU00:FS00:0xa7:Completed 40000 out of 250000 steps (16%)
01:19:58:WU00:FS00:0xa7:Completed 42500 out of 250000 steps (17%)
01:37:36:WU00:FS00:0xa7:Completed 45000 out of 250000 steps (18%)
01:55:12:WU00:FS00:0xa7:Completed 47500 out of 250000 steps (19%)
02:12:43:WU00:FS00:0xa7:Completed 50000 out of 250000 steps (20%)
02:30:12:WU00:FS00:0xa7:Completed 52500 out of 250000 steps (21%)
02:47:40:WU00:FS00:0xa7:Completed 55000 out of 250000 steps (22%)
03:05:11:WU00:FS00:0xa7:Completed 57500 out of 250000 steps (23%)
03:22:48:WU00:FS00:0xa7:Completed 60000 out of 250000 steps (24%)
03:40:15:WU00:FS00:0xa7:Completed 62500 out of 250000 steps (25%)
03:57:45:WU00:FS00:0xa7:Completed 65000 out of 250000 steps (26%)
04:15:17:WU00:FS00:0xa7:Completed 67500 out of 250000 steps (27%)
04:32:46:WU00:FS00:0xa7:Completed 70000 out of 250000 steps (28%)
04:50:17:WU00:FS00:0xa7:Completed 72500 out of 250000 steps (29%)
******************************* Date: 2020-04-22 *******************************
05:07:49:WU00:FS00:0xa7:Completed 75000 out of 250000 steps (30%)
05:25:21:WU00:FS00:0xa7:Completed 77500 out of 250000 steps (31%)
05:42:53:WU00:FS00:0xa7:Completed 80000 out of 250000 steps (32%)
06:00:25:WU00:FS00:0xa7:Completed 82500 out of 250000 steps (33%)
06:17:55:WU00:FS00:0xa7:Completed 85000 out of 250000 steps (34%)
06:35:28:WU00:FS00:0xa7:Completed 87500 out of 250000 steps (35%)
06:53:17:WU00:FS00:0xa7:Completed 90000 out of 250000 steps (36%)
07:10:48:WU00:FS00:0xa7:Completed 92500 out of 250000 steps (37%)
07:28:19:WU00:FS00:0xa7:Completed 95000 out of 250000 steps (38%)
07:45:51:WU00:FS00:0xa7:Completed 97500 out of 250000 steps (39%)
08:03:23:WU00:FS00:0xa7:Completed 100000 out of 250000 steps (40%)
08:20:53:WU00:FS00:0xa7:Completed 102500 out of 250000 steps (41%)
08:38:24:WU00:FS00:0xa7:Completed 105000 out of 250000 steps (42%)
08:55:56:WU00:FS00:0xa7:Completed 107500 out of 250000 steps (43%)
09:13:27:WU00:FS00:0xa7:Completed 110000 out of 250000 steps (44%)
09:30:57:WU00:FS00:0xa7:Completed 112500 out of 250000 steps (45%)
09:48:28:WU00:FS00:0xa7:Completed 115000 out of 250000 steps (46%)
10:05:57:WU00:FS00:0xa7:Completed 117500 out of 250000 steps (47%)
10:23:30:WU00:FS00:0xa7:Completed 120000 out of 250000 steps (48%)
10:41:01:WU00:FS00:0xa7:Completed 122500 out of 250000 steps (49%)
10:58:32:WU00:FS00:0xa7:Completed 125000 out of 250000 steps (50%)
******************************* Date: 2020-04-22 *******************************
11:16:02:WU00:FS00:0xa7:Completed 127500 out of 250000 steps (51%)
11:33:35:WU00:FS00:0xa7:Completed 130000 out of 250000 steps (52%)
11:51:07:WU00:FS00:0xa7:Completed 132500 out of 250000 steps (53%)
12:08:39:WU00:FS00:0xa7:Completed 135000 out of 250000 steps (54%)
12:26:10:WU00:FS00:0xa7:Completed 137500 out of 250000 steps (55%)
12:43:40:WU00:FS00:0xa7:Completed 140000 out of 250000 steps (56%)
13:01:13:WU00:FS00:0xa7:Completed 142500 out of 250000 steps (57%)
13:18:41:WU00:FS00:0xa7:Completed 145000 out of 250000 steps (58%)
13:36:16:WU00:FS00:0xa7:Completed 147500 out of 250000 steps (59%)
13:53:49:WU00:FS00:0xa7:Completed 150000 out of 250000 steps (60%)
14:11:24:WU00:FS00:0xa7:Completed 152500 out of 250000 steps (61%)
14:28:55:WU00:FS00:0xa7:Completed 155000 out of 250000 steps (62%)
14:46:25:WU00:FS00:0xa7:Completed 157500 out of 250000 steps (63%)
15:04:04:WU00:FS00:0xa7:Completed 160000 out of 250000 steps (64%)
15:21:36:WU00:FS00:0xa7:Completed 162500 out of 250000 steps (65%)
15:39:07:WU00:FS00:0xa7:Completed 165000 out of 250000 steps (66%)
15:56:33:WU00:FS00:0xa7:Completed 167500 out of 250000 steps (67%)
16:14:03:WU00:FS00:0xa7:Completed 170000 out of 250000 steps (68%)
16:31:39:WU00:FS00:0xa7:Completed 172500 out of 250000 steps (69%)
16:49:07:WU00:FS00:0xa7:Completed 175000 out of 250000 steps (70%)
17:06:39:WU00:FS00:0xa7:Completed 177500 out of 250000 steps (71%)
******************************* Date: 2020-04-22 *******************************
17:24:21:WU00:FS00:0xa7:Completed 180000 out of 250000 steps (72%)
17:41:52:WU00:FS00:0xa7:Completed 182500 out of 250000 steps (73%)
17:59:24:WU00:FS00:0xa7:Completed 185000 out of 250000 steps (74%)
18:16:55:WU00:FS00:0xa7:Completed 187500 out of 250000 steps (75%)
18:34:29:WU00:FS00:0xa7:Completed 190000 out of 250000 steps (76%)
18:52:01:WU00:FS00:0xa7:Completed 192500 out of 250000 steps (77%)
19:11:12:WU00:FS00:0xa7:Completed 195000 out of 250000 steps (78%)
19:28:52:WU00:FS00:0xa7:Completed 197500 out of 250000 steps (79%)
19:46:22:WU00:FS00:0xa7:Completed 200000 out of 250000 steps (80%)
20:03:54:WU00:FS00:0xa7:Completed 202500 out of 250000 steps (81%)
20:21:24:WU00:FS00:0xa7:Completed 205000 out of 250000 steps (82%)
20:38:56:WU00:FS00:0xa7:Completed 207500 out of 250000 steps (83%)
20:56:27:WU00:FS00:0xa7:Completed 210000 out of 250000 steps (84%)
21:13:57:WU00:FS00:0xa7:Completed 212500 out of 250000 steps (85%)
21:31:34:WU00:FS00:0xa7:Completed 215000 out of 250000 steps (86%)
21:49:03:WU00:FS00:0xa7:Completed 217500 out of 250000 steps (87%)
22:06:33:WU00:FS00:0xa7:Completed 220000 out of 250000 steps (88%)
22:24:06:WU00:FS00:0xa7:Completed 222500 out of 250000 steps (89%)
22:41:37:WU00:FS00:0xa7:Completed 225000 out of 250000 steps (90%)
22:59:08:WU00:FS00:0xa7:Completed 227500 out of 250000 steps (91%)
23:16:39:WU00:FS00:0xa7:Completed 230000 out of 250000 steps (92%)
******************************* Date: 2020-04-22 *******************************
23:34:15:WU00:FS00:0xa7:Completed 232500 out of 250000 steps (93%)
23:51:47:WU00:FS00:0xa7:Completed 235000 out of 250000 steps (94%)
00:09:19:WU00:FS00:0xa7:Completed 237500 out of 250000 steps (95%)
00:26:49:WU00:FS00:0xa7:Completed 240000 out of 250000 steps (96%)
00:44:20:WU00:FS00:0xa7:Completed 242500 out of 250000 steps (97%)
01:01:53:WU00:FS00:0xa7:Completed 245000 out of 250000 steps (98%)
01:19:27:WU00:FS00:0xa7:Completed 247500 out of 250000 steps (99%)
01:19:28:WU01:FS00:Connecting to 65.254.110.245:80
[93m01:19:29:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration[0m
01:19:29:WU01:FS00:Connecting to 18.218.241.186:80
[93m01:19:30:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m
01:19:30:WU01:FS00:Connecting to 65.254.110.245:80
[93m01:19:32:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration[0m
01:19:32:WU01:FS00:Connecting to 18.218.241.186:80
[93m01:19:32:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m
[91m01:19:32:ERROR:WU01:FS00:Exception: Could not get an assignment[0m
01:19:33:WU01:FS00:Connecting to 65.254.110.245:80
[93m01:19:33:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration[0m
01:19:33:WU01:FS00:Connecting to 18.218.241.186:80
[93m01:19:34:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m
01:19:34:WU01:FS00:Connecting to 65.254.110.245:80
[93m01:19:36:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration[0m
01:19:36:WU01:FS00:Connecting to 18.218.241.186:80
[93m01:19:37:WARNING:WU01:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration[0m
[91m01:19:37:ERROR:WU01:FS00:Exception: Could not get an assignment[0m
01:20:38:WU01:FS00:Connecting to 65.254.110.245:80
[93m01:20:40:WARNING:WU01:FS00:Failed to get assignment from '65.254.110.245:80': No WUs available for this configuration[0m
01:20:40:WU01:FS00:Connecting to 18.218.241.186:80
01:20:41:WU01:FS00:Assigned to work server 40.114.52.201
01:20:41:WU01:FS00:Requesting new work unit for slot 00: RUNNING cpu:2 from 40.114.52.201
01:20:41:WU01:FS00:Connecting to 40.114.52.201:8080
01:20:43:WU01:FS00:Downloading 2.14MiB
01:20:50:WU01:FS00:Download 5.84%
01:20:58:WU01:FS00:Download 11.68%
01:21:06:WU01:FS00:Download 17.51%
01:21:19:WU01:FS00:Download 23.35%
01:21:26:WU01:FS00:Download 26.27%
01:21:37:WU01:FS00:Download 29.19%
01:21:47:WU01:FS00:Download 32.11%
01:21:53:WU01:FS00:Download 55.46%
01:21:59:WU01:FS00:Download 100.00%
01:21:59:WU01:FS00:Download complete
01:21:59:WU01:FS00:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:13850 run:0 clone:38706 gen:50 core:0xa7 unit:0x0000003d287234c95e78893c57ddc78f
01:37:12:WU00:FS00:0xa7:Completed 250000 out of 250000 steps (100%)
01:37:18:WU00:FS00:0xa7:Saving result file ../logfile_01.txt
01:37:18:WU00:FS00:0xa7:Saving result file frame35.trr
01:37:18:WU00:FS00:0xa7:Saving result file frame35.xtc
01:37:18:WU00:FS00:0xa7:Saving result file md.log
01:37:18:WU00:FS00:0xa7:Saving result file science.log
01:37:18:WU00:FS00:0xa7:Folding@home Core Shutdown: FINISHED_UNIT
01:37:19:WU00:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
01:37:19:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:16420 run:1478 clone:0 gen:35 core:0xa7 unit:0x0000002ca8f5c67d5e8a605ba5ebe6bf
01:37:19:WU00:FS00:Uploading 4.74MiB to 168.245.198.125
01:37:19:WU01:FS00:Starting
01:37:19:WU00:FS00:Connecting to 168.245.198.125:8080
01:37:19:WU01:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/v7/lin/64bit/Core_a7.fah/FahCore_a7 -dir 01 -suffix 01 -version 706 -lifeline 7512 -checkpoint 15 -np 2
01:37:19:WU01:FS00:Started FahCore on PID 20398
01:37:19:WU01:FS00:Core PID:20402
01:37:19:WU01:FS00:FahCore 0xa7 started
01:37:20:WU01:FS00:0xa7:*********************** Log Started 2020-04-23T01:37:19Z ***********************
01:37:20:WU01:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
01:37:20:WU01:FS00:0xa7:       Type: 0xa7
01:37:20:WU01:FS00:0xa7:       Core: Gromacs
01:37:20:WU01:FS00:0xa7:       Args: -dir 01 -suffix 01 -version 706 -lifeline 20398 -checkpoint 15 -np
01:37:20:WU01:FS00:0xa7:             2
01:37:20:WU01:FS00:0xa7:************************************ CBang *************************************
01:37:20:WU01:FS00:0xa7:       Date: Nov 5 2019
01:37:20:WU01:FS00:0xa7:       Time: 05:57:01
01:37:20:WU01:FS00:0xa7:   Revision: 46c96f1aa8419571d83f3e63f9c99a0d602f6da9
01:37:20:WU01:FS00:0xa7:     Branch: master
01:37:20:WU01:FS00:0xa7:   Compiler: GNU 8.3.0
01:37:20:WU01:FS00:0xa7:    Options: -std=c++11 -O3 -funroll-loops -fno-pie -fPIC
01:37:20:WU01:FS00:0xa7:   Platform: linux2 4.19.0-5-amd64
01:37:20:WU01:FS00:0xa7:       Bits: 64
01:37:20:WU01:FS00:0xa7:       Mode: Release
01:37:20:WU01:FS00:0xa7:************************************ System ************************************
01:37:20:WU01:FS00:0xa7:        CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz
01:37:20:WU01:FS00:0xa7:     CPU ID: GenuineIntel Family 6 Model 15 Stepping 13
01:37:20:WU01:FS00:0xa7:       CPUs: 2
01:37:20:WU01:FS00:0xa7:     Memory: 3.84GiB
01:37:20:WU01:FS00:0xa7:Free Memory: 409.59MiB
01:37:20:WU01:FS00:0xa7:    Threads: POSIX_THREADS
01:37:20:WU01:FS00:0xa7: OS Version: 4.15
01:37:20:WU01:FS00:0xa7:Has Battery: true
01:37:20:WU01:FS00:0xa7: On Battery: false
01:37:20:WU01:FS00:0xa7: UTC Offset: 1
01:37:20:WU01:FS00:0xa7:        PID: 20402
01:37:20:WU01:FS00:0xa7:        CWD: /var/lib/fahclient/work
01:37:20:WU01:FS00:0xa7:******************************** Build - libFAH ********************************
01:37:20:WU01:FS00:0xa7:    Version: 0.0.18
01:37:20:WU01:FS00:0xa7:     Author: Joseph Coffland <[email protected]>
01:37:20:WU01:FS00:0xa7:  Copyright: 2019 foldingathome.org
01:37:20:WU01:FS00:0xa7:   Homepage: https://foldingathome.org/
01:37:20:WU01:FS00:0xa7:       Date: Nov 5 2019
01:37:20:WU01:FS00:0xa7:       Time: 06:13:26
01:37:20:WU01:FS00:0xa7:   Revision: 490c9aa2957b725af319379424d5c5cb36efb656
01:37:20:WU01:FS00:0xa7:     Branch: master
01:37:20:WU01:FS00:0xa7:   Compiler: GNU 8.3.0
01:37:20:WU01:FS00:0xa7:    Options: -std=c++11 -O3 -funroll-loops -fno-pie
01:37:20:WU01:FS00:0xa7:   Platform: linux2 4.19.0-5-amd64
01:37:20:WU01:FS00:0xa7:       Bits: 64
01:37:20:WU01:FS00:0xa7:       Mode: Release
01:37:20:WU01:FS00:0xa7:************************************ Build *************************************
01:37:20:WU01:FS00:0xa7:       SIMD: sse2
01:37:20:WU01:FS00:0xa7:********************************************************************************
01:37:20:WU01:FS00:0xa7:Project: 13850 (Run 0, Clone 38706, Gen 50)
01:37:20:WU01:FS00:0xa7:Unit: 0x0000003d287234c95e78893c57ddc78f
01:37:20:WU01:FS00:0xa7:Reading tar file core.xml
01:37:20:WU01:FS00:0xa7:Reading tar file frame50.tpr
01:37:20:WU01:FS00:0xa7:Digital signatures verified
01:37:20:WU01:FS00:0xa7:Calling: mdrun -s frame50.tpr -o frame50.trr -x frame50.xtc -e frame50.edr -cpt 15 -nt 2
01:37:20:WU01:FS00:0xa7:Steps: first=25000000 total=500000
01:37:24:WU01:FS00:0xa7:Completed 1 out of 500000 steps (0%)
[93m01:39:29:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80[0m
01:39:29:WU00:FS00:Connecting to 168.245.198.125:80
[93m01:41:40:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 168.245.198.125:80: Connection timed out[0m
01:41:40:WU00:FS00:Trying to send results to collection server
01:41:40:WU00:FS00:Uploading 4.74MiB to 146.94.192.82
01:41:40:WU00:FS00:Connecting to 146.94.192.82:8080
01:41:46:WU00:FS00:Upload 25.07%
01:41:51:WU00:FS00:Upload complete
01:41:51:WU00:FS00:Server responded WORK_ACK (400)
01:41:51:WU00:FS00:Final credit estimate, 1440.00 points
01:41:51:WU00:FS00:Cleaning up
01:50:45:WU01:FS00:0xa7:Completed 5000 out of 500000 steps (1%)

Can anyone explain what happened to my wu here?

I'm also a little confused by the info on the completed wu from the other folder. It seems to say it was assigned on 23rd, returned on the 25th, but says 0.379 days. Am I misunderstanding what those fields mean on that report as I thought that days referred to the time beteen assignment and return?

Gray_fox · Post by **Gray_fox** » Sat Apr 25, 2020 11:14 am

Not an expert in reading these FAH logs, but my experience as a PC tech means I can understand most logs in general to some degree

But from what I can make out

CPU(WU00) work unit started at 20:21:55(21st zulu)
CPU(WU00) work unit finished at 01:37:12
CPU(WU00) work unit upload started at 01:37:19 of 4.74MiB to IP 168.245.198.125
CPU(WU00) Upload failed due to timeout at 01:39:29
CPU(WU00) work unit upload started at 01:41:40 of 4.74MiB to 146.94.192.82
CPU(WU00) work unit upload finished at 01:41:51.(23st zulu)
You were credited with 1,440pts.

29h20m to complete work unit if my math is correct.

Neil-B · Post by **Neil-B** » Sat Apr 25, 2020 11:19 am

The column headings are switched for the returned and credited - known issue … your completed WU should show up as stats catch up (although this can be days/weeks not minutes/hours).

peterjammo · Post by **peterjammo** » Sat Apr 25, 2020 11:31 am

Thanks for that Neil, I can see that now. Just wondering why it would have been reassigned 18hrs after mine was returned? I thought that reassignment would be cancelled once a completed unit was received OK, even after timeout?

Neil-B · Post by **Neil-B** » Sat Apr 25, 2020 11:39 am

If yours was returned to a Collection Server (which it looks like it was) the Work Server doesn't know it has been sent back until it gets it from the Collection Server … I am guessing there is a delay between the two servers at the moment - If the WS is having issues receiving WUs from folders it is probably heavily loaded and so the CS may be having the same issue contacting it.

If the other folder got lucky and returned theirs direct to the WS then that nicely fits what you are seeing.

When the CS finally gets your results to the WS things will get properly recorded … This is one of the side effects of having a CS which buffers incoming WUs - until the WUs get back to the WS the processes cannot continue as normal

peterjammo · Post by **peterjammo** » Sat Apr 25, 2020 11:55 am

So other than a minor duplication of effort for the presumably tiny % that don't make timeout during the overload period, the only ill effect is on the ability to issue next in series wu? And if the problem is occurring because the WS is operating at full capacity issuing other wu, that's a non-issue too whilst server capacity is constrained (and disappears if the constraint goes).

In some ways, it's a nice set of "problems" to have, and yet another indication of the phenominal success of the project at the moment.

Neil-B · Post by **Neil-B** » Sat Apr 25, 2020 12:33 pm

I look at it that way too

… Pretty much all the current issues/problems are down to having had to scale up so rapidly and embrace a whole new folding community - There are hiccups but on the whole that incredible expansion of FAH outweighs all of them imho and even these are being dealt with faster than seems humanly possible given the circumstances we all find ourselves in.

Post by **PantherX** » Sat Apr 25, 2020 4:11 pm

peterjammo wrote:...I thought that reassignment would be cancelled once a completed unit was received OK, even after timeout?

Generally speaking, once a WU has been assigned to a Donor (duplicate or not) it will not be "cancelled" unless the WU reaches the expiration date. In that case, the client will delete the WU locally, there's no "command" from the Server ordering the delete.

Previously, if a WU is returned after the timeout but before the expiration date to the Work Server, that WU was already marked for assignment on the Work Server. Thus, it would still be assigned even though it has received the original copy and the next WU has been generated. That was the observable behavior that may or may not have changed with updates to the Server code. IMO, it would a nice enhancement to prevent the minor duplication of work but if the code tweak requires extensive work and verification, it might not be feasible to do.

peterjammo · Post by **peterjammo** » Sun Apr 26, 2020 9:40 am

Is the next wu generated in that series the next "gen" ie in this case 16420 1478 0 36?

EDIT - found this on an old post

Project - not explained outright but seem to be the protein under study. To me, this implies a particular amino acid sequence.
Run - the arrangement of the atoms in the protein in three dimensional space (orientation irrelevant) so in other words what configuration they're in.
Clone - describes the set of forces given to each atom
Gen - time steps in the simulation process, they are very serial so the n+1th is generated after the nth finishes

So assuming that's right next in in series wu was 16420 1478 0 36. I just had a look at that one to see whether my return appeared to trigger the next issue.

https://apps.foldingathome.org/wu#proje ... e=0&gen=36

If I'm reading that right, it was assigned a few minutes after the other folder returned the wu, approx 28 hours after mine went back to the collection server? Suggests that my slightly late wu took an awfully long time to get back to the WS, or perhaps still hasn't?

I'm not bothered at all about loss of points etc, or minor duplication of work, only that if there is a generic problem with return of wu in a certain circumstance, I'd like that to be flagged in case there's a bigger problem being hidden in the vast volume of work that's being done.

Neil-B · Post by **Neil-B** » Sun Apr 26, 2020 12:41 pm

Just checked the app again … Looks like your WU return may still stuck in the CS - or the WU stats are lagging (which is also possible) … It should turn up eventually but please don't hold your breath while waiting as these things can take days/weeks to catch up.

TPL · Post by **TPL** » Sun Apr 26, 2020 1:35 pm

I think I lost some credits this morning. Server response was (WORK_ACK), estimate 18.5k. Points didn't show up while 2 next WU's did. Ok, it may take time from some CS and still come up later but usually points will update within an hour or so.

I don't complain for lost points as I can't eat them on fill up my car tank with them.

Anyway it would be nice to understand what happened. Am I close with my guess that it was duplicate WU that someone else was still folding after timeout? And got ready before me?

Neil-B · Post by **Neil-B** » Sun Apr 26, 2020 1:48 pm

It really is likely just to be delays in the stats system - they happen - it can be days, weeks, probably not months - it really depends on the projects and the servers they are on so they don't always appear in order .. I currently have over 30 WUs waiting to appear from 17th onwards and I know which servers are being tricky for me … I have had as many as 100 in the past !!! … but that is very unusual … If your logs are showing the WUs uploaded successfully then they will show up eventually.

Stats issues tend to be the last things fixed as they don't actually impact the science - when things do catch up you get nice "bonus" spikes of points … If you look at this plot … https://folding.extremeoverclocking.com ... s=&t=39363 … my kit does about 275k a day - you can see days which spike much higher when stats catch up - the really big one was the 100+ WUs

TPL · Post by **TPL** » Sun Apr 26, 2020 2:02 pm

Ok, thanks.

peterjammo · Post by **peterjammo** » Sun Apr 26, 2020 7:09 pm

Neil-B wrote:Just checked the app again … Looks like your WU return may still stuck in the CS -

What's bothering me is that if my wu is stuck or delayed by at least 28 hrs, or even 3 days and counting as it may be now, if my reading of the available info suggests, I'm guessing it's quite likely that a lot of others may be similarly stuck or delayed. If CS -> WS delays of that length are happening regularly, does that not mean that a potentially large number of wu will be reassigned pointlessly by the WS as timeouts pass while the completed wu are delayed? I'm assuming that the WS "decide" when a wu timeout has passed and then reassign, and that they can't "see" any wu which are waiting to be sent by the CS.

I'm not bothered much about how long/whether the stats catch up, other than their potential (not so much at present) usefulness as an audit trail for my own machines.

Neil-B · Post by **Neil-B** » Sun Apr 26, 2020 7:23 pm

It is probably only a small proportion of a projects WUs that get held up (the forums only tend to see where there are issues not all the WUs that are getting sorted normally) - and I would expect that the WUs are actually making it back to the asap as the researchers and the team will have prioritised this … what may be happening is that the stats reporting is degraded under these circumstances … the team will be working to minimise this happening but even with some "losses" (if that indeed is what happens) the big picture is that the massive increase that is causing these overloads and the fast expansion of the infrastructure that may no be quite bedded in yet is still a huge benefit to the science.

A "similar" case is one of the GPU projects at the moment that has a high (er than normal) failure rate - but this was a risk by pushing it out very quickly, and the gains by pushing it out have outweighed the increased failure rate … but from an individual folders perspective who may feel they have wasted "17 hours" of folding power on a failed project this seems difficult to swallow.

The researchers and the team will be doing their best to minimise issues and not waste any effort - but sometimes it happens.

Folding Forum

WU 16420 1478 0 35 - what happened to my one?

WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?

Re: WU 16420 1478 0 35 - what happened to my one?