Project 9015 (418, 2, 87)

[petnek]

Hello,
this WU I successfully completed but it stuck on the connection to the server.

Code: Select all

13:09:07:WU00:FS00:0xa4:Completed 242500 out of 250000 steps  (97%)
13:11:07:WU00:FS00:0xa4:Completed 245000 out of 250000 steps  (98%)
13:13:08:WU00:FS00:0xa4:Completed 247500 out of 250000 steps  (99%)
13:15:08:WU00:FS00:0xa4:Completed 250000 out of 250000 steps  (100%)
13:15:09:WU00:FS00:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
13:15:19:WU00:FS00:0xa4:
13:15:19:WU00:FS00:0xa4:Finished Work Unit:
13:15:19:WU00:FS00:0xa4:- Reading up to 916296 from "00/wudata_01.trr": Read 916296
13:15:19:WU00:FS00:0xa4:trr file hash check passed.
13:15:19:WU00:FS00:0xa4:- Reading up to 839380 from "00/wudata_01.xtc": Read 839380
13:15:19:WU00:FS00:0xa4:xtc file hash check passed.
13:15:19:WU00:FS00:0xa4:edr file hash check passed.
13:15:19:WU00:FS00:0xa4:logfile size: 23247
13:15:19:WU00:FS00:0xa4:Leaving Run
13:15:20:WU00:FS00:0xa4:- Writing 1781411 bytes of core data to disk...
13:15:20:WU00:FS00:0xa4:Done: 1780899 -> 1722326 (compressed to 96.7 percent)
13:15:20:WU00:FS00:0xa4:  ... Done.
13:15:22:WU00:FS00:0xa4:- Shutting down core
13:15:22:WU00:FS00:0xa4:
13:15:22:WU00:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
13:15:22:WU00:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
13:15:22:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:9015 run:418 clone:2 gen:87 core:0xa4 unit:0x00000077664f2de453e55dcbdb81c94c
13:15:23:WU00:FS00:Uploading 1.64MiB to 171.64.65.124
13:15:23:WU00:FS00:Connecting to 171.64.65.124:8080
******************************* Date: 2015-04-13 *******************************

After that client downloaded next unit from the same server (collection server also same) and uploaded it without problems. After client complete restart it automatically uploaded that unit, so it somehow stuck there.

[bruce]

I'm not sure what caused it to get stuck (you didn't post that part of the log) but it has been credited:

Hi petnek (team 49658),
Your WU (P9015 R418 C2 G87) was added to the stats database on 2015-04-13 14:10:51 for 845.997 points of credit

[petnek]

When I noticed this issue, second WU after that was in 90%. That part of log contain all informations about weird WU. You can see logfile from entire day here. Like in previous post, issued WU is from time 13:13:08 like WU00 FS00

[bruce]

I have no explanation.

Your log shows four occurrences of "state:SEND" which are paired with only three "Upload complete" messages and it's not like your connection failed because the WU that hung is not the last one.

[Joe_H]

Only possibility I can think of is that either the ACK response from the WS that the WU had been successfully uploaded was lost between the WS and your system, or that the client missed it once it reached your system. That has been seen before on some ISP's or when the system is connected by a wireless connection. If you see this happening often, then you may want to look into your network connection.

If the WU remained on your system, it will eventually be deleted when the timeout is reached. Or you can remove it manually.

One suggestion, please return the logging verbosity to the default of 3. Higher settings rarely provide any useful information, and do get in the way of troubleshooting a client problem.